Changelog
Tento obsah zatiaľ nie je dostupný vo vašom jazyku.
The changes to the TrustInk API and to these docs, newest first. The API is at version 1.0, in preview. Additions such as new fields, routes and event types can arrive with any release, so let your integration ignore fields and event types it does not know.
September 2026
Section titled “September 2026”API 1.0 preview
- Cases with one or more participants, signing links by email, reminders (
reminders.afterDays), expiry (validUntil) and cancellation (DELETE /cases/{caseId}). - Predefined signature fields in PDF points or page fractions (coordinates).
- One-time codes by email (
multiFactorType), with SMS to follow (one-time codes). - Signed documents at PAdES B-LTA: a one-shot certificate per signer from the TrustInk Signing CA, RFC 3161 timestamps, embedded revocation data and the TrustInk seal, plus a sealed evidence summary PDF.
- Webhooks signed with HMAC-SHA256 (
Trustink-Signature), with basic, API key and OAuth 2.0 client credentials authentication (webhooks). - Real-time events over AWS AppSync Events (real-time events).
- Quick-sign cases and kiosk devices for signing in person (in-person signing).
- The audit trail of a case (
GET /cases/{caseId}/events). - Public verification of any signed PDF (
POST /verify/upload,POST /verify, verification).
Docs
- The documentation at trustink.io/docs: quickstart, guides and the API reference generated from the OpenAPI document.