Sign documents with national eIDs and the PAdES standard.
Idura Signatures allows you to sign any PDF document using the national eIDs supported by Idura.
The signed documents are compliant with the PAdES-LTA standard.
Idura Signatures is designed to be embedded into your application. This means there is no signing portal where you run the process from.
Instead, you create a signing process using the Signatures GraphQL API, then redirect each user to a unique signing link in the Idura-hosted signatory UI.
Once all users have signed, you retrieve the signed documents via the API.
Terms and definitions
Signature order: a basic building block of the Signatures API. It contains the documents and the signatories you invite to sign them.
Document: a PDF included in a signature order.
Signatory: a person invited to sign the document. Each signatory gets a unique signing link.
Signature seal: a visual mark placed on the signed document. It can show details like the document ID and time of signing, filled from the signatory’s claims through templating.
Webhooks: a tool for receiving near real-time events for your signature orders, for example when a signatory has signed.
The terms below relate to your account at Idura and are fully explained in the Idura Verify core concepts.
Tenant: your company’s isolated environment at Idura. You create a tenant
when you sign up for an account, and it holds your domains
and applications. No other customer has access to your tenant.
Test and Production: two separate environments inside your tenant. Test environment uses test users, Production uses real eIDs and requires a paid subscription.
Domain: the address your signing requests run through, for example
acme-corp.test.idura.broker. Each domain belongs to either your Test or Production environment.
Application: represents the backend service you are building. Creating
an application gives you the client ID and secret you’ll need to call the Signatures API.
eID providers: the national identity services that authenticate your users, such as Danish MitID or Swedish BankID. Every signature is eID-based and tied to a verified identity. See all eIDs supported by Idura.
Where to go next
If you are new to Idura Signatures, start with the Getting started guide. It takes you from account setup to your first signature order.
From there:
GraphQL examples: example queries and mutations for common tasks.
Interactive tour: walk through a complete signing flow, step by step.
Integrations: client libraries for C#, Node.js, PHP, and Python.
