Signatures
Embedded Signing
Signing inside your own product. The embedded session, its states, and what the embedded signer sees.
Embedded signing puts Docshark's signing session inside your own product. The signer never leaves your app. It is for platforms embedding signature flows: onboarding, contracts inside a portal, in-app approvals.
How it works
- Your backend creates the envelope and requests an embedded signing session for a recipient.
- Docshark returns a session URL you load in an iframe or web view.
- The signer completes the same guided flow, consent, fields, finish, inside your chrome.
- Events flow back to you through webhooks (
ENVELOPE_VIEWED,ENVELOPE_SIGNED,ENVELOPE_COMPLETED, …) so your app reacts in real time.
Session states
The embedded view handles its own lifecycle. Your UI should expect:
- Loading. The session resolves; show your own spinner outside the frame.
- Identity confirmation. The signer confirms or verifies who they are.
- Consent / disclosure. The ESIGN screen, same as hosted signing.
- Review. The document opens; required fields block as usual.
- Decline. The signer can still refuse; the decline surfaces to you as an event.
- Completion. Finish returns the sealed outcome; the envelope detail carries the audit trail and sealed PDF as normal.
- Retry / error. Expired or invalid sessions produce a recoverable state; request a fresh session URL rather than reusing a dead one.
Sealed copies
Completed embedded envelopes behave identically to hosted ones. The sealed PDF and audit evidence live on the envelope record; fetch them through your integration or from the dashboard.
When to use it
- You own the customer relationship and want signing invisible inside your product.
- You need signing on a device or surface you control.
- You want envelope events driving your own state machine via webhooks.
For sending people to a hosted flow, the normal envelope email is simpler. Embedded is for when the signing screen must be yours.