We use Zoho CRM and Zoho Sign in the EU data center, with the official Zoho Sign extension installed.

Our goal is to start embedded signing from a CRM record, let the customer sign on a tablet without a Sign login, and retain automatic document linking and status updates in CRM.

Routes tested:

1. Existing integrated routes — CRM synchronization works

• POST /crm/v8/Sales_Orders/{record_id}/actions/sign_mail_merge

• Writer mergeAndSign / POST /writer/api/v1/documents/{document_id}/merge/sign, using a CRM Mail Merge template, record_id, service_name=zohosign, and signer_data with action_type=in_person_sign.

2. Direct embedded route — signing works, native CRM synchronization does not

• Writer POST /documents/{document_id}/merge with record_id and output_settings={"format":"pdf"}.

• Sign create and submit through CRM Deluge’s zoho.sign.createDocument and zoho.sign.submitRequest, using action_type=SIGN, is_embedded=true, recipient name/email, and email_reminders=false.

• POST /api/v1/requests/{request_id}/actions/{action_id}/embedtoken.

• Signing completes, but no corresponding record appears in CRM’s zohosign__ZohoSign_Documents module.

3. Embedded signing through Writer

• Top-level is_embedded=true returns R5012: unsupported parameter.

• Adding it inside signer_data does not produce an embedded in-person action; /embedtoken returns 2009: Action is not embedded.

Is there a supported API route or parameter set that combines embedded signing with the official CRM extension’s automatic synchronization?

Can a directly created Sign request be registered with that integration, or must API-created embedded requests always use a separate webhook/callback for CRM synchronization?