Get started¶
Esigna is a digital signing platform that creates legally binding, eIDAS-compliant signatures valid across Europe. This documentation covers the esigna API, which lets you integrate signing into your own application.
The base URL for all API endpoints is:
Choose your integration path¶
Esigna offers two APIs depending on how much control you want over the signing workflow:
Portal API — esigna manages the full signing workflow. You create a signing process with a document and a list of participants, and esigna handles inviting participants, collecting signatures, and notifying you when the process is complete. Best suited for adding signing to your app without building the signing flow yourself.
Signing API (also called the Integration API) — your app manages the document and the signing flow, while esigna provides the underlying signature capability. You send the document directly for signing and receive the signed file back. Best suited for embedding signing into an existing custom flow or UI.
Terms used explains the words these pages use.
Before you start¶
1. Get credentials
Contact us to apply for a client ID and client secret. Keep these secret — do not expose them in client-facing code or source repositories.
2. Obtain an access token
All API requests require a Bearer token. See Authorization for how to exchange your credentials for a token and which scopes to request.
Next steps¶
- Authorization — obtain a token with
portal/readandportal/writescopes - Portal API — create signing processes and download signed documents
- Webhooks — set up a webhook to be told when participants sign, decline, or all have signed
- Authorization — obtain a token with the
api/signaturesscope - Signing API — sign a document in three steps