Decline to sign
Closes the document with status "declined", records the reason in the audit trail, and emails the owner. Needs the access code when the recipient has one. Phone verification is also required. A recipient who must pass a Government ID check can decline without having passed it, so a stranger sent someone else's link can say "this is not for me" without handing a government ID to a third party; the audit line then says the decline came without identity verification.
View as MarkdownPath Parameters
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/public/signing/string/decline" \ -H "Content-Type: application/json" \ -d '{}'{ "status": "string"}Fill fields and sign
One atomic action: writes the signer's field values, applies their PNG data-URL signature, records ESIGN consent (required), and advances the document — enforcing turn order, validating required fields, and rejecting values for fields that aren't theirs. When the last signer completes, the final PDF is built (signatures stamped, certificate appended) and everyone is emailed.
Reassign this slot to someone else
Hands the signing slot to a different person, with a reason: the recipient row is updated in place to the new name/email and a fresh token is minted, the original invitee is preserved (reassignedFromName/Email on the recipient), the substitution is recorded in the audit trail, the new signer is emailed their own signing link, and the document owner is notified. One hop only — a slot that has already been reassigned once cannot be reassigned again — and not available on a signer-group slot (EAS-125; a group member steps back by declining instead).