|HTTP Status Code
400 Bad Request
|Invalid authentication, check that your are using the correct API Key on the right environment (Sandbox / Production).
|Access to this resource is forbidden in this context.
404 Not Found
|The requested ressource was not found.
429 Too Many Requests
|Too many requests sent in a given amount of time. Please reduce the number of calls or rely on webhooks instead of polling. Learn more about rate-limiting.
500 Internal Server Error
|Servers are not working as expected. The request is probably valid but needs to be requested again later.
503 Service Unavailable
|We are currently under maintenance.
To help you troubleshoot your issues, all the 4XX errors contain additionnal information in the JSON response.
|Key that identify the error type
|Human readable message explaining the error
|Only present for errors of type
Array of objects with attributes:
name identifying the concerned field and
reason describing the validation issue
"detail": "You have some invalid params in your payload.",
"reason": "Value must be in [\"none\", \"email\"]."
"detail": "The signature request \"80c30a0e-84cd-4574-8161-8669f6603189\" is still ongoing, the completed documents are not available yet"
|The audit trail is not ready to be downloaded yet
|An approver with the same information is already attached to the Signature Request.
|The given date range is out of the valid range.
|A contact restricted to a single workspace cannot be used as a signer or approver for a signature request from another workspace.
|The given date range is invalid: the start date is greater than the end date.
|The document is already attached to a Signature Request. To attach a document to another Signature Request you need to re-upload it first.
|The document is already used for another electronic seal.
|Unable to replace the document.
|Cannot upload the document because it fails to be unlocked.
|The document is not valid. For example its extension is invalid, or it's not readable.
|Size of document is too large to be performed
|The limit of images for the electronic seal has been reached.
|The limit of fields for the electronic seal has been reached.
|The dimensions for the field are invalid.
|With the current signature level, only one signature field per document and per signer is allowed.
|The field type is not allowed for the document. It might be because the document is already signed or the document doesn't support this kind of field.
|You have some invalid params in your payload.
|This error corresponds to the 404 HTTP error for any resource.
|The given Signature Request's expiration date is not within the allowed range.
|The Signature Request doesn't have any document, therefore the actual action cannot be performed.
|The Signature Request is not activable in its current state.
|The Signature Request can't be reactivated.
|The Signature Request already has metadata. You can still update them.
|There is an error in the signature request's sender configuration.
|The actual action is not compatible with the Signature Request's status.
|The number of documents in the Signature Request is greater than the authorized number.
|The number of signers in the Signature Request is greater than the authorized number.
|A signer with the same information is already attached to the Signature Request.
|The authentication mode and the signature level for the signer are not compatible.
|The signature level with the given authentication mode is not enabled for your organization.
|The Signer does not have any field. You need at least one field per Signer.
|Signer's phone number is required in this case.
|Reordering Signers is not allowed in this context.
|The given signature level for Signer is not available in the current context.
|The signature level is not enabled for your organization.
|All Signers should have the same signature level for this specific Signature Request level.
|The current action is not compatible with the Signer's status.
|A limit has been reached concerning your current subscription.