Skip to content
Last updated

Embedded signing lets you control how signers access envelopes. Instead of Signable sending emails to signers, you receive the signing page URL and deliver it through your preferred channel.

Embed signing in your application, send links from your email domain, or deliver signing URLs through SMS messages.

Display the signing page directly within your website or customer portal using an iframe or redirect.

Benefits:

  • Keeps signers in your branded environment
  • Integrates signing into existing workflows like account setup or checkout
  • Lets you add authentication before displaying documents
  • Eliminates redirects to external sites

Common implementations:

  • Customer onboarding portals
  • Account management dashboards
  • Mobile applications
  • Internal employee systems

How embedded signing works

Without embedded signing, Signable sends signing links and completion emails to all parties.

Embedded signing changes who delivers the signing link to your signers.

When you create an envelope with embedded signing enabled, you control link delivery:

  1. Your system sends an API request to create an envelope
  2. The API returns the signing page URL in the response
  3. You deliver the URL through your chosen channel (email, SMS, or embedded iframe)
  4. Signers access the signing page through your delivery method
  5. Signers complete the envelope on Signable's signing page
  6. Signable emails completed documents to all parties

Send API request with embedded signing enabled

Receive signing page URL in response

Deliver URL using your channel

Signer accesses signing page

Signer completes envelope

Signable sends completion emails

The primary difference is delivery control. With embedded signing, you retrieve the signing URL and deliver it through your systems rather than relying on Signable's automated emails.

Requirements

Embedded signing requires account setup and acknowledgement of identity verification responsibilities.

You need a paid Signable plan to use embedded signing. The feature is not available on free plans.

Identity assurance acknowledgement

You must sign Signable's Identity Assurance Acknowledgement form before using embedded signing. This form confirms you accept responsibility for verifying signer identities when you control access to signing pages.

After you sign the acknowledgement form, contact the Signable Customer Success team to enable embedded signing on your account.

Technical implementation

Your development team must integrate with the Signable API to:

  • Create envelopes with the embedded signing parameter
  • Extract signing URLs from API responses
  • Implement your chosen delivery method (iframe embedding, email sending, or SMS delivery)
  • Handle signing completion webhooks