---
title: "Resend request"
description: "Resend the signing request email to a recipient who has not completed, as a reminder or after a soft bounce, within the documented wait periods."
canonical: "https://signatureapi.com/docs/api/resources/recipients/resend"
source: "https://signatureapi.com/docs/api/resources/recipients/resend.md"
last_verified_api_version: "1.18.0"
last_modified: "2026-11-18T12:07:52Z"
---

# Resend request

Resend the signing request email to a recipient who has not completed, as a reminder or after a soft bounce, within the documented wait periods.

_Last verified against API version 1.18.0._

Resends the signing request to a recipient who has not yet completed their ceremony.

Use this endpoint to:

- **Send reminders.** If a recipient has not signed, resend the invitation as a reminder.
- **Retry after a soft bounce.** If the invitation email was temporarily undeliverable, resend to try again.
- **Re-deliver a lost email.** If a recipient reports not receiving the invitation, resend it.

The resend is rate-limited to prevent email spam. The response includes `can_resend_at`, which tells you when the next resend can be initiated. The wait period after each email depends on how many have been sent so far, counting the first invitation:

| Emails sent | Wait before the next resend |
| ----------- | --------------------------- |
| 1-3         | 15 minutes                  |
| 4-6         | 1 hour                      |
| 7-9         | 24 hours                    |
| 10          | No more resends allowed     |

A request sent before `can_resend_at` fails with [`too-early-to-resend`](https://signatureapi.com/docs/v1/errors/too-early-to-resend), and a request after the tenth email fails with [`too-many-attempts`](https://signatureapi.com/docs/v1/errors/too-many-attempts). For reminders, space them at least 24 hours apart, and read `can_resend_at` from each response.

> **Note:** The request can only be resent if the recipient's ceremony uses `email_link` authentication, the recipient's status is `sent` or `soft_bounced`, and the envelope status is `in_progress`.

### Path Parameters

#### `recipient_id` (string, path, required)

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

### Returns

Returns a `200 OK` status code along with the following property:

#### `can_resend_at` (datetime)

Time after which the next resend can be initiated, in ISO 8601 format.

### Errors

| Status | Type                                                                                 | When                                                                                                                                 |
| ------ | ------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------ |
| `404`  | [`not-found`](https://signatureapi.com/docs/v1/errors/not-found)                     | No recipient with this ID exists in the account and mode of your API key.                                                            |
| `409`  | [`too-early-to-resend`](https://signatureapi.com/docs/v1/errors/too-early-to-resend) | The time in `can_resend_at` has not passed yet. The `detail` names the time.                                                         |
| `409`  | [`too-many-attempts`](https://signatureapi.com/docs/v1/errors/too-many-attempts)     | Ten emails have already been sent to this recipient.                                                                                 |
| `409`  | [`cannot-resend`](https://signatureapi.com/docs/v1/errors/cannot-resend)             | The recipient has no active `email_link` ceremony, its status is not `sent` or `soft_bounced`, or the envelope is not `in_progress`. |
| `422`  | [`validation-error`](https://signatureapi.com/docs/v1/errors/validation-error)       | The request body is invalid.                                                                                                         |

For errors every endpoint can return, such as authentication and rate limits, see [Errors](https://signatureapi.com/docs/api/errors).

### Example: Default

```http
POST /v1/recipients/re_2f0wBwlt2te0kjU5QeL3Nl/resend HTTP/1.1
Host: api.signatureapi.com
X-API-Key: YOUR_API_KEY
```

Response 200 OK:

```json
{
  "can_resend_at": "2026-11-02T17:42:12.000Z",
  "subject_override": null,
  "message_override": null
}
```

Response 404 Not Found:

```json
{
  "type": "https://signatureapi.com/docs/v1/errors/not-found",
  "title": "Not Found",
  "status": 404,
  "detail": "The recipient was not found."
}
```

Response 409 Conflict:

```json
{
  "type": "https://signatureapi.com/docs/v1/errors/too-early-to-resend",
  "title": "Too Early To Resend",
  "status": 409,
  "detail": "Please wait until after 2026-11-02T17:42:12.000Z to resend the request."
}
```

Response 422 Unprocessable Content:

```json
{
  "type": "https://signatureapi.com/docs/v1/errors/validation-error",
  "title": "Validation Error",
  "status": 422,
  "detail": "The request body contains validation errors.",
  "errors": [
    "subject_override must be shorter than or equal to 500 characters"
  ]
}
```

### Example: Custom message

```http
POST /v1/recipients/re_2f0wBwlt2te0kjU5QeL3Nl/resend HTTP/1.1
Host: api.signatureapi.com
X-API-Key: YOUR_API_KEY
Content-Type: application/json

{
  "subject_override": "Reminder: please sign your offer letter",
  "message_override": "Your offer letter is ready for your signature."
}
```

Response 200 OK:

```json
{
  "can_resend_at": "2026-11-02T17:42:12.000Z",
  "subject_override": "Reminder: please sign your offer letter",
  "message_override": "Your offer letter is ready for your signature."
}
```

Errors that any request can return (authentication, rate limits, server errors) are on the [Errors](https://signatureapi.com/docs/api/errors) and [Authentication](https://signatureapi.com/docs/api/authentication) pages.
