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 Token

Signature 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:

  1. Ensure all documents intended for signing are uploaded through the file-manager endpoint. Keep the URLs of these documents handy.

  2. Build payload request

  3. Enter the details of the recipients who are required to sign the documents. This includes their names and email addresses.

  4. Paste the URLs of the documents that were uploaded in step 1 into the designated field ('fields' array node from payload).

  5. Customize any message or instructions you wish to include in the email that will be sent to recipients.

  6. 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.

Below you can find information regarding on how to create a signature request

post

Create entity

Authorizations
OAuth2authorizationCodeRequired
Authorization URL: Token URL:
Available scopes:
  • : OpenID Connect scope for add user roles to the access token
Body

Document sign request

idstring · uuidOptional
createdDatestring · date-timeOptional

Document signature request creation date

titlestringOptional

Document title

Example: Sample document
signatureReasonstringOptional

Signature reason

Example: Signature reason
saveSignedFileToOriginalPathbooleanOptional

Whether to save signed file to original path or not

Example: false
requestedBystringOptional

Name of the user who requested the signature

Example: John Doe
userIdstring · uuidOptional

User id of the user who requested the signature

Example: 123e4567-e89b-12d3-a456-426614174000
expirationDatestring · date-timeOptional

Expiration date of the signature request

sentDatestring · date-timeOptional

Send date of the signature request

alertOneDayBeforeExpirationbooleanOptional

Whether to alert one day before expiration or not

Example: false
autoReminderbooleanOptional

Whether to auto remind or not

Example: false
reminderFrequencyInDaysinteger · int32Optional

Reminder frequency in days. autoReminder flag must be true

Example: 3
maxAutoRemindersinteger · int32Optional

Max. auto reminders. autoReminder flag must be true

Example: 5
statusstring · enumOptional

Status of the document signature request

Example: DRAFTPossible values:
protectWithPasswordbooleanOptional

Whether to protect with password or not

Example: false
passwordstringOptional

Password for the document

Example: password
messageToAllRecipientsstringOptional

Message to all recipients

Example: Your document(s) are ready to be signed
tagsstring[]Optional

Tags for the document

Responses
200

OK

application/json
post
/v1/signatures/request

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

Get results paginated

Authorizations
OAuth2authorizationCodeRequired
Authorization URL: Token URL:
Available scopes:
  • : OpenID Connect scope for add user roles to the access token
Query parameters
Responses
200

OK

*/*
get
/v1/signatures/request

This feature allows you to keep track of all your signature requests efficiently, ensuring no document is left unsigned or unattended.

Last updated