recipient.released
Fires when a recipient becomes ready to receive an invitation. The recipient status changes topending.
This event fires after all previous recipients in the routing order have completed, or immediately for the first recipient when the envelope starts.
Example payload
Example payload
JSON
recipient.sent
Fires when SignatureAPI sends the invitation email to a recipient. The recipient status changes tosent.
This event only fires for recipients with delivery_type set to email.
Example payload
Example payload
JSON
recipient.accessed
Fires when a recipient opens the ceremony URL. To reduce duplicate events, this fires at most once every 60 seconds for the same IP address and user agent combination. The recipient has not yet authenticated at this point. Thedata object includes the recipient’s ip address, user_agent, and a session_id. Use session_id to correlate multiple events from the same ceremony session.
Some security platforms access the ceremony URL to prefetch content or scan for threats. These requests can trigger
recipient.accessed before the intended recipient opens the link. To confirm that the human recipient has accessed the ceremony, use the recipient.viewed event instead.Example payload
Example payload
JSON
recipient.viewed
Fires after a recipient authenticates and the documents are displayed in the ceremony. This confirms the recipient passed all authentication steps and can view the documents. Thedata object includes a session_id. Use it to correlate multiple events from the same ceremony session.
Example payload
Example payload
JSON
recipient.completed
Fires when a recipient finishes all required actions in the ceremony. The recipient status changes tocompleted.
For signers, this means they have signed and finalized. For approvers and preparers, this means they have reviewed and submitted their inputs.
The data object includes a session_id. Use it to correlate multiple events from the same ceremony session.
Example payload
Example payload
JSON
recipient.rejected
Fires when a recipient declines the envelope. When a recipient rejects, the entire envelope is voided. Thedata.reason property contains the recipient’s explanation if they provided one. It is an empty string if no reason was given. The data object also includes a session_id.
Example payload
Example payload
JSON
recipient.soft_bounced
Fires when the invitation email is temporarily undeliverable. The recipient status changes tosoft_bounced. Common causes include a full mailbox or a temporary server issue.
The data.detail property contains the bounce reason from the remote email server. Use the Resend Request endpoint to try delivering the invitation again.
Example payload
Example payload
JSON
recipient.hard_bounced
Fires when the invitation email is permanently undeliverable. The recipient status changes tohard_bounced. Common causes include an invalid or nonexistent email address.
The data.detail property contains the bounce reason from the remote email server. You can view further details, such as SMTP responses, in the Dashboard.
After a hard bounce, you cannot resend to this recipient. Use the Replace Recipient endpoint to assign a new person with a valid email address.
Example payload
Example payload
JSON
recipient.failed
Fires when an error prevents the invitation from being sent to a recipient. The recipient status changes tofailed.
The data.detail property contains a description of the failure, such as the recipient’s email being on a blocklist.
You may need to use the Replace Recipient endpoint to assign a different person.
Example payload
Example payload
JSON
recipient.replaced
Fires when a recipient is replaced through the Replace Recipient endpoint. The original recipient’s status changes toreplaced.
The data object includes new_recipient_id and new_recipient_name identifying the replacement recipient.
Example payload
Example payload
JSON
recipient.resent
Fires when the invitation email is resent to a recipient via the Resend Request endpoint. The recipient status remainssent.
Example payload
Example payload
JSON