---
title: "Recipient"
description: "The recipient object represents a person who participates in an envelope as a signer, approver, preparer, automatic signer, or qualified signer"
canonical: "https://signatureapi.com/docs/api/resources/recipients/object"
source: "https://signatureapi.com/docs/api/resources/recipients/object.md"
last_verified_api_version: "1.18.0"
last_modified: "2026-11-18T12:07:52Z"
---

# Recipient

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

_Last verified against API version 1.18.0._

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

Recipients have five types, each with a different role:

| Type                                                                                        | Description                                                                                                       |
| ------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| [Signer](https://signatureapi.com/docs/api/resources/recipients/signer)                     | Reviews documents and adds a signature or initials. Every envelope must have at least one signing recipient.      |
| [Approver](https://signatureapi.com/docs/api/resources/recipients/approver)                 | Reviews and approves documents without signing. Approver actions are not recorded in the audit log.               |
| [Preparer](https://signatureapi.com/docs/api/resources/recipients/preparer)                 | Fills in document fields before signers receive the envelope. Preparer actions are not recorded in the audit log. |
| [Automatic Signer](https://signatureapi.com/docs/api/resources/recipients/automatic-signer) | The signature is applied automatically by the system. No ceremony, no email.                                      |
| [Qualified Signer](https://signatureapi.com/docs/api/resources/recipients/qualified-signer) | Signs with a qualified electronic signature (QES) through your own trust service provider. In public beta.        |

To choose between them:

**Which recipient type do I need?**

| Recipient type | Use when | Key rule |
|---|---|---|
| [`signer`](https://signatureapi.com/docs/api/resources/recipients/signer) | The person adds a signature or initials in their own ceremony. A simple electronic signature covers most business documents. | Every envelope needs at least one signing recipient. Every step of the ceremony is recorded in the audit log. |
| [`qualified_signer`](https://signatureapi.com/docs/api/resources/recipients/qualified-signer) | The law, a regulator or the other party requires a qualified electronic signature (QES) under eIDAS. | In public beta: you bring your own QTSP. Sequential routing, and exactly one `signature` place. |
| [`automatic_signer`](https://signatureapi.com/docs/api/resources/recipients/automatic-signer) | You have recorded authority to sign on the person's behalf. | No email and no ceremony: the signature comes from the images you provide, with a `mandate`. Consult your legal counsel for high-risk documents. |
| [`approver`](https://signatureapi.com/docs/api/resources/recipients/approver) | The person reviews and authorizes the documents, and can fill in input places, without signing. | The last button is Approve. Approver actions are not recorded in the audit log. Use sequential routing so the approver acts before the signer. |
| [`preparer`](https://signatureapi.com/docs/api/resources/recipients/preparer) | The person fills in input places before the signers receive the envelope. | Can't add signatures or initials. The last button is Finish. 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. Automatic signers are the exception: they do not access a ceremony; their signature is applied automatically by the system. A recipient's `status` tracks their progress through the workflow. See the [recipient lifecycle](https://signatureapi.com/docs/api/resources/recipients/lifecycle) for details on each status and what triggers a transition.

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

## Attributes

**Signer**

#### `id` (string)

The unique identifier of the recipient. Recipient IDs use the `re_` prefix.

#### `envelope_id` (string)

The unique identifier of the envelope, in UUID format.

#### `type` (enum)

The type of the recipient. Determines what actions the recipient can perform during the ceremony.

TypeDescription

signerSigns documents. Every envelope must have at least one signing recipient. approverReviews and approves documents without signing. preparerFills in document fields on behalf of another party. automatic\_signerThe signature is applied automatically by the system. qualified\_signerSigns with a qualified electronic signature (QES) through your own trust service provider. In public beta. See [Qualified Signer](https://signatureapi.com/docs/api/resources/recipients/qualified-signer).

For signers, the type is `signer`.

#### `key` (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.

#### `name` (string)

The full name of the recipient. Appears in invitation emails and is pre-filled for typed signatures.

#### `email` (string)

The email address of the recipient. SignatureAPI emails the ceremony link to this address when the ceremony uses `email_link` authentication, and the completed deliverable when `delivery_type` is `email`.

#### `status` (enum)

The current status of the recipient in the signing workflow.

StatusDescription

pendingThe envelope has not been sent to the recipient yet. This is the initial status. awaitingThe recipient is waiting for earlier recipients in the routing order to complete. sentThe invitation has been sent to the recipient. completedThe recipient has completed their required actions (for example, signed or approved). rejectedThe recipient declined to complete the envelope. soft\_bouncedThe invitation email was temporarily undeliverable (for example, a full mailbox). You can resend the request. hard\_bouncedThe invitation email was permanently undeliverable (for example, an invalid address). Use the Replace endpoint to assign a new recipient. failedAn error occurred and the invitation could not be sent. replacedThis recipient was replaced with a new one via the Replace endpoint.

#### `ceremony` (object)

The current [ceremony](https://signatureapi.com/docs/api/resources/ceremonies/object) for the recipient.

**Ceremony**

#### `authentication` (array of authentication object)

**Email Link Authentication**

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.

#### `type` (enum)

The type of authentication. Available values: `email_link`, `email_code`, and `custom`.

For email link authentication, this value is `email_link`.

#### `subject_override` (string | null)

The custom subject line used for this recipient's invitation email. `null` if the envelope title is used.

#### `message_override` (string | null)

The custom message body used for this recipient's invitation email. `null` if the envelope message is used.

**Email Code Authentication**

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.

#### `type` (enum)

The type of authentication. Available values: `email_link`, `email_code`, and `custom`.

For email code authentication, this value is `email_code`.

**Custom Authentication**

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.

#### `type` (enum)

The type of authentication. Available values: `email_link`, `email_code`, and `custom`.

For custom authentication, this value is `custom`.

#### `provider` (string)

The name of your company or application that authenticated the recipient. This value appears in the envelope audit log as the authentication provider.

#### `data` (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/docs/legal/terms/terms) for details.

#### `redirect_url` (string | null)

An HTTPS URL to redirect the recipient to after the ceremony finishes.

Learn more in [Redirect URL](https://signatureapi.com/docs/api/resources/ceremonies/redirect-url).

#### `redirect_delay` (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](https://signatureapi.com/docs/api/resources/ceremonies/redirect-url).

#### `url_variant` (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.

#### `embeddable_in` (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.

#### `url` (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.

#### `delivery_type` (enum)

Controls whether the completed deliverable is automatically emailed to this recipient.

ValueDescription

emailThe completed deliverable is delivered to this recipient by email. This is the default for signers. noneThe completed deliverable is not emailed. Your application is responsible for distributing the deliverable.

#### `signature_options` (array of enum)

The signature methods available to the signer. The first item in the array is shown as the default.

OptionDescription

typedThe signer types their name. It is pre-filled from the recipient's name property. drawnThe signer draws their signature using a mouse, stylus, or touchscreen.

If not specified, both `typed` and `drawn` are available, with `typed` shown first.

#### `completed_at` (timestamp)

The time at which the recipient completed their required actions on the envelope (for example, signed or approved), in ISO 8601 format. Returns `null` if the recipient has not yet completed.

#### `status_updated_at` (timestamp)

The time at which the recipient's status last changed, in ISO 8601 format. Updates whenever the recipient transitions to a new status.

**Deprecated Fields**

#### `ceremony_creation` (enum, deprecated)

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.

**Preparer**

#### `id` (string)

The unique identifier of the recipient. Recipient IDs use the `re_` prefix.

#### `envelope_id` (string)

The unique identifier of the envelope, in UUID format.

#### `type` (enum)

The type of the recipient. Determines what actions the recipient can perform during the ceremony.

TypeDescription

signerSigns documents. Every envelope must have at least one signing recipient. approverReviews and approves documents without signing. preparerFills in document fields on behalf of another party. automatic\_signerThe signature is applied automatically by the system. qualified\_signerSigns with a qualified electronic signature (QES) through your own trust service provider. In public beta. See [Qualified Signer](https://signatureapi.com/docs/api/resources/recipients/qualified-signer).

For preparers, the type is `preparer`.

#### `key` (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.

#### `name` (string)

The full name of the recipient. Appears in invitation emails and is pre-filled for typed signatures.

#### `email` (string)

The email address of the recipient. SignatureAPI emails the ceremony link to this address when the ceremony uses `email_link` authentication, and the completed deliverable when `delivery_type` is `email`.

#### `status` (enum)

The current status of the recipient in the signing workflow.

StatusDescription

pendingThe envelope has not been sent to the recipient yet. This is the initial status. awaitingThe recipient is waiting for earlier recipients in the routing order to complete. sentThe invitation has been sent to the recipient. completedThe recipient has completed their required actions (for example, signed or approved). rejectedThe recipient declined to complete the envelope. soft\_bouncedThe invitation email was temporarily undeliverable (for example, a full mailbox). You can resend the request. hard\_bouncedThe invitation email was permanently undeliverable (for example, an invalid address). Use the Replace endpoint to assign a new recipient. failedAn error occurred and the invitation could not be sent. replacedThis recipient was replaced with a new one via the Replace endpoint.

#### `ceremony` (object)

The current [ceremony](https://signatureapi.com/docs/api/resources/ceremonies/object) for the recipient.

**Ceremony**

#### `authentication` (array of authentication object)

**Email Link Authentication**

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.

#### `type` (enum)

The type of authentication. Available values: `email_link`, `email_code`, and `custom`.

For email link authentication, this value is `email_link`.

#### `subject_override` (string | null)

The custom subject line used for this recipient's invitation email. `null` if the envelope title is used.

#### `message_override` (string | null)

The custom message body used for this recipient's invitation email. `null` if the envelope message is used.

**Email Code Authentication**

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.

#### `type` (enum)

The type of authentication. Available values: `email_link`, `email_code`, and `custom`.

For email code authentication, this value is `email_code`.

**Custom Authentication**

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.

#### `type` (enum)

The type of authentication. Available values: `email_link`, `email_code`, and `custom`.

For custom authentication, this value is `custom`.

#### `provider` (string)

The name of your company or application that authenticated the recipient. This value appears in the envelope audit log as the authentication provider.

#### `data` (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/docs/legal/terms/terms) for details.

#### `redirect_url` (string | null)

An HTTPS URL to redirect the recipient to after the ceremony finishes.

Learn more in [Redirect URL](https://signatureapi.com/docs/api/resources/ceremonies/redirect-url).

#### `redirect_delay` (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](https://signatureapi.com/docs/api/resources/ceremonies/redirect-url).

#### `url_variant` (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.

#### `embeddable_in` (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.

#### `url` (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.

#### `delivery_type` (enum)

Controls whether SignatureAPI emails the completed deliverable to the recipient once the envelope is finished.

ValueDescription

emailThe completed deliverable is delivered to this recipient by email. noneThe completed deliverable is not emailed. Your application is responsible for distributing the deliverable. This is the default for approvers and preparers.

#### `completed_at` (timestamp)

The time at which the recipient completed their required actions on the envelope (for example, signed or approved), in ISO 8601 format. Returns `null` if the recipient has not yet completed.

#### `status_updated_at` (timestamp)

The time at which the recipient's status last changed, in ISO 8601 format. Updates whenever the recipient transitions to a new status.

**Deprecated Fields**

#### `ceremony_creation` (enum, deprecated)

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.

**Approver**

#### `id` (string)

The unique identifier of the recipient. Recipient IDs use the `re_` prefix.

#### `envelope_id` (string)

The unique identifier of the envelope, in UUID format.

#### `type` (enum)

The type of the recipient. Determines what actions the recipient can perform during the ceremony.

TypeDescription

signerSigns documents. Every envelope must have at least one signing recipient. approverReviews and approves documents without signing. preparerFills in document fields on behalf of another party. automatic\_signerThe signature is applied automatically by the system. qualified\_signerSigns with a qualified electronic signature (QES) through your own trust service provider. In public beta. See [Qualified Signer](https://signatureapi.com/docs/api/resources/recipients/qualified-signer).

For approvers, the type is `approver`.

#### `key` (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.

#### `name` (string)

The full name of the recipient. Appears in invitation emails and is pre-filled for typed signatures.

#### `email` (string)

The email address of the recipient. SignatureAPI emails the ceremony link to this address when the ceremony uses `email_link` authentication, and the completed deliverable when `delivery_type` is `email`.

#### `status` (enum)

The current status of the recipient in the signing workflow.

StatusDescription

pendingThe envelope has not been sent to the recipient yet. This is the initial status. awaitingThe recipient is waiting for earlier recipients in the routing order to complete. sentThe invitation has been sent to the recipient. completedThe recipient has completed their required actions (for example, signed or approved). rejectedThe recipient declined to complete the envelope. soft\_bouncedThe invitation email was temporarily undeliverable (for example, a full mailbox). You can resend the request. hard\_bouncedThe invitation email was permanently undeliverable (for example, an invalid address). Use the Replace endpoint to assign a new recipient. failedAn error occurred and the invitation could not be sent. replacedThis recipient was replaced with a new one via the Replace endpoint.

#### `ceremony` (object)

The current [ceremony](https://signatureapi.com/docs/api/resources/ceremonies/object) for the recipient.

**Ceremony**

#### `authentication` (array of authentication object)

**Email Link Authentication**

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.

#### `type` (enum)

The type of authentication. Available values: `email_link`, `email_code`, and `custom`.

For email link authentication, this value is `email_link`.

#### `subject_override` (string | null)

The custom subject line used for this recipient's invitation email. `null` if the envelope title is used.

#### `message_override` (string | null)

The custom message body used for this recipient's invitation email. `null` if the envelope message is used.

**Email Code Authentication**

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.

#### `type` (enum)

The type of authentication. Available values: `email_link`, `email_code`, and `custom`.

For email code authentication, this value is `email_code`.

**Custom Authentication**

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.

#### `type` (enum)

The type of authentication. Available values: `email_link`, `email_code`, and `custom`.

For custom authentication, this value is `custom`.

#### `provider` (string)

The name of your company or application that authenticated the recipient. This value appears in the envelope audit log as the authentication provider.

#### `data` (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/docs/legal/terms/terms) for details.

#### `redirect_url` (string | null)

An HTTPS URL to redirect the recipient to after the ceremony finishes.

Learn more in [Redirect URL](https://signatureapi.com/docs/api/resources/ceremonies/redirect-url).

#### `redirect_delay` (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](https://signatureapi.com/docs/api/resources/ceremonies/redirect-url).

#### `url_variant` (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.

#### `embeddable_in` (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.

#### `url` (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.

#### `delivery_type` (enum)

Controls whether SignatureAPI emails the completed deliverable to the recipient once the envelope is finished.

ValueDescription

emailThe completed deliverable is delivered to this recipient by email. noneThe completed deliverable is not emailed. Your application is responsible for distributing the deliverable. This is the default for approvers and preparers.

#### `completed_at` (timestamp)

The time at which the recipient completed their required actions on the envelope (for example, signed or approved), in ISO 8601 format. Returns `null` if the recipient has not yet completed.

#### `status_updated_at` (timestamp)

The time at which the recipient's status last changed, in ISO 8601 format. Updates whenever the recipient transitions to a new status.

**Deprecated Fields**

#### `ceremony_creation` (enum, deprecated)

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.

**Automatic Signer**

#### `id` (string)

The unique identifier of the recipient. Recipient IDs use the `re_` prefix.

#### `envelope_id` (string)

The unique identifier of the envelope, in UUID format.

#### `type` (enum)

The type of the recipient. Determines what actions the recipient can perform during the ceremony.

TypeDescription

signerSigns documents. Every envelope must have at least one signing recipient. approverReviews and approves documents without signing. preparerFills in document fields on behalf of another party. automatic\_signerThe signature is applied automatically by the system. qualified\_signerSigns with a qualified electronic signature (QES) through your own trust service provider. In public beta. See [Qualified Signer](https://signatureapi.com/docs/api/resources/recipients/qualified-signer).

For automatic signers, the type is `automatic_signer`.

#### `key` (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.

#### `name` (string)

The full name of the signer. Appears in the audit log line that records the automatic signature.

#### `signature` (object | null)

The signature image applied to the document, as supplied at envelope creation. `null` if no preset signature was supplied.

**Preset symbol**

#### `type` (string)

The symbol type. Currently only `drawn` is supported.

#### `url` (string)

The URL of the PNG upload referenced when the automatic signer was created.

#### `initials` (object | null)

The initials image applied to the document, as supplied at envelope creation. `null` if no preset initials were supplied. Same shape as `signature`.

#### `mandate` (string)

A short statement explaining why the initiator was authorized to sign on behalf of this person. This string is shown as-is in the audit log. Maximum 500 characters.

#### `status` (enum)

The current status of the recipient. An automatic signer transitions from `pending` or `awaiting` directly to `completed` once the envelope is released and the signature is applied. See [recipient lifecycle](https://signatureapi.com/docs/api/resources/recipients/lifecycle).

#### `completed_at` (timestamp)

The time at which the recipient's signature was applied, in ISO 8601 format. Returns `null` if the recipient has not yet completed.

#### `status_updated_at` (timestamp)

The time at which the recipient's status last changed, in ISO 8601 format.

> **Note:** Automatic signers do not have `email`, `ceremony`, `delivery_type`, or `signature_options` properties. They do not receive invitations or access a ceremony.

### Example: Signer

Response 200 OK:

```json
{
  "id": "re_49r1R2jpPDz8hSpP75ZkPp",
  "envelope_id": "eb4cf433-a8af-4161-b37b-7ef57d423e56",
  "type": "signer",
  "key": "client",
  "name": "Jane Doe",
  "email": "jane.doe@example.com",
  "status": "completed",
  "ceremony": {
    "authentication": [
      {
        "type": "email_link",
        "subject_override": null,
        "message_override": null
      }
    ],
    "redirect_url": null,
    "redirect_delay": 3,
    "embeddable_in": [],
    "url_variant": "standard",
    "url": null
  },
  "delivery_type": "email",
  "ceremony_creation": "automatic",
  "signature_options": [
    "typed",
    "drawn"
  ],
  "completed_at": "2026-11-02T14:41:02.000Z",
  "status_updated_at": "2026-11-02T14:41:02.000Z"
}
```

### Example: Approver

Response 200 OK:

```json
{
  "id": "re_1mdt9PluVuu4QIhYYe8R1P",
  "envelope_id": "eb4cf433-a8af-4161-b37b-7ef57d423e56",
  "type": "approver",
  "key": "hiring_manager",
  "name": "Alex Chen",
  "email": "alex.chen@example.com",
  "status": "completed",
  "ceremony": {
    "authentication": [
      {
        "type": "email_link",
        "subject_override": null,
        "message_override": null
      }
    ],
    "redirect_url": null,
    "redirect_delay": 3,
    "embeddable_in": [],
    "url_variant": "standard",
    "url": null
  },
  "delivery_type": "none",
  "ceremony_creation": "automatic",
  "completed_at": "2026-11-02T14:30:00.000Z",
  "status_updated_at": "2026-11-02T14:30:00.000Z"
}
```

### Example: Preparer

Response 200 OK:

```json
{
  "id": "re_65ucNVJLuMTdsNsdZ96H3L",
  "envelope_id": "eb4cf433-a8af-4161-b37b-7ef57d423e56",
  "type": "preparer",
  "key": "preparer",
  "name": "Sam Patel",
  "email": "sam.patel@example.com",
  "status": "completed",
  "ceremony": {
    "authentication": [
      {
        "type": "email_link",
        "subject_override": null,
        "message_override": null
      }
    ],
    "redirect_url": null,
    "redirect_delay": 3,
    "embeddable_in": [],
    "url_variant": "standard",
    "url": null
  },
  "delivery_type": "none",
  "ceremony_creation": "automatic",
  "completed_at": "2026-11-02T14:10:00.000Z",
  "status_updated_at": "2026-11-02T14:10:00.000Z"
}
```

### Example: Automatic signer

Response 200 OK:

```json
{
  "id": "re_37Z4CKAhhVglhjQXeYclOa",
  "envelope_id": "eb4cf433-a8af-4161-b37b-7ef57d423e56",
  "type": "automatic_signer",
  "key": "company",
  "name": "Acme Corp",
  "signature": {
    "type": "drawn",
    "url": "https://api.signatureapi.com/v1/uploads/upl_3JJz6t1o8A5YjX5VpnX27Z"
  },
  "initials": {
    "type": "drawn",
    "url": "https://api.signatureapi.com/v1/uploads/upl_2tq9HtBuXZH2GSsrzJp9O7"
  },
  "mandate": "Authorized by Acme Corp Legal on November 2, 2026",
  "status": "completed",
  "status_updated_at": "2026-11-02T14:05:00.000Z",
  "completed_at": "2026-11-02T14:05:00.000Z"
}
```
