Use Case:

-For existing sign requests, we need to retrieve the embedded signing URL.

-For new sign requests, we need both:

-The embedded signing experience (embed_url_external_user_id)

-The email notification sent to the signer

Issue:

When we include the embed_url_external_user_id parameter in the request payload (to generate the embedded signing link), the email notification to the signer is not sent.

-No errors are returned in the API response

-The sign request is created successfully

-The embedded URL is generated and works

-But no email is triggered to the signer

Expected Behavior:

-When creating a new sign request and providing embed_url_external_user_id, we expect:

-The signer to receive the standard email notification

-The embedded URL to be available as an alternative signing option

Request for Clarification:

-Is it expected behavior that enabling embed_url_external_user_id suppresses the email notification?

-Is there any way to enable both embedded signing and email notification simultaneously?

-If not, is there an alternative method to manually trigger the email without duplicating the sign request?

This is currently blocking our final signature flow implementation, and we would appreciate urgent clarification or workaround suggestions.