Quick Start
Get your API keys
All API calls require authentication. To obtain an authentication token you will require a username, password, client id and secret (this was emailed to you).
Any request that doesn't include an API key will return an error.
You can generate an API key from your DMS Workspace E-Signature Dashboard at any time or by contacting us via email at [email protected]
Create Token
Create TokenSignature Flow

Example Request
Bellow you will find some example requests
Making your first request
Create a new document signature request
To initiate a document signature request, follow the steps below:
Ensure all documents intended for signing are uploaded through the file-manager endpoint. Keep the URLs of these documents handy.
Build payload request
Enter the details of the recipients who are required to sign the documents. This includes their names and email addresses.
Paste the URLs of the documents that were uploaded in step 1 into the designated field ('fields' array node from payload).
Customize any message or instructions you wish to include in the email that will be sent to recipients.
Submit the request.
Upon submission, an email will be automatically sent to all listed recipients, containing the documents for signing along with any instructions provided. Recipients will have the option to either sign the documents electronically or decline the request.
This straightforward process ensures a seamless experience for both the requester and the recipients, facilitating efficient document management and expedited turnaround times for necessary signatures.
Note that the files to be signed must be uploaded first via the file-manager endpoint and keep the urls, which you will need to specify on the signature request.
Below you can find information regarding on how to create a signature request
Create entity
- : OpenID Connect scope for add user roles to the access token
Document sign request
Document signature request creation date
Document title
Sample documentSignature reason
Signature reasonWhether to save signed file to original path or not
falseName of the user who requested the signature
John DoeUser id of the user who requested the signature
123e4567-e89b-12d3-a456-426614174000Expiration date of the signature request
Send date of the signature request
Whether to alert one day before expiration or not
falseWhether to auto remind or not
falseReminder frequency in days. autoReminder flag must be true
3Max. auto reminders. autoReminder flag must be true
5Status of the document signature request
DRAFTPossible values: Whether to protect with password or not
falsePassword for the document
passwordMessage to all recipients
Your document(s) are ready to be signedTags for the document
OK
Bad Request
Unauthorized
Not Found
Recipients to sign sent document (s)
Once you create the document signature request, an email will be sent by the system to all recipients, from there they will have a link to visualize the documents to be signed and they will have the option to sign or decline to do it. This process is automatically executed from our side.
Query existing document signature requests
To query existing document signature requests, you can find information bellow
Get results paginated
- : OpenID Connect scope for add user roles to the access token
OK
Bad Request
Unauthorized
Not Found
This feature allows you to keep track of all your signature requests efficiently, ensuring no document is left unsigned or unattended.
Last updated