Talk to the team
Build your integration with us
Our team reviews your use case: which endpoints to use, how to structure the envelopes and what to validate in the sandbox before going to production. Get your questions answered directly on WhatsApp.
Automate the creation, sending and tracking of envelopes from your own system, with nobody needing to open the platform.
Upload the document, assemble the envelope with signers and validations, publish and check the status: the full flow in REST calls.
curl -X POST https://api.signater.com/v1/ecm/envelopes \
-H "x-api-token: $SIGNATER_API_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"vaultId": "5b8f6c2e-8a34-4f4b-9a4e-2f1c3d7e9a01",
"name": "Service agreement",
"language": "EnUs",
"signers": [
{ "name": "Sarah Miller", "email": "[email protected]" }
],
"documents": [
{ "id": "9c7d1a3f-6b2e-4c5d-8e9f-0a1b2c3d4e5f",
"name": "Contrato" }
]
}'From envelopes to evidence, the REST resources cover the full signing cycle, so your system orchestrates everything without anyone opening the platform.
Assemble, publish and track every stage, from draft to the final certificate of completion. Pausing, canceling and resending invitations are API calls too.
Upload accepts PDF, Word, spreadsheet and image files, always converting to PDF. The returned ID goes straight into the envelope.
An approved template becomes a new document in a single call, with the variable data filled in by your system.
Register recurring signers once; on the next sends, name, email and phone come pre-filled.
Separate clients or departments into vaults and choose who is a member of each. Every envelope created through the API lives in one of them.
Download the signed PDF, the original and the certificate of completion with direct calls, ready to archive in your system.
Authentication and limits
Every call is authenticated with an API key sent in the dedicated
x-api-token header. Create a key for each system that integrates, with its own
name and description, and revoke any one without taking the others
down.
Traffic is limited per key and per IP address, in a sliding window. Whoever exceeds the limit gets an HTTP 429 with a standardized response, easy to handle with a retry policy in your client.
Sandbox
Vaults and API keys can be created in sandbox mode. Test envelopes are born in that isolated vault, away from the account's real documents.
In the sandbox, authentication factors run in simplified form: test codes replace the real dispatches, and you validate the flow without bothering a signer.
Webhooks
Every envelope event — published, signed, completed — fires a webhook to your endpoint, with automatic retries if it happens to be down.
Documentation
The documentation at docs.api.signater.com is born from the API's own OpenAPI specification: every endpoint, with parameters, payload examples and response codes.
Explore the calls in the browser before writing the first line of your integration, and come back to the reference whenever you need the exact format of a field.
{
"id": "b4c2f8d1-3e5a-4b6c-9d7e-1f2a3b4c5d6e",
"name": "Service agreement",
"status": "Published",
"signInOrder": false,
"signers": [
{
"name": "Sarah Miller",
"status": "Approved",
"approvedAtUtc": "2026-07-02T14:32:08Z"
},
{
"name": "Carlos Lima",
"status": "ReadyToReview"
}
]
}The Business and Enterprise plans, together with webhooks and the sandbox environment. There is no extra charge for access: on one of those plans, the API is unlocked.
Each request carries an API key in the dedicated x-api-token header. You create the keys on the platform itself, can keep several active at the same time and revoke any one instantly, without affecting the others.
Yes. Vaults and API keys can be created in sandbox mode: test envelopes stay isolated and the authentication factors run in simplified form, with test codes. You validate the integration without touching production data.
No. Documents created through the API consume the same plan balance as those created on the platform. There is no per-call fee and no separate charge for integrations.
Yes, through webhooks: events like envelope.published, envelope.signed and envelope.expired are delivered to your endpoint, with automatic retries if it is unavailable.
At docs.api.signater.com. The reference is generated from the API's OpenAPI specification and covers all endpoints, with parameters, request examples and response codes.
Talk to the team
Our team reviews your use case: which endpoints to use, how to structure the envelopes and what to validate in the sandbox before going to production. Get your questions answered directly on WhatsApp.