Last updated
Last updated
The Electronic Signature APIs allow you to:
Upload documents for signing by end-users
Have end-users sign previously uploaded documents
This API will return a value of Documents Signed.
Currently only available via the , and signing is available using the .
The Electronic Signature APIs use form-encoded request bodies, and JSON-encoded response bodies. They also support authentication using HTTP Headers.
Authentication Headers are presented below
The Upload Documents API has the following input parameters which should be contained in a form-encoded request body
The Electronic Signature API returns a set of top level values as well as a detailed set of actions that can be used for a more granular evaluation of the individual fields.
For the Sign Endpoint (this is the same response sent to the callback of the asynchronous endpoint)
The Upload Documents API has the following input parameters which should be contained in a form-encoded request body
The Electronic Signature API returns a set of top level values as well as a detailed set of actions that can be used for a more granular evaluation of the individual fields.
For the Sign Endpoint (this is the same response sent to the callback of the asynchronous endpoint)
The Upload Documents API has the following input parameters which should be contained in a form-encoded request body
Example JSON Response
For the Sign Endpoint
Result codes details what the current (or final) result of a job is. Result Codes for all jobs fall into one of three categories:
This means no further processing is possible on the job. General failures occur when a job could not be submitted due to a logical/technical issue. These jobs do not show up in the portal and do not have a Smile Job ID.
* - read more on how to troubleshoot this error \