# Recipients

> The recipient object, roles, authentication, and signing order.

A recipient represents a person involved in an envelope — someone who signs, approves, or just receives a copy. The [Integration Guide](/en/guides/integration-guide/#1-create-the-envelope-and-recipients) shows how to create recipients when creating the envelope; this resource goes deeper into the object and the operations on existing recipients.

## Roles

| Role | Behavior |
|---|---|
| `SIGNER` | Must sign. Their required fields must be completed. |
| `APPROVER` | Must approve before `SIGNER`s with a higher `signingOrder` can sign. |
| `VIEWER` | Can view the document, takes no action. |
| `CC` | Receives a copy of the completed document, doesn't participate in the process. |
| `ASSISTANT` | Can fill in fields on behalf of another recipient. |

## Create recipients

```http
POST /envelope/recipient/create-many
```

Each recipient accepts `email`, `name`, `role`, and optionally `signingOrder`, `accessAuth`, and `actionAuth`.

See the full spec in the [API Reference](/en/api/operations/envelope-recipient-createmany/).

### Signing order

With sequential signing, recipients with a lower `signingOrder` sign first; those sharing the same value can sign simultaneously. To enable sequential signing, set `signingOrder: "SEQUENTIAL"` in the envelope's `meta` — see [Create the envelope](/en/guides/integration-guide/#1-create-the-envelope-and-recipients).

### Recipient authentication

To reinforce security for a specific recipient, beyond the API's general authentication:

| `accessAuth` (to view the document) | Description |
|---|---|
| `ACCOUNT` | The recipient must be signed in. |
| `TWO_FACTOR_AUTH` | The recipient must verify with 2FA. |

| `actionAuth` (to sign) | Description |
|---|---|
| `ACCOUNT` | The recipient must be signed in. |
| `PASSKEY` | Requires passkey authentication. |
| `TWO_FACTOR_AUTH` | Requires a 2FA code. |
| `PASSWORD` | Requires password verification. |
| `EXPLICIT_NONE` | Explicitly disables action authentication. |
| `CLAVE_UNICA` | Requires verifying the recipient's identity with ClaveÚnica (Chile's government ID system). |
| `FAO_HASH` | Verification tied to Advanced Electronic Signature — see [Advanced Electronic Signature](/en/guides/fea-orquestacion/). |

<Aside type="note" title="RUT and Advanced Electronic Signature">
	For recipients in an envelope with FEA, a `rut` property is added (the identity to verify against the certification authority), and signing order becomes mandatorily sequential. See the [Advanced Electronic Signature](/en/guides/fea-orquestacion/#2-create-the-envelope-and-recipients) chapter.
</Aside>

## Update recipients

```http
POST /envelope/recipient/update-many
```

Only available while the envelope isn't `COMPLETED`. Accepts the same fields as creation, all optional except the `id` of the recipient to modify.

See the full spec in the [API Reference](/en/api/operations/envelope-recipient-updatemany/).

## Delete a recipient

```http
POST /envelope/recipient/delete
```

See the full spec in the [API Reference](/en/api/operations/envelope-recipient-delete/).

## Reject on a recipient's behalf

```http
POST /envelope/recipient/{recipientId}/reject
```

Marks a recipient as `REJECTED` without going through the normal signing flow — for example, if you're told about the rejection through a channel outside Legaldoc and need to reflect it on the envelope.

See the full spec in the [API Reference](/en/api/operations/envelope-recipient-rejectonbehalfof/).

## Get a recipient

```http
GET /envelope/recipient/{recipientId}
```

Returns the full object, including `signingStatus` (`NOT_SIGNED`, `SIGNED`, `REJECTED`), `readStatus` (`NOT_OPENED`, `OPENED`), and `sendStatus` (`NOT_SENT`, `SENT`).

See the full spec in the [API Reference](/en/api/operations/envelope-recipient-get/).

---

## See also

- [Fields](/en/resources/fields/) — assigning fields to each recipient
- [Integration Guide](/en/guides/integration-guide/) — the full creation and signing flow
- [Advanced Electronic Signature](/en/guides/fea-orquestacion/) — RUT, sequential order, and identity verification