One integration in front of the signing layer.
REST, embed, or headless — choose the integration depth you want. First-party clients, webhooks, and a sandbox for every partner.
Choose your integration depth
All three paths use the same backend. Pick based on how much of the signer UI you want to own.
| Path | You build | EndorsedSign manages | Best for |
|---|---|---|---|
| REST API + Elements embed | Your product shell; embed takes signer UI | Full signer flow, state machine, audit, delivery | Fast integration — live in hours |
| REST API + Headless SDK | Every pixel of the signer experience | Workflow state, audit lineage, delivery pipeline | Full UX control; complex product requirements |
| REST API only | Your own signer UI from scratch | State transitions, records, audit trail | You have strong frontend infra and want zero dependencies |
Most partners start with the Elements embed and migrate to headless only when a specific UI requirement cannot be met by embed configuration.
Integration surface
Every capability is accessible via API. The surfaces below are the most commonly used integration points.
REST API
Server calls use a tenant API key: confirm the key, create a document from a template, send it, and mint a signing-session token. Upload, the envelope wizard, and webhook registration stay in the admin app.
Learn more →Elements embed
Drop a React component into your product. Signing UI is rendered inside your page on your domain.
Learn more →Headless SDK
Own every pixel. EndorsedSign handles state transitions, audit, and delivery while your UI drives the experience.
Learn more →Client SDKs
TypeScript, Python, and .NET clients maintained alongside API behaviour. Typed request and response models.
Learn more →Webhooks
Real-time events for every signing transition. HMAC-signed, retried, replayable.
Learn more →Developer console
Inspect API calls and webhook deliveries. Replay failures. No log-trawling required.
Learn more →Claim a sandbox, mint an API key, and start building
Sandbox tenants are self-serve. One POST returns a tenant + an API key + a seeded demo signer — no early-access queue.