Unique identifier assigned when the Order Entry transaction is created. Resolves to the internal transaction; caller must be authorized for this transaction.
Example:1064752
Returns DocuSign routing status per recipient for the specified transaction (after the case is in flight).
Path parameter: transactionId (required) — resolves to the internal transaction; the caller must be authorized for this transaction.
Response fields:
success — whether status rows were loadedsigners — array of rows: recipientId, signerName, signerStatus, signerEmail, dateOfAction, signerAuthMethod (Phone | SMS | None), signerCountryCode (default 1 for US), signerPhoneNo (digits only)signerStatus examples: Delivered, Needs to Sign, Needs to View, Waiting for Other Signer(s), Completed (Signed).
Unique identifier assigned when the Order Entry transaction is created. Resolves to the internal transaction; caller must be authorized for this transaction.
Example:1064752
Returns the signer status payload
True when signer status rows were retrieved successfully.
Per-recipient DocuSign status and contact details for the transaction.
Example:{"recipientId":"11306862","signerName":"EE EE1","signerStatus":"Needs to Sign","signerEmail":"anannya.gupta@zinnia.com","dateOfAction":"2026-01-12T14:22:00","signerAuthMethod":"Phone","signerCountryCode":"1","signerPhoneNo":"8650827071"}
Submits the Order Entry case to DocuSign using the supplied signer roster. Call GET /esignature/{transactionId} first to load available recipients, then POST the selected signer contact and auth details here to start the e-signature workflow.
Request body:
transactionId (required) — positive integer for the case to submitsigners (required) — at least one signer row with final routing detailsEach signer row: recipientId, signerName, signerEntityRole, signerEmail, signerSequence, signerAccessCode, signerAuthMethod (selected method, for example Phone), signerCountryCode, signerPhoneNo.
Response: success and message only (no signer list). message confirms submission when success is true.
Case submission payload: transaction to submit and the final DocuSign signer roster (selected auth method per signer).
Transaction (case) identifier to submit for e-signature.
>= 1
Final signer roster with selected auth method and contact details.
>= 1 items
Returns the case submission result envelope
True when the case was submitted to DocuSign for e-signature.
User-safe confirmation or failure text from the submission result.
Voids the in-flight DocuSign envelope for the case and updates case status to Pending in Order Entry.
Request body:
transactionId (required, string) — must be a positive integer string for the case to cancelResponse: success and message. When success is false, message explains the failure in user-safe terms.
Identifies the case whose e-signature ceremony should be canceled (void DocuSign; case returns to Pending).
String form of the transaction (case) id to cancel; must be a positive integer.
>= 1 characters
Returns the cancel result envelope
True when the DocuSign ceremony was voided and the case returned to Pending upstream.
User-safe message when success is false; may also confirm the outcome when true.
Asks Order Entry to resend the DocuSign signing notification for the case. Upstream AnnuityNet: POST RetriggerEsignatureEmail/{transactionId}. Only applies when e-signature is in progress; upstream returns success: false with a user-safe message otherwise.
Request body:
transactionId (required, string) — positive integer string for the caseResponse: success and message (for example, notification successfully triggered when success is true).
Identifies the case whose DocuSign signing notification should be resent (in-progress e-sign only).
String form of the transaction (case) id; must be a positive integer.
>= 1 characters
Returns the retrigger result envelope
True when the signing notification was retriggered (e-sign in progress upstream).
User-safe message; e.g. notification successfully triggered when success is true.
Corrects signer email and/or phone while e-signature is pending upstream. AnnuityNet: POST UpdateESignSignerDetails with the same request payload.
Request body:
transactionId (required) — positive integer for the casesigners (required) — at least one signer row with corrected contact detailsEach signer row: recipientId, signerEmail, signerSequence, signerAuthMethod (for example Phone), signerCountryCode, signerPhoneNo.
Response: success and message. When success is false, message explains the failure in user-safe terms.
Transaction ID and signer rows with corrected email and/or phone while e-signature is pending upstream.
Transaction (case) identifier whose signer contact details should be updated.
>= 1
Signer rows with corrected email and/or phone while e-sign is pending.
>= 1 items
Returns the update result envelope
True when signer contact details were updated (e-sign must be pending upstream).
User-safe message confirming the update or describing a failure.