Welcome!

The signNow REST API allows you to integrate e-signatures into your app, website, CRM or cloud storage.

It’s been designed to share signNow’s core webapp functions: to give or request a legally binding e-signature, and to build multi-step role-based workflows where several document templates are sent to multiple signers and each signer is given a different level of access.

Learn more about it in Features.

Requests

Most signNow API requests have an Authorization header and content-type header - application/json. Some endpoints accept only content-type: multipart/form-data. Request documentation and samples are available in the API Reference.

curl -X POST \
  https://api-eval.signnow.com/template \
  -H 'Authorization: Bearer {{access_token}}' \
  -H 'Content-Type: application/json' \
  -d '{
        "document_id":"{{document_id}}",
        "document_name":"my_template"
      }'

Responses

As a RESTful API, signNow relies on a list of predefined URLs which return responses in JSON format.

{
   "id":{{template_id}} 
}

Error responses

Errors vary between these responses: invalid_client, invalid_request, invalid_token, access_denied, invalid_payload, internal API error etc. Check out the error responses for specific endpoints in API Reference.

Resources

Authentication

The signNow API relies on the principles of REST architecture and OAuth 2 authentication. To ensure data privacy, unencrypted HTTP is not supported.

Methods

GET - means ‘retrieve data’. This request doesn’t create or update anything; works with users, tokens, document history, etc.

POST - use this method to create new resources: add users, event subscriptions, signature invites etc.

PUT - update a resource: add a signed document or receive a response when someone declines to sign a document.

DELETE - make this request to remove a resource.

SDKs

signNow currently supports five server-side libraries for testing the signNow API in your environment.

Testing environment

Feel free to request an API key and create a sandbox where you’ll be able to use a ready-for-Test App and generate as many apps as you’d like with their own client ID-secret pairs.

Code examples

In signNow API documentation we use curl to illustrate examples of requests. Here is an example of a request to create a one-time link for downloading a document.

curl -X POST \
  https://api-eval.signnow.com/document/{{document_id}}/download/link \
  -H 'Authorization: Bearer {{access_token}}'

A successful response is usually marked in a table as 200OK:

{
  "status": "success"
}