Headless SDK
Own every pixel of the signing experience while EndorsedSign manages state transitions, audit lineage, and delivery.
Embed vs headless — when to choose which
| Factor | Elements embed | Headless SDK |
|---|---|---|
| Integration time | Hours to days | Days to weeks |
| UI control | Brand-level config + theme prop | Complete — every element is yours |
| Framework support | React only | Any framework — state is framework-agnostic |
| Document rendering | Managed by EndorsedSign | You implement using the document URL |
| Field navigation | Managed by EndorsedSign | You implement using field metadata from SDK |
| State machine | Managed by EndorsedSign | Managed by EndorsedSign |
| Audit trail | Managed by EndorsedSign | Managed by EndorsedSign |
The headless SDK gives you more control. The tradeoff is that you own the rendering and interaction layer.
What the headless SDK provides
Signing state machine
The SDK exposes the current signing state — which fields are required, which are filled, what transitions are allowed. Your UI reacts to it.
Field metadata
Get the full field manifest: type, position, required status, current value. Render fields in your own components.
Submit and progress hooks
Call SDK methods to update field values, advance through the signing flow, and submit the completed signature.
Real-time status events
Subscribe to signing events — field filled, step completed, session expired — and update your UI accordingly.
Common questions
Build headless against a live sandbox
The headless path is the REST API + your own UI. Claim a sandbox in one call, then wire up your framework of choice.