Terms used¶
This page defines key terms and concepts you will encounter throughout the documentation. We recommend familiarising yourself with these before getting started.
Portal API¶
Esigna manages the entire signing workflow — your app creates a signing process via the API, and esigna handles sending documents, notifying participants, and collecting signatures. Once all participants have signed, a process.completed webhook tells your app, and it downloads the signed document.
Choose this if you want to add signing to your app without building the signing flow yourself.
Signing API¶
Also called the Integration API. Your app manages the document and participants, while esigna provides the underlying signature capability. This gives you full control over the user experience and workflow.
Choose this if you need to embed signing directly into your own custom flow or UI.
Other terms¶
| Term | Definition |
|---|---|
| Signing process | A single document sent out for signatures, tracking the document, participants, and overall completion state. |
| Participant | A person invited to a signing process, either to sign the document (a signer) or to read it (a viewer). |
| Kennitala | The Icelandic national ID number, 10 digits. |
| Webhook | An HTTP request esigna sends to your app when something happens in a signing process. |