SignatureAPI has added two new recipient event types, recipient.accessed and recipient.viewed, giving you finer-grained visibility into what recipients do between opening a signing request and completing the ceremony. If you build dashboards, reminders, or analytics on top of recipient activity, these events close a real gap in the timeline.
The New Events
recipient.accessedfires when a recipient enters the signing ceremony. It includes the recipient’s IP address and user agent, which is useful for audit logs, fraud signals, and understanding which device or browser the recipient is using.recipient.viewedfires when the recipient has completed any required authentication and the documents are actually being displayed. This is the moment the recipient is looking at the content, rather than simply having clicked through to the ceremony.
Together, these two events let you distinguish between “opened the link” and “actually started reviewing the documents,” which matters for nudge campaigns, compliance trails, and conversion analysis.
Session Correlation
Ceremony events now also include a session_id, so you can group related activity from the same ceremony session across multiple events. This makes it easier to reconstruct exactly what happened in a single recipient visit.
For the full list of fields and examples, see the Recipient Events docs.