Skip to main content

Authenticate and Obtain an Access Token

POST 
/access/login

To use the Skribble API, you first need an API key and an API user. Both can be managed on the API key page in your business profile. Consult our guide for setup instructions.

Skribble offers two types of API keys:

Demo API keys

Demo API keys are for testing and development purposes. Signatures created with demo keys have no legal weight and are free of charge.

Demo keys can be identified by their name, which starts with api_demo.

Production API keys

Production API keys are used for live systems. Signatures created with production keys will be invoiced.

Production keys can be identified by their name, which starts with api_production or, in some cases, api_prod.

⚠ Note All costs incurred by signature requests created with your API keys will be charged to your business. We recommend starting with a demo API key during development and testing, and switching to a production key only once testing is complete.

For help setting up Skribble Business, contact us at info@skribble.com.

To obtain an access token, authenticate using the /access/login endpoint. You can pass your credentials as raw JSON or as x-www-form-urlencoded key-value pairs (see example requests).

Upon successful authentication, a JSON Web Token (JWT) is returned. This JWT must be included in nearly every API request.

The access token is passed in the Authorization HTTP header using the Bearer scheme. Example: Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI...

Token life cycle​

API key​

API keys have a long but finite lifetime. The validity period depends on the volume of API calls and is agreed upon individually as part of the shared secret agreement.

Access token​

Access tokens have a lifetime of approximately 20 minutes. Automatic token renewal is not currently supported.

Logout​

There is no logout endpoint. Access tokens expire automatically after the defined lifetime.

Request​

Responses​

OK