Integration guide

This document will guide you through the configuration and implementation steps that are necessary in order for your backend to be able to retrieve and send documents for users to electronically sign.

The integration steps are as follows:

Step 1 -Authentication

Step 2 -Create envelope request

Step 3 -Get / Archive documents

The Yoti Sign endpoints are listed below:

Knowledge base
Have a look at our FAQs for more information and try out our demo.

Authentication token

Before you start
Request your API keys, please let us know if you want to use sandbox or production.

Yoti Sign uses an HTTP authentication scheme called ‘bearer authentication’. This involves security tokens called ‘bearer tokens’. They are the predominant type of access token used with OAuth 2.0. A resource should interpret a bearer token as "Give the bearer of this token access". The client must send this token in the Authorization header when making requests to protected resources.

Important Your API Key must remains strictly confidential. It must be stored securely. We advise that you never commit any code containing your API Key, and never share it beyond the authorised party.

If you believe your API key has been compromised, please contact us as soon as possible. This can be done through your account manager or via our support channel by emailing clientsupport@yoti.com.

Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard