Build signing into the way your business works.

Connect the agreement to its source record

Create an envelope with a PDF and recipient details, or reference a saved template to reuse its roles and field layout. The API can send the envelope as part of creation or leave it as a draft. Store the returned envelope identifier against your customer, supplier or onboarding record so the two systems remain connected.

Read the envelope to follow its status and individual recipients, then download the current PDF. Check that the envelope is completed before treating the download as a fully signed agreement: an in-progress document can contain only the signatures collected so far. This distinction keeps downstream teams from acting on an unfinished record.

React to events and verify the outcome

Webhook subscriptions let your application respond to events such as an envelope being sent, signed or completed. Deliveries are signed and retried by TrustInk’s worker. Verify the webhook signature, handle repeated deliveries safely and use the envelope API to confirm the current state before making an important downstream change.

For a signing experience within your product, retrieve the recipient’s embedded signing URL. Embedded signing must first be enabled for your approved application origins; coordinate that setup before placing the signing page in an iframe. Treat the link as sensitive and give it only to the intended person. A browser completion message can update the interface; the server-side envelope record should determine whether the business process proceeds.

Test the lifecycle before sending real requests

Use a sandbox API key to exercise envelope creation, signing and completion without real recipient emails or consuming live sending quota. Sandbox envelopes still produce documents, audit records and webhook events, so route your test activity to an appropriate receiving endpoint.

API access and webhook configuration are included on Business and Unlimited plans. Live sending also requires a verified sending domain and available plan capacity. Keep API keys on your server, separate test and live credentials, and revoke a key when an integration no longer needs access.

Support repeat and self-service journeys

For a batch of individual agreements, the bulk endpoint creates a separate envelope for each recipient from a single-recipient template. Read each result rather than assuming the whole batch succeeded. For a reusable public starting point, create a PowerForm that collects a visitor’s details and starts their own signing request.

REST hooks also provide the building blocks for automation services such as Zapier or Make. These are API integration capabilities; the exact workflow, field mapping and error handling need to be configured for your application.

Common questions