Swagger API reference
Explore the authenticated REST endpoints, request bodies, response models, and status codes for bundle, employment confirmation, and signing API operations.
Open Swagger (opens in a new tab)Developers
Find the API reference, webhook contract, upload flow, and tenant setup entry points used by client integrations.
API requests use tenant API keys in the XApiKey header. Generate keys in
the tenant dashboard, then use Swagger and the bundle guide to wire the integration.
Integration operating contract
Contact Us to discuss non-production testing and access options.
The application currently has an in-process global limiter of 600 requests per minute, partitioned by the remote IP observed by the application. Because it is global, it also applies to authenticated API calls. Requests rejected by the limiter receive HTTP 429.
Explore the authenticated REST endpoints, request bodies, response models, and status codes for bundle, employment confirmation, and signing API operations.
Open Swagger (opens in a new tab)Create a bundle, request a signed upload target, send PDF bytes to blob storage, complete the file attachment, and receive lifecycle callbacks.
Read the bundle guideValidate signed bundle events with HMAC-SHA256, handle retries idempotently, and inspect delivery history on bundle responses.
Verify webhook signaturesSign in to your tenant dashboard to create, update, or revoke API keys before calling authenticated endpoints.
Sign in to manage keysGive this Markdown file to an AI coding assistant so it can implement the OptiTrust API flow with the correct upload, webhook, signing, and authentication rules.
Open the skill file
Current client integrations are exposed under /api/bundles,
/api/employment-confirmations, and /api/sign.