# Resending

Resend an email when a recipient can't find it. Lettermint sends the stored content again as a new email with its own message ID. The new email counts towards your usage like any other send.

You can resend an email only while Lettermint still stores its content. See [data retention](/platform/emails/data-retention).

## Resend with the API

Send a `POST` request to `/v1/messages/{messageId}/resend` with a project token or a Team API token that has the `write:messages` scope.

```bash title="cURL"
curl -X POST https://api.lettermint.co/v1/messages/f47ac10b-58cc-4372-a567-0e02b2c3d479/resend \
  -H "x-lettermint-token: $LETTERMINT_PROJECT_TOKEN" \
  -H "Idempotency-Key: order-12345-confirmation-resend" \
  -H "Content-Type: application/json" \
  -d '{ "recipients": ["recipient@example.com"] }'
```

Leave out `recipients` to resend to every original recipient. Any address you list must have been a recipient of the original email.

- The To and Cc headers stay the same as in the original email. Lettermint delivers only to the recipients you chose.
- The project's current route settings and sending mode apply, such as tracking and Sandbox.
- The new email has `resent_from_message_id` set to the ID of the original email.
- Use an [idempotency key](/platform/emails/idempotency) if you might retry the request.

You can also resend an email from its page in the dashboard.

## When you can't resend

| Status | Code | Reason |
| --- | --- | --- |
| `409` | `MESSAGE_NOT_RESENDABLE` | The email is not sent yet, was canceled, was stopped by a sending policy, or was received through an inbound route. |
| `409` | `RECIPIENT_NOT_RESENDABLE` | A recipient unsubscribed, reported spam, hard bounced, or is still in delivery. `details.recipients` lists each one with its reason. Nothing was sent. |
| `410` | `MESSAGE_CONTENT_UNAVAILABLE` | Lettermint deleted the content under your data retention period. |
| `429` | `RESEND_LIMIT_REACHED` | You resent this email 5 times in the last 24 hours. |