If you already run your own CRM, ERP, or any internal system, signing and document workflow don't have to live in a separate interface — you can embed them right inside your product. The eObig partner REST API is built exactly for that: product teams, integrators, and companies with their own systems typically connect it in a couple of days. Let's look at how simple it is and where to begin.
Why Integration Is Simple
The eObig partner API is plain REST over HTTPS, so it fits any stack without exotic libraries. The base path is api.eobig.com/partner/v1, with the version baked right into the URL — so API updates won't break your code, and you decide when to move to a newer version.
The documentation ships as an OpenAPI 3.0 spec with an interactive Swagger UI. That means you can open the spec, hit "try it out" straight in the browser, and then generate a ready-made client in your language — no hand-written wrappers. Behavior stays predictable at the edges too: responses include rate-limit headers, so you always see what's left and plan your load without surprises.
One important security detail: the private signing key never reaches the server. You produce the signature on the client side in CMS/CAdES format and pass the finished signature to the API — the platform accepts it as is. For more on this model, see the article on browser-based signing security, and for the standard itself, what a qualified electronic signature is.
Authorization in 2 Headers
No complex OAuth dance: authorization rests on two headers. X-Access-Token is your access key, and X-Organization is the identifier of the company the integration acts on behalf of. The key can be revoked at any time, so rotation and access control stay in your hands.
Here's what a typical document-upload request looks like:
POST https://api.eobig.com/partner/v1/documents
X-Access-Token: <your_key>
X-Organization: <company_id>
Content-Type: multipart/form-data
file=@contract.pdf
In response you get a document identifier that you work with from there: adding signatures, granting access to participants, or creating a guest link. Simple authentication means you'll make your first working request within minutes of receiving the key.
Key API Capabilities
In total there are around twenty endpoints covering the full document life cycle — from upload to archive. Here are the most important groups:
| Group | What it lets you do |
|---|---|
| Documents | Upload, list and search, fetch the original and the signed version, delete |
| Organization | Rename, tags, archiving, batch status checks |
| Signatures | Get existing signatures, add a ready CMS/CAdES signature |
| Access | Participants and sharing, guest links to sign or fill in |
| Counterparties | Verify a counterparty by its EDRPOU code |
| Webhooks | Subscribe, list, delete callback URLs |
Guest links deserve special attention: your counterparty signs a document or fills it in via a link WITHOUT registering in the system. For an integration, that means external parties join the process with zero friction — this scenario is covered in detail in the article on sending for signature without registration.
Webhooks: Real Time in Your CRM
Instead of polling the server in a "signed yet?" loop, subscribe to webhooks. You provide your callback URL, and eObig sends a notification the moment an event happens: document signed, signing failed, counterparty declined, plus AI events. Your CRM updates the deal status in the same second.
Every webhook call carries an HMAC signature in the header — you verify the message's authenticity and reject forgeries. If your service is briefly unavailable, the system retries delivery, so no event is lost. Unlike many document-workflow services, webhooks here are a native part of the API, not a bolt-on.
AI Right Inside the API
This is the advantage most platforms simply don't have: AI is available directly through the API. You can programmatically generate a document from a text description, edit an existing one, or build a template — without pulling the user out of your interface.
Because such tasks take time, they run asynchronously: you place a request and learn about completion through a webhook. AI has a separate quota, so generation doesn't compete with your regular requests. Picture it: a manager in your CRM describes a deal in words and, seconds later, gets a ready contract draft right in their working window. For more of what the platform's AI can do, see the AI page.
How to Get Started
Self-service key issuance in the dashboard isn't available yet, so access to the partner API is granted by the team. To get a key, submit a request via a demo or reach out to us directly — we'll grant access and help with your first integration.
From there it's the standard path: open the Swagger UI, generate a client, make your first document-upload request, subscribe to webhooks, and run one scenario end to end. The full set of platform tools is on the features page, and the fundamentals of workflow integration are in the article on document workflow API integration.
Key Takeaways
- Partner REST API
api.eobig.com/partner/v1with path versioning — integration usually takes a couple of days. - Authorization via simple
X-Access-TokenandX-Organizationheaders; the key can be revoked. - The private key is never stored on the server — the CMS/CAdES signature is produced client-side.
- Around twenty endpoints, registration-free guest links, EDRPOU verification.
- Webhooks with an HMAC signature and delivery retries — real time without polling.
- AI right inside the API — a unique advantage for generating and editing documents.
Want to embed signing and document workflow into your product? Start for free at portal.eobig.com or book a demo — we'll show the API on your own processes and help with integration. You can review plans on the pricing page.