API Agreement Statuses, Recipient Statuses, Agreement Events, and Webhook Events
Last update: Apr 06, 2023.
Most states relate to specific Adobe Sign "roles".
PDF reference available here.
STATUSES
Status
Status meaning/description
OUT_FOR_SIGNATUREWaiting for Signature by one or more Signers
OUT_FOR_DELIVERYWaiting for acceptance by "Certified Recipient" (non-signer)
OUT_FOR_ACCEPTANCEWaiting for acceptance by "Acceptor" (non-signer)
OUT_FOR_FORM_FILLINGWaiting for "form filler" recipient to fill out data in fields (non-signer)
OUT_FOR_APPROVALWaiting for "Approver" to approve (non-signer)
AUTHORINGAgreement not yet finished with "authoring" so not yet sent to 1st recipient
ABORTEDCancelled (by sender) OR rejected (by recipient) — Terminal State
CANCELLEDCancelled (by sender) OR rejected (by recipient) — Legacy status, now = ABORTED — Terminal State
SIGNEDCompleted "signed" — Terminal State
APPROVEDCompleted "approved" — Terminal State
DELIVEREDCompleted by "Certified Recipient" — Terminal State
ACCEPTEDCompleted by "Acceptor" — Terminal State
FORM_FILLEDFilled out by "Form filler"
EXPIREDAgreement has passed "Expiration Date/Time" — Terminal State
ARCHIVEDApplies only to files "archived" to Adobe Sign for secure storage — Terminal State
PREFILLWaiting to be pre-filled by sender
WIDGET_WAITING_FOR_VERIFICATIONIf email verification is on, signed web-forms (widgets) must have signer verify email address provided during signing before agreement is "complete"/fully executed
DRAFTA "stub record" state where no doc conversion has taken place so there is not yet an "authoring" or signing experience but you can change any related data before starting the steps to create an agreement. There is an agreement ID (stubbed) and associated data but nothing else has happened. Agreements in this state can be deleted without incurring a transaction.
DOCUMENTS_NOT_YET_PROCESSEDRequest has been made to create an agreement but Adobe Sign is still working on processing the docs for the agreement.
WAITING_FOR_FAXINWhen agreement has been sent and forced WRITTEN. This status references legacy "Faxin" feature now deprecated but is still used for "written" (print, wet-sign, scan and upload) transactions.
WAITING_FOR_VERIFICATIONOLD status same as WIDGET_WAITING_FOR_VERIFICATION
Status related to recipients
Status
Status meaning/description
COMPLETEDYour required action is complete
CANCELLEDYou (or someone before you in the recipient order) has cancelled the agreement
EXPIREDThe agreement expired while waiting for you to take the required action
NOT_YET_VISIBLERecipients before you have not finished their required action/s
WAITING_FOR_OTHERSRecipients after you still need to take their required actions
WAITING_FOR_MY_APPROVALYou are the current recipient (APPROVER) and need to approve
WAITING_FOR_AUTHORINGYou are the current sender and need to finish the authoring step and set the agreement to IN_PROCESS
WAITING_FOR_MY_ACKNOWLEDGEMENTYou are the current recipient (CERTIFIED_RECIPIENT) and need to Acknowledge your receipt
WAITING_FOR_MY_ACCEPTANCEYou are the current recipient (ACCEPTOR) and need to Accept
WAITING_FOR_MY_FORM_FILLINGYou are the current recipient (FORM_FILLER) and need to fill out the fields
WAITING_FOR_MY_DELEGATIONYou are the current recipient (DELEGATOR) and need to delegate the agreement to someone
WAITING_FOR_MY_SIGNATUREYou are the current recipient (SIGNER) and need to sign
WAITING_FOR_MY_VERIFICATIONYou have signed a web form (widget) but have not completed the post signing email verification step
WAITING_FOR_PREFILLYou are the 1st recipient where the sender has marked fields to be pre-filled (by her/him) but has not finished prefilling and sending
Agreement Events
Event Name
Description of Event
Status Change
CREATEDWhen an agreement or Draft is created
A new resource with DRAFT status or AUTHORING or with one of the OUT_FOR_ status depending on the participants roles.
AGREEMENT_MODIFIEDAgreement modified by sender modify document in flight
No change in the status.
USER_ACK_AGREEMENT_MODIFIEDWhen signer acknowledges modification before signing
No change in the status.
ESIGNEDWhen agreement is signed
Either change in status based on the next participants role if there are more recipients or the status changes to SIGNED.
DIGSIGNEDWhen agreement is digitally signed
Either change in status based on the next participants role if there are more recipients or the status changes to SIGNED.
APPROVEDWhen agreement is approved
Either change in status based on the next participants role if there are more recipients or the status changes to one of SIGNED or APPROVED.
ACCEPTEDWhen agreement is accepted
Either no change in status if there are more recipients or the status changes to one of SIGNED, APPROVED or ACCEPTED.
DELIVEREDWhen agreement is delivered
Either no change in status if there are more recipients or the status changes to one of SIGNED, APPROVED, ACCEPTED, FORM_FILLED or DELIVERED.
FORM_FILLEDWhen agreement is filled
Either no change in status if there are more recipients or the status changes to one of SIGNED, APPROVED, ACCEPTED or FORM_FILLED.
ABORTEDWhen agreement is cancelled or rejected
Status changes to ABORTED.
EXPIREDWhen agreement is expired
Status changes to EXPIRED.
RECALLEDWhen agreement is recalled by sender
Status changes to ABORTED.
DELEGATEDWhen participant delegates to someone else
No change in status.
REPLACED_SIGNERWhen a participant is replaced
No change in status.
AUTO_CANCELLED_CONVERSION_PROBLEMWhen the documents cannot be converted successfully
Status changes to ABORTED.
Webhook Events
Webhook events follow the same naming conventions as Agreement Events but are delivered as HTTP POST payloads to your configured webhook endpoint. Key notes:
- Webhook payloads include the full agreement details at the time of the event.
- Partners should use per-agreement (resource-level) webhooks rather than account-level webhooks. See Webhooks for Partner Integrations for details.
- For the complete webhook event reference, see the Webhook Reference.
© Copyright 2023, Adobe Inc.. Last update: Apr 06, 2023.