> ## Documentation Index
> Fetch the complete documentation index at: https://signatureapi-daf4ee54.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Recipient

> The recipient object represents a person who participates in an envelope as a signer, approver, or preparer

A **recipient** is a person who receives and acts on an envelope. Every envelope must have at least one recipient.

Recipients have three types, each with a different role:

| Type                                                | Description                                                                                                       |
| --------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| [Signer](/docs/api/resources/recipients/signer)     | Reviews documents and adds a signature or initials. Every envelope must have at least one signer.                 |
| [Approver](/docs/api/resources/recipients/approver) | Reviews and approves documents without signing. Approver actions are not recorded in the audit log.               |
| [Preparer](/docs/api/resources/recipients/preparer) | Fills in document fields before signers receive the envelope. Preparer actions are not recorded in the audit log. |

Each recipient participates in the envelope through a **ceremony**, a guided session where they complete their assigned actions. A recipient's `status` tracks their progress through the workflow. See the [recipient lifecycle](/docs/api/resources/recipients/lifecycle) for details on each status and what triggers a transition.

A recipient belongs to an [envelope](/docs/api/resources/envelopes/object).

## Attributes

<Expandable title="Signer">
  <ResponseField name="id" type="string">
    The unique identifier of the recipient. Recipient IDs use the `re_` prefix.
  </ResponseField>

  <ResponseField name="envelope_id" type="string">
    The unique identifier of the envelope, in UUID format.
  </ResponseField>

  <ResponseField name="type" type="enum">
    The type of the recipient. Determines what actions the recipient can perform during the ceremony.

    | Type       | Description                                                    |
    | ---------- | -------------------------------------------------------------- |
    | `signer`   | Signs documents. Every envelope must have at least one signer. |
    | `approver` | Reviews and approves documents without signing.                |
    | `preparer` | Fills in document fields on behalf of another party.           |

    For signers, the type is `signer`.
  </ResponseField>

  <ResponseField name="key" type="string">
    A unique identifier you assign to each recipient in the envelope.

    Use it to match recipients with the places they should interact with (such as signature fields) and to identify them in events and webhook notifications.

    The key must start with a lowercase letter. It can contain lowercase letters, numbers, and underscores. Maximum 32 characters. It must be unique within the envelope.
  </ResponseField>

  <ResponseField name="name" type="string">
    The full name of the recipient. Appears in invitation emails and is pre-filled for typed signatures.
  </ResponseField>

  <ResponseField name="email" type="string">
    The email address of the recipient. Used to send invitation emails when `delivery_type` is `email`.
  </ResponseField>

  <ResponseField name="status" type="enum">
    The current status of the recipient in the signing workflow.

    | Status         | Description                                                                                                                               |
    | -------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
    | `pending`      | The envelope has not been sent to the recipient yet. This is the initial status.                                                          |
    | `awaiting`     | The recipient is waiting for earlier recipients in the routing order to complete.                                                         |
    | `sent`         | The invitation has been sent to the recipient.                                                                                            |
    | `completed`    | The recipient has completed their required actions (for example, signed or approved).                                                     |
    | `rejected`     | The recipient declined to complete the envelope.                                                                                          |
    | `soft_bounced` | The invitation email was temporarily undeliverable (for example, a full mailbox). You can resend the request.                             |
    | `hard_bounced` | The invitation email was permanently undeliverable (for example, an invalid address). Use the Replace endpoint to assign a new recipient. |
    | `failed`       | An error occurred and the invitation could not be sent.                                                                                   |
    | `replaced`     | This recipient was replaced with a new one via the Replace endpoint.                                                                      |
  </ResponseField>

  <ResponseField name="ceremony" type="object">
    The current [ceremony](/docs/api/resources/ceremonies/object) for the recipient.

    <Expandable title="Ceremony">
      <ResponseField name="authentication" type="array of authentication object">
        <Expandable title="Email Link Authentication">
          <div class="mt-4">
            With **email link authentication**, the recipient receives an email with a direct link to the ceremony. Clicking the link authenticates the recipient and opens the signing session.
          </div>

          <ResponseField name="type" type="enum">
            The type of authentication. Available values: `email_link`, `email_code`, and `custom`.

            For email link authentication, this value is `email_link`.
          </ResponseField>

          <ResponseField name="subject_override" type="string | null">
            The custom subject line used for this recipient's invitation email. `null` if the envelope title is used.
          </ResponseField>

          <ResponseField name="message_override" type="string | null">
            The custom message body used for this recipient's invitation email. `null` if the envelope message is used.
          </ResponseField>
        </Expandable>

        <Expandable title="Email Code Authentication">
          <div class="mt-4">
            With **email code authentication**, the recipient receives an email from SignatureAPI containing a 9-digit code. The recipient must enter this code to authenticate and access the ceremony.
          </div>

          <ResponseField name="type" type="enum">
            The type of authentication. Available values: `email_link`, `email_code`, and `custom`.

            For email code authentication, this value is `email_code`.
          </ResponseField>
        </Expandable>

        <Expandable title="Custom Authentication">
          <div class="mt-4">
            With **custom authentication**, your application authenticates the recipient. SignatureAPI provides a ceremony URL that you share or embed in your application to give the recipient access.
          </div>

          <ResponseField name="type" type="enum">
            The type of authentication. Available values: `email_link`, `email_code`, and `custom`.

            For custom authentication, this value is `custom`.
          </ResponseField>

          <ResponseField name="provider" type="string">
            The name of your company or application that authenticated the recipient. This value appears in the envelope audit log as the authentication provider.
          </ResponseField>

          <ResponseField name="data" type="object">
            Key-value pairs with metadata about the authentication event, such as timestamps, session IDs, and user identifiers. These values appear in the envelope audit log.

            <Warning>
              The values in `data` must be sufficient to verify how the recipient was authenticated. You must retain all records needed to prove the recipient's authentication, such as session information. In cases such as legal proceedings, you may need to provide these records to confirm identity.

              Review our [Terms & Conditions](https://signatureapi.com/terms) for details.
            </Warning>
          </ResponseField>
        </Expandable>
      </ResponseField>

      <ResponseField name="redirect_url" type="string | null">
        An HTTPS URL to redirect the recipient to after the ceremony finishes.

        Learn more in [Redirect URL](/docs/api/resources/ceremonies/redirect-url).
      </ResponseField>

      <ResponseField name="redirect_delay" type="integer | null">
        The delay in seconds before the ceremony redirects to `redirect_url` (standalone ceremonies) or emits completion events (embedded ceremonies).

        Defaults to `3`. Allowed range: `0` to `20`.

        Learn more in [Redirect URL](/docs/api/resources/ceremonies/redirect-url).
      </ResponseField>

      <ResponseField name="url_variant" type="enum">
        The format of the ceremony URL.

        Available options:

        * `standard` (default): Full-length URL. Works for most use cases.
        * `short`: Shortened URL. Use this when sharing through space-constrained channels such as SMS or push notifications.
      </ResponseField>

      <ResponseField name="embeddable_in" type="array of strings">
        Origins allowed to embed this ceremony in an iframe.

        These values set the `frame-ancestors` directive in the ceremony's Content Security Policy (CSP) header. Sources typically take the form of a scheme and host (for example, `https://app.example.com`). Wildcards are supported (for example, `https://*.example.com`). For all available options, see the [frame-ancestors documentation](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/frame-ancestors#sources).

        Defaults to an empty list (`[]`), which means embedding is not allowed. To allow embedding from all origins (not recommended for production), use `["*"]`.

        <Note>Only the origin (scheme and host) is used. Paths are ignored.</Note>
      </ResponseField>

      <ResponseField name="url" type="string | null">
        The URL where the recipient can access the ceremony. You can share this link with the recipient directly or embed it in your application.

        This property is `null` when:

        * The ceremony uses `email_link` authentication. SignatureAPI delivers the URL by email in that case.
        * The ceremony is not active (for example, it is completed, revoked, or declined).

        The URL expires 30 days after creation, or when a new ceremony is created for the same recipient.
      </ResponseField>
    </Expandable>
  </ResponseField>

  <ResponseField name="delivery_type" type="enum">
    Controls whether the completed deliverable is automatically emailed to this recipient.

    | Value   | Description                                                                                                 |
    | ------- | ----------------------------------------------------------------------------------------------------------- |
    | `email` | The completed deliverable is delivered to this recipient by email. This is the default for signers.         |
    | `none`  | The completed deliverable is not emailed. Your application is responsible for distributing the deliverable. |
  </ResponseField>

  <ResponseField name="signature_options" type="array of enum">
    The signature methods available to the signer. The first item in the array is shown as the default.

    | Option  | Description                                                                         |
    | ------- | ----------------------------------------------------------------------------------- |
    | `typed` | The signer types their name. It is pre-filled from the recipient's `name` property. |
    | `drawn` | The signer draws their signature using a mouse, stylus, or touchscreen.             |

    If not specified, both `typed` and `drawn` are available, with `typed` shown first.
  </ResponseField>

  <ResponseField name="completed_at" type="timestamp">
    The time at which the recipient completed their required actions on the envelope (for example, signed or approved), in <Tooltip tip="For example: 2025-12-31T23:59:59.999Z">ISO 8601</Tooltip> format. Returns `null` if the recipient has not yet completed.
  </ResponseField>

  <ResponseField name="status_updated_at" type="timestamp">
    The time at which the recipient's status last changed, in <Tooltip tip="For example: 2025-12-31T23:59:59.999Z">ISO 8601</Tooltip> format. Updates whenever the recipient transitions to a new status.
  </ResponseField>

  <div class="mb-4">
    <Expandable title="Deprecated Fields">
      <ResponseField name="ceremony_creation" type="enum" deprecated={true}>
        How the ceremony is created for the recipient.

        Available options are `automatic` and `manual`. The default is `automatic`.

        <Note>
          This property is deprecated. Use the `ceremony` object on the recipient when creating an envelope to control ceremony creation. This property will continue to be supported for backwards compatibility.
        </Note>
      </ResponseField>
    </Expandable>
  </div>
</Expandable>

<Expandable title="Preparer">
  <ResponseField name="id" type="string">
    The unique identifier of the recipient. Recipient IDs use the `re_` prefix.
  </ResponseField>

  <ResponseField name="envelope_id" type="string">
    The unique identifier of the envelope, in UUID format.
  </ResponseField>

  <ResponseField name="type" type="enum">
    The type of the recipient. Determines what actions the recipient can perform during the ceremony.

    | Type       | Description                                                    |
    | ---------- | -------------------------------------------------------------- |
    | `signer`   | Signs documents. Every envelope must have at least one signer. |
    | `approver` | Reviews and approves documents without signing.                |
    | `preparer` | Fills in document fields on behalf of another party.           |

    For preparers, the type is `preparer`.
  </ResponseField>

  <ResponseField name="key" type="string">
    A unique identifier you assign to each recipient in the envelope.

    Use it to match recipients with the places they should interact with (such as signature fields) and to identify them in events and webhook notifications.

    The key must start with a lowercase letter. It can contain lowercase letters, numbers, and underscores. Maximum 32 characters. It must be unique within the envelope.
  </ResponseField>

  <ResponseField name="name" type="string">
    The full name of the recipient. Appears in invitation emails and is pre-filled for typed signatures.
  </ResponseField>

  <ResponseField name="email" type="string">
    The email address of the recipient. Used to send invitation emails when `delivery_type` is `email`.
  </ResponseField>

  <ResponseField name="status" type="enum">
    The current status of the recipient in the signing workflow.

    | Status         | Description                                                                                                                               |
    | -------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
    | `pending`      | The envelope has not been sent to the recipient yet. This is the initial status.                                                          |
    | `awaiting`     | The recipient is waiting for earlier recipients in the routing order to complete.                                                         |
    | `sent`         | The invitation has been sent to the recipient.                                                                                            |
    | `completed`    | The recipient has completed their required actions (for example, signed or approved).                                                     |
    | `rejected`     | The recipient declined to complete the envelope.                                                                                          |
    | `soft_bounced` | The invitation email was temporarily undeliverable (for example, a full mailbox). You can resend the request.                             |
    | `hard_bounced` | The invitation email was permanently undeliverable (for example, an invalid address). Use the Replace endpoint to assign a new recipient. |
    | `failed`       | An error occurred and the invitation could not be sent.                                                                                   |
    | `replaced`     | This recipient was replaced with a new one via the Replace endpoint.                                                                      |
  </ResponseField>

  <ResponseField name="ceremony" type="object">
    The current [ceremony](/docs/api/resources/ceremonies/object) for the recipient.

    <Expandable title="Ceremony">
      <ResponseField name="authentication" type="array of authentication object">
        <Expandable title="Email Link Authentication">
          <div class="mt-4">
            With **email link authentication**, the recipient receives an email with a direct link to the ceremony. Clicking the link authenticates the recipient and opens the signing session.
          </div>

          <ResponseField name="type" type="enum">
            The type of authentication. Available values: `email_link`, `email_code`, and `custom`.

            For email link authentication, this value is `email_link`.
          </ResponseField>

          <ResponseField name="subject_override" type="string | null">
            The custom subject line used for this recipient's invitation email. `null` if the envelope title is used.
          </ResponseField>

          <ResponseField name="message_override" type="string | null">
            The custom message body used for this recipient's invitation email. `null` if the envelope message is used.
          </ResponseField>
        </Expandable>

        <Expandable title="Email Code Authentication">
          <div class="mt-4">
            With **email code authentication**, the recipient receives an email from SignatureAPI containing a 9-digit code. The recipient must enter this code to authenticate and access the ceremony.
          </div>

          <ResponseField name="type" type="enum">
            The type of authentication. Available values: `email_link`, `email_code`, and `custom`.

            For email code authentication, this value is `email_code`.
          </ResponseField>
        </Expandable>

        <Expandable title="Custom Authentication">
          <div class="mt-4">
            With **custom authentication**, your application authenticates the recipient. SignatureAPI provides a ceremony URL that you share or embed in your application to give the recipient access.
          </div>

          <ResponseField name="type" type="enum">
            The type of authentication. Available values: `email_link`, `email_code`, and `custom`.

            For custom authentication, this value is `custom`.
          </ResponseField>

          <ResponseField name="provider" type="string">
            The name of your company or application that authenticated the recipient. This value appears in the envelope audit log as the authentication provider.
          </ResponseField>

          <ResponseField name="data" type="object">
            Key-value pairs with metadata about the authentication event, such as timestamps, session IDs, and user identifiers. These values appear in the envelope audit log.

            <Warning>
              The values in `data` must be sufficient to verify how the recipient was authenticated. You must retain all records needed to prove the recipient's authentication, such as session information. In cases such as legal proceedings, you may need to provide these records to confirm identity.

              Review our [Terms & Conditions](https://signatureapi.com/terms) for details.
            </Warning>
          </ResponseField>
        </Expandable>
      </ResponseField>

      <ResponseField name="redirect_url" type="string | null">
        An HTTPS URL to redirect the recipient to after the ceremony finishes.

        Learn more in [Redirect URL](/docs/api/resources/ceremonies/redirect-url).
      </ResponseField>

      <ResponseField name="redirect_delay" type="integer | null">
        The delay in seconds before the ceremony redirects to `redirect_url` (standalone ceremonies) or emits completion events (embedded ceremonies).

        Defaults to `3`. Allowed range: `0` to `20`.

        Learn more in [Redirect URL](/docs/api/resources/ceremonies/redirect-url).
      </ResponseField>

      <ResponseField name="url_variant" type="enum">
        The format of the ceremony URL.

        Available options:

        * `standard` (default): Full-length URL. Works for most use cases.
        * `short`: Shortened URL. Use this when sharing through space-constrained channels such as SMS or push notifications.
      </ResponseField>

      <ResponseField name="embeddable_in" type="array of strings">
        Origins allowed to embed this ceremony in an iframe.

        These values set the `frame-ancestors` directive in the ceremony's Content Security Policy (CSP) header. Sources typically take the form of a scheme and host (for example, `https://app.example.com`). Wildcards are supported (for example, `https://*.example.com`). For all available options, see the [frame-ancestors documentation](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/frame-ancestors#sources).

        Defaults to an empty list (`[]`), which means embedding is not allowed. To allow embedding from all origins (not recommended for production), use `["*"]`.

        <Note>Only the origin (scheme and host) is used. Paths are ignored.</Note>
      </ResponseField>

      <ResponseField name="url" type="string | null">
        The URL where the recipient can access the ceremony. You can share this link with the recipient directly or embed it in your application.

        This property is `null` when:

        * The ceremony uses `email_link` authentication. SignatureAPI delivers the URL by email in that case.
        * The ceremony is not active (for example, it is completed, revoked, or declined).

        The URL expires 30 days after creation, or when a new ceremony is created for the same recipient.
      </ResponseField>
    </Expandable>
  </ResponseField>

  <ResponseField name="delivery_type" type="enum">
    Controls how the recipient receives the invitation to access the envelope. Also determines whether the completed deliverable is emailed to this recipient.

    | Value   | Description                                                                                                                                                           |
    | ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
    | `email` | SignatureAPI sends an invitation email with the ceremony link. The completed deliverable is also delivered by email.                                                  |
    | `none`  | No emails are sent. Your application is responsible for distributing the ceremony URL and the completed deliverable. This is the default for approvers and preparers. |
  </ResponseField>

  <ResponseField name="completed_at" type="timestamp">
    The time at which the recipient completed their required actions on the envelope (for example, signed or approved), in <Tooltip tip="For example: 2025-12-31T23:59:59.999Z">ISO 8601</Tooltip> format. Returns `null` if the recipient has not yet completed.
  </ResponseField>

  <ResponseField name="status_updated_at" type="timestamp">
    The time at which the recipient's status last changed, in <Tooltip tip="For example: 2025-12-31T23:59:59.999Z">ISO 8601</Tooltip> format. Updates whenever the recipient transitions to a new status.
  </ResponseField>

  <div class="mb-4">
    <Expandable title="Deprecated Fields">
      <ResponseField name="ceremony_creation" type="enum" deprecated={true}>
        How the ceremony is created for the recipient.

        Available options are `automatic` and `manual`. The default is `automatic`.

        <Note>
          This property is deprecated. Use the `ceremony` object on the recipient when creating an envelope to control ceremony creation. This property will continue to be supported for backwards compatibility.
        </Note>
      </ResponseField>
    </Expandable>
  </div>
</Expandable>

<Expandable title="Approver">
  <ResponseField name="id" type="string">
    The unique identifier of the recipient. Recipient IDs use the `re_` prefix.
  </ResponseField>

  <ResponseField name="envelope_id" type="string">
    The unique identifier of the envelope, in UUID format.
  </ResponseField>

  <ResponseField name="type" type="enum">
    The type of the recipient. Determines what actions the recipient can perform during the ceremony.

    | Type       | Description                                                    |
    | ---------- | -------------------------------------------------------------- |
    | `signer`   | Signs documents. Every envelope must have at least one signer. |
    | `approver` | Reviews and approves documents without signing.                |
    | `preparer` | Fills in document fields on behalf of another party.           |

    For approvers, the type is `approver`.
  </ResponseField>

  <ResponseField name="key" type="string">
    A unique identifier you assign to each recipient in the envelope.

    Use it to match recipients with the places they should interact with (such as signature fields) and to identify them in events and webhook notifications.

    The key must start with a lowercase letter. It can contain lowercase letters, numbers, and underscores. Maximum 32 characters. It must be unique within the envelope.
  </ResponseField>

  <ResponseField name="name" type="string">
    The full name of the recipient. Appears in invitation emails and is pre-filled for typed signatures.
  </ResponseField>

  <ResponseField name="email" type="string">
    The email address of the recipient. Used to send invitation emails when `delivery_type` is `email`.
  </ResponseField>

  <ResponseField name="status" type="enum">
    The current status of the recipient in the signing workflow.

    | Status         | Description                                                                                                                               |
    | -------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
    | `pending`      | The envelope has not been sent to the recipient yet. This is the initial status.                                                          |
    | `awaiting`     | The recipient is waiting for earlier recipients in the routing order to complete.                                                         |
    | `sent`         | The invitation has been sent to the recipient.                                                                                            |
    | `completed`    | The recipient has completed their required actions (for example, signed or approved).                                                     |
    | `rejected`     | The recipient declined to complete the envelope.                                                                                          |
    | `soft_bounced` | The invitation email was temporarily undeliverable (for example, a full mailbox). You can resend the request.                             |
    | `hard_bounced` | The invitation email was permanently undeliverable (for example, an invalid address). Use the Replace endpoint to assign a new recipient. |
    | `failed`       | An error occurred and the invitation could not be sent.                                                                                   |
    | `replaced`     | This recipient was replaced with a new one via the Replace endpoint.                                                                      |
  </ResponseField>

  <ResponseField name="ceremony" type="object">
    The current [ceremony](/docs/api/resources/ceremonies/object) for the recipient.

    <Expandable title="Ceremony">
      <ResponseField name="authentication" type="array of authentication object">
        <Expandable title="Email Link Authentication">
          <div class="mt-4">
            With **email link authentication**, the recipient receives an email with a direct link to the ceremony. Clicking the link authenticates the recipient and opens the signing session.
          </div>

          <ResponseField name="type" type="enum">
            The type of authentication. Available values: `email_link`, `email_code`, and `custom`.

            For email link authentication, this value is `email_link`.
          </ResponseField>

          <ResponseField name="subject_override" type="string | null">
            The custom subject line used for this recipient's invitation email. `null` if the envelope title is used.
          </ResponseField>

          <ResponseField name="message_override" type="string | null">
            The custom message body used for this recipient's invitation email. `null` if the envelope message is used.
          </ResponseField>
        </Expandable>

        <Expandable title="Email Code Authentication">
          <div class="mt-4">
            With **email code authentication**, the recipient receives an email from SignatureAPI containing a 9-digit code. The recipient must enter this code to authenticate and access the ceremony.
          </div>

          <ResponseField name="type" type="enum">
            The type of authentication. Available values: `email_link`, `email_code`, and `custom`.

            For email code authentication, this value is `email_code`.
          </ResponseField>
        </Expandable>

        <Expandable title="Custom Authentication">
          <div class="mt-4">
            With **custom authentication**, your application authenticates the recipient. SignatureAPI provides a ceremony URL that you share or embed in your application to give the recipient access.
          </div>

          <ResponseField name="type" type="enum">
            The type of authentication. Available values: `email_link`, `email_code`, and `custom`.

            For custom authentication, this value is `custom`.
          </ResponseField>

          <ResponseField name="provider" type="string">
            The name of your company or application that authenticated the recipient. This value appears in the envelope audit log as the authentication provider.
          </ResponseField>

          <ResponseField name="data" type="object">
            Key-value pairs with metadata about the authentication event, such as timestamps, session IDs, and user identifiers. These values appear in the envelope audit log.

            <Warning>
              The values in `data` must be sufficient to verify how the recipient was authenticated. You must retain all records needed to prove the recipient's authentication, such as session information. In cases such as legal proceedings, you may need to provide these records to confirm identity.

              Review our [Terms & Conditions](https://signatureapi.com/terms) for details.
            </Warning>
          </ResponseField>
        </Expandable>
      </ResponseField>

      <ResponseField name="redirect_url" type="string | null">
        An HTTPS URL to redirect the recipient to after the ceremony finishes.

        Learn more in [Redirect URL](/docs/api/resources/ceremonies/redirect-url).
      </ResponseField>

      <ResponseField name="redirect_delay" type="integer | null">
        The delay in seconds before the ceremony redirects to `redirect_url` (standalone ceremonies) or emits completion events (embedded ceremonies).

        Defaults to `3`. Allowed range: `0` to `20`.

        Learn more in [Redirect URL](/docs/api/resources/ceremonies/redirect-url).
      </ResponseField>

      <ResponseField name="url_variant" type="enum">
        The format of the ceremony URL.

        Available options:

        * `standard` (default): Full-length URL. Works for most use cases.
        * `short`: Shortened URL. Use this when sharing through space-constrained channels such as SMS or push notifications.
      </ResponseField>

      <ResponseField name="embeddable_in" type="array of strings">
        Origins allowed to embed this ceremony in an iframe.

        These values set the `frame-ancestors` directive in the ceremony's Content Security Policy (CSP) header. Sources typically take the form of a scheme and host (for example, `https://app.example.com`). Wildcards are supported (for example, `https://*.example.com`). For all available options, see the [frame-ancestors documentation](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/frame-ancestors#sources).

        Defaults to an empty list (`[]`), which means embedding is not allowed. To allow embedding from all origins (not recommended for production), use `["*"]`.

        <Note>Only the origin (scheme and host) is used. Paths are ignored.</Note>
      </ResponseField>

      <ResponseField name="url" type="string | null">
        The URL where the recipient can access the ceremony. You can share this link with the recipient directly or embed it in your application.

        This property is `null` when:

        * The ceremony uses `email_link` authentication. SignatureAPI delivers the URL by email in that case.
        * The ceremony is not active (for example, it is completed, revoked, or declined).

        The URL expires 30 days after creation, or when a new ceremony is created for the same recipient.
      </ResponseField>
    </Expandable>
  </ResponseField>

  <ResponseField name="delivery_type" type="enum">
    Controls how the recipient receives the invitation to access the envelope. Also determines whether the completed deliverable is emailed to this recipient.

    | Value   | Description                                                                                                                                                           |
    | ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
    | `email` | SignatureAPI sends an invitation email with the ceremony link. The completed deliverable is also delivered by email.                                                  |
    | `none`  | No emails are sent. Your application is responsible for distributing the ceremony URL and the completed deliverable. This is the default for approvers and preparers. |
  </ResponseField>

  <ResponseField name="completed_at" type="timestamp">
    The time at which the recipient completed their required actions on the envelope (for example, signed or approved), in <Tooltip tip="For example: 2025-12-31T23:59:59.999Z">ISO 8601</Tooltip> format. Returns `null` if the recipient has not yet completed.
  </ResponseField>

  <ResponseField name="status_updated_at" type="timestamp">
    The time at which the recipient's status last changed, in <Tooltip tip="For example: 2025-12-31T23:59:59.999Z">ISO 8601</Tooltip> format. Updates whenever the recipient transitions to a new status.
  </ResponseField>

  <div class="mb-4">
    <Expandable title="Deprecated Fields">
      <ResponseField name="ceremony_creation" type="enum" deprecated={true}>
        How the ceremony is created for the recipient.

        Available options are `automatic` and `manual`. The default is `automatic`.

        <Note>
          This property is deprecated. Use the `ceremony` object on the recipient when creating an envelope to control ceremony creation. This property will continue to be supported for backwards compatibility.
        </Note>
      </ResponseField>
    </Expandable>
  </div>
</Expandable>

<ResponseExample>
  ```json Signer theme={null}
  // HTTP Status 200

  {
    "id": "re_26w2VVV5JVm4j459TY5BNM",
    "envelope_id": "52872f0e-b919-4d69-89cd-e7e56af00548",
    "type": "signer",
    "key": "client",
    "name": "Emily Johnson",
    "email": "emily@example.com",
    "status": "completed",
    "status_updated_at": "2025-12-31T15:00:00.000Z",
    "completed_at": "2025-12-31T15:00:00.000Z",
    "delivery_type": "email",
    "signature_options": ["typed", "drawn"],
    "ceremony": {
      "authentication": [
        {
          "type": "email_link",
          "subject_override": null,
          "message_override": null
        }
      ],
      "redirect_url": null,
      "redirect_delay": 3,
      "embeddable_in": [],
      "url_variant": "standard",
      "url": null
    },
    "ceremony_creation": "automatic"
  }
  ```

  ```json Approver theme={null}
  // HTTP Status 200

  {
    "id": "re_7KpQVVV5JVm4j459TY5ABC",
    "envelope_id": "52872f0e-b919-4d69-89cd-e7e56af00548",
    "type": "approver",
    "key": "manager",
    "name": "Sarah Chen",
    "email": "sarah@example.com",
    "status": "completed",
    "status_updated_at": "2025-12-31T14:30:00.000Z",
    "completed_at": "2025-12-31T14:30:00.000Z",
    "delivery_type": "none",
    "ceremony": {
      "authentication": [
        {
          "type": "email_link",
          "subject_override": null,
          "message_override": null
        }
      ],
      "redirect_url": null,
      "redirect_delay": 3,
      "embeddable_in": [],
      "url_variant": "standard",
      "url": null
    },
    "ceremony_creation": "automatic"
  }
  ```

  ```json Preparer theme={null}
  // HTTP Status 200

  {
    "id": "re_9XtRVVV5JVm4j459TY5DEF",
    "envelope_id": "52872f0e-b919-4d69-89cd-e7e56af00548",
    "type": "preparer",
    "key": "sales_rep",
    "name": "Alex Smith",
    "email": "alex@example.com",
    "status": "completed",
    "status_updated_at": "2025-12-31T14:00:00.000Z",
    "completed_at": "2025-12-31T14:00:00.000Z",
    "delivery_type": "none",
    "ceremony": {
      "authentication": [
        {
          "type": "email_link",
          "subject_override": null,
          "message_override": null
        }
      ],
      "redirect_url": null,
      "redirect_delay": 3,
      "embeddable_in": [],
      "url_variant": "standard",
      "url": null
    },
    "ceremony_creation": "automatic"
  }
  ```
</ResponseExample>