Leah Breen

July Developer Ask Me Anything (AMA): Customizing the embedded signing & sending experience with Docusign APIs

Forum|Forum|1 year ago
July 9, 2025
14 replies
1550 views

👋 Hey developers! Have questions about embedding Docusign into your app? We’re giving you the chance to ask your questions async-style in this AMA thread, open now through July 31. When you comment with a question, you’ll be automatically entered into a sweepstakes to choose a $100 gift 🎁

Whether you’re getting started or looking to fine-tune your implementation, this is your opportunity to get answers directly from Paige Rossi, Lead Developer Advocate on the Docusign Developer Content team.

🔧 Topic for this AMA: Embedding Docusign eSignature into your app

A clunky signing experience—like redirecting users to their inbox—can hurt completion rates.

With embedded signing and sending, you can keep everything in-app and streamline the user experience. The right API implementation can boost completion rates and improve UX.

If you’ve been wondering how to create a smooth, in-app signing experience, this AMA is for you.

🧠 Ask Paige about:

How to embed Docusign eSignature into your apps using the eSignature REST API
The difference between embedded signing and embedded sending
When and how to use focused view to embed Docusign without redirecting to a separate URL
Customization tips that make embedded sending feel native

💬 How to participate:

Drop your questions below through July 31
Paige will reply directly in the thread and tag @paige.rossi
No question is too small—this is a space to learn!
🎁 Bonus! Comment in the AMA thread and you’ll be automatically entered into a drawing to win a $100 Loop & Tie gift. If you’re selected, you get to choose from a curated collection of gifts—think alpaca throw blankets, premium coffee bundles, and more—then have it shipped straight to your door. (The terms & conditions can be viewed here.) Note: To be eligible, your reply must be relevant to the AMA topic. Off-topic questions may be moved by moderators and may not qualify as entries.

💡Not sure what to ask? Try asking:

What’s the difference between embedded signing and embedded sending?
How do I decide when to use embedded signing vs remote signing?
How can I embed the Docusign experience without redirecting to a new URL?
How can I make the signing experience match my app’s branding?
Why should I use embedded signing instead of simply embedding the envelope in an iframe?

📌 Reminder:
This AMA is for general questions about Docusign’s APIs and implementation best practices. For account-specific issues, reach out to Support. For feature requests, drop them in the Ideas section.

Let’s build better signing experiences—ask away 👇

This topic has been closed for replies.

Show previous replies

paige.rossi

Docusign Employee

Question about the frameAncestors property, it is possible to use wild cards? I ask because we have some temporary environments for testing and would help to have the recipient URL created to [*.mydomain.com] instead of [first.mydomain.com, second.mydomain.com, dude.mydomain.com, ...]

@MoisesW Unfortunately we don't support wildcards in that property right now due to strict requirements from some customers around CSP. I’ve made our development team aware of this question though so they can note this feedback.

M

Maneesha

New Voice

Hi @pagie.rossi,

We have a use case where senior management users prefer not to leave the source system for signing documents. To accommodate this, we’ve implemented an embedded signing button.

However, as soon as we add the clientUserId parameter to enable embedded signing, the recipient is treated as a captive recipient. This causes a problem: even though the user has an active DocuSign account—with their signature styles and stamps already uploaded—the embedded signing experience does not link to their DocuSign account or retrieve their saved configurations.

Is there any way to associate a captive (embedded) recipient with a DocuSign user account so they can still use their saved signature, initials, and stamp settings during embedded signing?

paige.rossi

Docusign Employee

We have a use case where senior management users prefer not to leave the source system for signing documents. To accommodate this, we’ve implemented an embedded signing button.
However, as soon as we add the clientUserId parameter to enable embedded signing, the recipient is treated as a captive recipient. This causes a problem: even though the user has an active DocuSign account—with their signature styles and stamps already uploaded—the embedded signing experience does not link to their DocuSign account or retrieve their saved configurations.
Is there any way to associate a captive (embedded) recipient with a DocuSign user account so they can still use their saved signature, initials, and stamp settings during embedded signing?

@Maneesha Unfortunately no, captive recipients are not able to be associated with a Docusign account during signing. If it’s more important for the signer to be able to use their stored signatures, remote signing may be the better option.

Gabriel.Hollandsworth

Docusign Alumni

That’s a wrap! 🎉

Thanks to everyone who participated in our async AMA on customizing the embedded signing and sending experience with Docusign APIs. We loved seeing your questions and hope Paige’s answers helped you get one step closer to building a smoother signing experience in your app.

🔒 This thread is now closed to new comments, but you can still read through the Q&A anytime.

🎁 If you dropped a question in the thread, you’re automatically entered into the drawing for a $100 Loop & Tie gift—we’ll contact the winner shortly.

Thanks again for being part of the Docusign Community!

Thank you for being part of the Docusign Community!

🔧 Topic for this AMA: Embedding Docusign eSignature into your app

🧠 Ask Paige about:

💬 How to participate:

💡Not sure what to ask? Try asking:

Sign up

You can login or register as either a Docusign customer or developer. If you don’t already have a Docusign customer or developer account, you can create one for free when registering.

Docusign Community

You can login or register as either a Docusign customer or developer. If you don’t already have a Docusign customer or developer account, you can create one for free when registering.