Embedded sending lets users add and position fields on documents without leaving your application. Signable provides the document setup page as an embeddable URL, so you do not need to build and maintain your own drag-and-drop field editor.
Embedded sending currently covers the "Add fields" step (green box) of the Envelope Send Flow (all boxes). In future, it will expand to cover the entire envelope sending flow.
Your application controls the rest of the sending journey. You create the draft envelope and its parties through the API, display Signable's document setup page in an iframe, and send the completed draft when your user is ready.
In the embedded document setup page, users can:
- Preview every document in the envelope
- Add fields to a document
- Assign fields to the parties already created through the API
- Move, resize, edit, and remove fields
- Your server creates a draft envelope with at least one document and one party.
- Your server creates a short-lived embed session for the draft.
- Signable returns a
session_url. - Your application loads the URL in an iframe.
- The user positions and configures fields in Signable's document setup page.
- Your application asks the user to review any details you manage outside the iframe.
- Your server sends the prepared envelope through the API.
Embedded sending provides the document setup interface. Your integration remains responsible for the steps before and after it.
| Your application | Embedded document setup |
|---|---|
| Upload documents when creating the draft | Display documents |
| Create parties and set their names, email addresses, roles, messages, passwords, and mobile numbers | Add and position fields |
| Configure signing order, OTP, reminders, expiry, and other envelope settings | Assign fields to existing parties |
| Provide review, confirmation, and error states | Save field changes |
| Send the completed draft | — |
Over time, embedded sending will expand to support the entire envelope sending journey, from document upload through to reviewing an envelope summary and sending the envelope.
To introduce these enhancements incrementally, Create an embed session includes a config parameter. It currently only supports a component value of document_setup. As we add functionality, new values will become available. We’ll announce these enhancements in advance through our changelog, giving you time to plan for and adopt them at your own pace.
What would you like to see next for embedded sending? Submit a feature request.
Create draft envelopes and embed sessions from your server. Never expose your Signable API key in browser code.
An embed session URL contains a short-lived credential and expires after 120 seconds. Treat it as sensitive, avoid logging it, and load it promptly. Create a new session if the URL expires before the embedded page loads.
When the URL is loaded, the embedded application securely exchanges the session token for a JSON Web Token (JWT). The JWT authenticates subsequent requests made by the embedded document setup page, so your API key is never exposed to the browser or iframe. The session expires after 60 minutes.
- Embed document setup in your application – Implement the create draft, embed and send flow.