Embedded vs Non-Embedded with the Dropbox Sign API

With the Dropbox sign API, there are two choices when completing signature requests: non-embedded signing and embedded signing.

What is non­-embedded signing?

With non-­embedded signing, your users sign documents on sign.dropbox.com. We notify the signer via email and collect their eSignature on Dropbox sign. We also send signature request reminders to the signer. Documentation can be found here.

What is embedded signing?

With embedded signing, users sign directly on your site instead of being redirected to sign.dropbox.com. Simply display the document to the user at any time using a secure iframe. It's completely seamless and the user doesn't even need to have a Dropbox sign account. Take a look at our premium branding guide to learn more about customizing your app's embedded signing.

What is non-­embedded requesting?

The signature request walkthrough can be found here.

What is embedded requesting?

Embedded requesting allows you to have users create and send signature requests on your site in an iFrame. Documentation can be found here.

What are embedded templates?

Embedded templates allow your users to create and edit templates on your site in an iFrame.

Templates are a great time-saving tool used to quickly create signature requests based on frequently­ used documents. A W4 tax form is a good example, where the form stays the same for all signers.

Documentation can be found here.