---
title: "Recipient events"
description: "Monitor recipient actions and status changes including signing, bounces, and replacements."
canonical: "https://signatureapi.com/docs/api/resources/events/recipient-events"
source: "https://signatureapi.com/docs/api/resources/events/recipient-events.md"
last_verified_api_version: "1.18.0"
last_modified: "2026-11-18T12:10:02Z"
---

# Recipient events

Monitor recipient actions and status changes including signing, bounces, and replacements.

_Last verified against API version 1.18.0._

Recipient events track key actions and status changes for recipients within an envelope. This page describes each event type, when it fires, and the additional data included in the payload.

> **Tip:** In test mode, send an example event to your webhook handler with the CLI: `npx signatureapi trigger recipient.completed`. See [CLI webhooks](https://signatureapi.com/docs/cli/webhooks).

## recipient.released

Fires when a recipient becomes ready to receive an invitation. The recipient status changes to `pending`.

Power Automate trigger: [When a recipient is released](https://signatureapi.com/docs/integrations/power-automate/triggers/recipient-released).

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

```json JSON
{
    "id": "evt_1a2b3c4d5e6f7g8h9i0j",
    "type": "recipient.released",
    "timestamp": "2025-12-31T23:59:59.999Z",
    "data": {
        "object_id": "re_00ZeZjRaXCgT30n1eBx53N",
        "object_type": "recipient",
        "envelope_id": "eb4cf433-a8af-4161-b37b-7ef57d423e56",
        "envelope_metadata": {
            "deal_id": "50055",
            "deal_owner": "Jane C."
        },
        "recipient_type": "signer",
        "recipient_key": "client"
    }
}
```

## recipient.sent

Fires when SignatureAPI has sent the invitation email to a recipient whose ceremony uses `email_link` authentication. It means the email was sent, not that it reached the inbox: a bounce arrives later as [`recipient.soft_bounced`](https://signatureapi.com/docs/api/resources/events/recipient-events#recipientsoft_bounced) or [`recipient.hard_bounced`](https://signatureapi.com/docs/api/resources/events/recipient-events#recipienthard_bounced).

Power Automate trigger: [When a recipient is sent](https://signatureapi.com/docs/integrations/power-automate/triggers/recipient-sent).

When the ceremony uses another authentication method, SignatureAPI sends no invitation email and you deliver the ceremony URL yourself. The event then fires when the ceremony becomes active.

#### Example payload

```json JSON
{
    "id": "evt_2b3c4d5e6f7g8h9i0j1k",
    "type": "recipient.sent",
    "timestamp": "2025-12-31T23:59:59.999Z",
    "data": {
        "object_id": "re_00ZeZjRaXCgT30n1eBx53N",
        "object_type": "recipient",
        "envelope_id": "eb4cf433-a8af-4161-b37b-7ef57d423e56",
        "envelope_metadata": {
            "deal_id": "50055",
            "deal_owner": "Jane C."
        },
        "recipient_type": "signer",
        "recipient_key": "client"
    }
}
```

## 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.

The `data` 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.

> **Note:** 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

```json JSON
{
    "id": "evt_2b3c4d5e6f7g8h9i0j1k",
    "type": "recipient.accessed",
    "timestamp": "2025-12-31T23:59:59.999Z",
    "data": {
        "object_id": "re_00ZeZjRaXCgT30n1eBx53N",
        "object_type": "recipient",
        "envelope_id": "eb4cf433-a8af-4161-b37b-7ef57d423e56",
        "envelope_metadata": {
            "deal_id": "50055",
            "deal_owner": "Jane C."
        },
        "recipient_type": "signer",
        "recipient_key": "client",
        "ip": "123.122.990.22",
        "user_agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36",
        "session_id": "ses_2X6eHBCL84MDGrLQX0mHI72"
    }
}
```

## 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.

The `data` object includes a `session_id`. Use it to correlate multiple events from the same ceremony session.

#### Example payload

```json JSON
{
    "id": "evt_2b3c4d5e6f7g8h9i0j1k",
    "type": "recipient.viewed",
    "timestamp": "2025-12-31T23:59:59.999Z",
    "data": {
        "object_id": "re_00ZeZjRaXCgT30n1eBx53N",
        "object_type": "recipient",
        "envelope_id": "eb4cf433-a8af-4161-b37b-7ef57d423e56",
        "envelope_metadata": {
            "deal_id": "50055",
            "deal_owner": "Jane C."
        },
        "recipient_type": "signer",
        "recipient_key": "client",
        "session_id": "ses_2X6eHBCL84MDGrLQX0mHI72"
    }
}
```

## recipient.completed

Fires when a recipient finishes all required actions in the ceremony. The recipient status changes to `completed`.

Power Automate trigger: [When a recipient is completed](https://signatureapi.com/docs/integrations/power-automate/triggers/recipient-completed).

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

```json JSON
{
    "id": "evt_3c4d5e6f7g8h9i0j1k2l",
    "type": "recipient.completed",
    "timestamp": "2025-12-31T23:59:59.999Z",
    "data": {
        "object_id": "re_00ZeZjRaXCgT30n1eBx53N",
        "object_type": "recipient",
        "envelope_id": "eb4cf433-a8af-4161-b37b-7ef57d423e56",
        "envelope_metadata": {
            "deal_id": "50055",
            "deal_owner": "Jane C."
        },
        "recipient_type": "signer",
        "recipient_key": "client",
        "session_id": "ses_2X6eHBCL84MDGrLQX0mHI72"
    }
}
```

## recipient.rejected

Fires when a recipient declines the envelope. A rejection does not cancel the envelope. To move on, either [replace the recipient](https://signatureapi.com/docs/api/resources/recipients/replace) or [cancel the envelope](https://signatureapi.com/docs/api/resources/envelopes/cancel), through the API or the Dashboard.

Power Automate trigger: [When a recipient rejects](https://signatureapi.com/docs/integrations/power-automate/triggers/recipient-rejected).

The `data.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

```json JSON
{
    "id": "evt_4d5e6f7g8h9i0j1k2l3m",
    "type": "recipient.rejected",
    "timestamp": "2025-12-31T23:59:59.999Z",
    "data": {
        "object_id": "re_00ZeZjRaXCgT30n1eBx53N",
        "object_type": "recipient",
        "envelope_id": "eb4cf433-a8af-4161-b37b-7ef57d423e56",
        "envelope_metadata": {
            "deal_id": "50055",
            "deal_owner": "Jane C."
        },
        "recipient_type": "signer",
        "recipient_key": "client",
        "reason": "Not the terms we agreed to on June.",
        "session_id": "ses_2X6eHBCL84MDGrLQX0mHI72"
    }
}
```

## recipient.soft\_bounced

Fires when the invitation email is temporarily undeliverable. The recipient status changes to `soft_bounced`. Common causes include a full mailbox or a temporary server issue.

Power Automate trigger: [When a recipient bounces](https://signatureapi.com/docs/integrations/power-automate/triggers/recipient-bounced).

The `data.detail` property contains the bounce reason from the remote email server. Use the [Resend Request](https://signatureapi.com/docs/api/resources/recipients/resend) endpoint to try delivering the invitation again.

#### Example payload

```json JSON
{
    "id": "evt_5e6f7g8h9i0j1k2l3m4n",
    "type": "recipient.soft_bounced",
    "timestamp": "2025-12-31T23:59:59.999Z",
    "data": {
        "object_id": "re_00ZeZjRaXCgT30n1eBx53N",
        "object_type": "recipient",
        "envelope_id": "eb4cf433-a8af-4161-b37b-7ef57d423e56",
        "envelope_metadata": {
            "deal_id": "50055",
            "deal_owner": "Jane C."
        },
        "recipient_type": "signer",
        "recipient_key": "client",
        "detail": "Server 123.122.990.22 responded with: Mailbox Full"
    }
}
```

## recipient.hard\_bounced

Fires when the invitation email is permanently undeliverable. The recipient status changes to `hard_bounced`. Common causes include an invalid or nonexistent email address.

Power Automate trigger: [When a recipient bounces](https://signatureapi.com/docs/integrations/power-automate/triggers/recipient-bounced).

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.

> **Note:** After a hard bounce, you cannot resend to this recipient. Use the [Replace Recipient](https://signatureapi.com/docs/api/resources/recipients/replace) endpoint to assign a new person with a valid email address.

#### Example payload

```json JSON
{
    "id": "evt_6f7g8h9i0j1k2l3m4n5o",
    "type": "recipient.hard_bounced",
    "timestamp": "2025-12-31T23:59:59.999Z",
    "data": {
        "object_id": "re_00ZeZjRaXCgT30n1eBx53N",
        "object_type": "recipient",
        "envelope_id": "eb4cf433-a8af-4161-b37b-7ef57d423e56",
        "envelope_metadata": {
            "deal_id": "50055",
            "deal_owner": "Jane C."
        },
        "recipient_type": "signer",
        "recipient_key": "client",
        "detail": "Permanent/General, diagnostic code: smtp; 550 5.1.1 As requested: user unknown"
    }
}
```

## recipient.failed

Fires when an error prevents the invitation from being sent to a recipient. The recipient status changes to `failed`.

Power Automate trigger: [When a recipient fails](https://signatureapi.com/docs/integrations/power-automate/triggers/recipient-failed).

The `data.detail` property contains a description of the failure, such as the recipient's email being on a blocklist.

> **Note:** You may need to use the [Replace Recipient](https://signatureapi.com/docs/api/resources/recipients/replace) endpoint to assign a different person.

#### Example payload

```json JSON
{
    "id": "evt_7g8h9i0j1k2l3m4n5o6p",
    "type": "recipient.failed",
    "timestamp": "2025-12-31T23:59:59.999Z",
    "data": {
        "object_id": "re_00ZeZjRaXCgT30n1eBx53N",
        "object_type": "recipient",
        "envelope_id": "eb4cf433-a8af-4161-b37b-7ef57d423e56",
        "envelope_metadata": {
            "deal_id": "50055",
            "deal_owner": "Jane C."
        },
        "recipient_type": "signer",
        "recipient_key": "client",
        "detail": "Recipient in email blocklist."
    }
}
```

## recipient.replaced

Fires when a recipient is replaced through the [Replace Recipient](https://signatureapi.com/docs/api/resources/recipients/replace) endpoint. The original recipient's status changes to `replaced`.

Power Automate trigger: [When a recipient is replaced](https://signatureapi.com/docs/integrations/power-automate/triggers/recipient-replaced).

The `data` object includes `new_recipient_id` and `new_recipient_name` identifying the replacement recipient.

#### Example payload

```json JSON
{
    "id": "evt_8h9i0j1k2l3m4n5o6p7q",
    "type": "recipient.replaced",
    "timestamp": "2025-12-31T23:59:59.999Z",
    "data": {
        "object_id": "re_00ZeZjRaXCgT30n1eBx53N",
        "object_type": "recipient",
        "envelope_id": "eb4cf433-a8af-4161-b37b-7ef57d423e56",
        "envelope_metadata": {
            "deal_id": "50055",
            "deal_owner": "Jane C."
        },
        "recipient_type": "signer",
        "recipient_key": "client",
        "new_recipient_id": "re_5SfFjI3eVfDokAXXDSjJlz",
        "new_recipient_name": "John Doe"
    }
}
```

## recipient.resent

Fires when the invitation email is resent to a recipient via the [Resend Request](https://signatureapi.com/docs/api/resources/recipients/resend) endpoint. The recipient status remains `sent`.

Power Automate trigger: [When a recipient is resent](https://signatureapi.com/docs/integrations/power-automate/triggers/recipient-resent).

#### Example payload

```json JSON
{
    "id": "evt_9i0j1k2l3m4n5o6p7q8r",
    "type": "recipient.resent",
    "timestamp": "2025-12-31T23:59:59.999Z",
    "data": {
        "object_id": "re_00ZeZjRaXCgT30n1eBx53N",
        "object_type": "recipient",
        "envelope_id": "eb4cf433-a8af-4161-b37b-7ef57d423e56",
        "envelope_metadata": {
            "deal_id": "50055",
            "deal_owner": "Jane C."
        },
        "recipient_type": "signer",
        "recipient_key": "client"
    }
}
```
