1. Create a case
POST /cases with a title, validUntil and the participants. The answer carries each participant’s
signing link and a presigned URL for the PDF.
Build signing into your system
Create a case, upload the PDF, let people sign on any device or at your counter, and get back a PAdES-signed document with its evidence. One REST API, webhooks and real-time events.
Where to start
Section titled “Where to start”QuickstartFrom API credentials to a signed PDF and its evidence summary in six steps.
GuidesSignature fields, webhooks, real-time events, the kiosk flow, one-time codes and verification.
API referenceEvery route with its parameters, bodies, answers and error codes, generated from the OpenAPI document.
SandboxTry everything against the sandbox before you go live, with the same API as production.
How a case flows
Section titled “How a case flows”2. Upload the PDF
PUT the document to the presigned URL. TrustInk invites the participants by email, or opens the case on your kiosk for signing in person.
3. People sign
Each participant opens their link on any device, optionally confirms a one-time code, and signs. You follow along with webhooks or real-time events.
4. Get the documents
When everyone has signed you receive case-completed with links to the signed PDF (PAdES B-LTA, sealed by
TrustInk) and the sealed evidence summary.
Good to know
Section titled “Good to know”- Environments. The sandbox answers on
https://api-sandbox.trustink.io, production onhttps://api.trustink.io. See Sandbox. - Hosting. TrustInk runs on AWS in the EU (Ireland, eu-west-1).
- Signature level. Today a TrustInk signature is a simple electronic signature (eIDAS article 25) with advanced cryptographic evidence: a certificate per signer, RFC 3161 timestamps and long-term validation data.
- Verification. Anyone can check a signed PDF on trustink.io/verify or with
POST /verify.