> For the complete documentation index, see [llms.txt](https://developers.bead.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.bead.xyz/onboarding/resend-application.md).

# Resend Application

Use `POST /merchant-onboarding/{applicationId}/resend-to-applicant` to email the applicant their invitation again. The applicant receives the same link they were first sent, and the link's expiry starts over.

Resend applies only after an application has been sent to the applicant. To send an application for the first time, see [Send to Applicant](https://developers.bead.xyz/onboarding/send-to-applicant.md).

{% hint style="info" %}
**Which endpoint do I call?** Send and resend are two steps of one flow. Each works for exactly one status, and the other returns `400`.

| Application status | Call                                                            | Result                                                                                  |
| ------------------ | --------------------------------------------------------------- | --------------------------------------------------------------------------------------- |
| `prepared`         | `POST /merchant-onboarding/{applicationId}/send-to-applicant`   | First send. The application moves to `signing`.                                         |
| `signing`          | `POST /merchant-onboarding/{applicationId}/resend-to-applicant` | The invitation is emailed again with the same link. The application stays in `signing`. |
| Any other status   | Neither                                                         | Both return `400` with the current status.                                              |
| {% endhint %}      |                                                                 |                                                                                         |

#### When to use Resend

Use resend when the application is in `signing` and the applicant needs the email again, for example:

* the applicant lost or deleted the original email
* the email went to spam or was never received
* the invitation is close to expiring and the applicant needs more time
* you corrected the business or owner details after the invitation went out and want the applicant to see them

Resend writes any business or owner detail that changed since the invitation was sent before it emails the applicant, so the applicant sees the corrected values.

#### When not to use Resend

Do not call resend when:

* the application is in `prepared`. Nothing has been sent yet, so use [Send to Applicant](https://developers.bead.xyz/onboarding/send-to-applicant.md).
* the application is in `draft`. Use `POST /merchant-onboarding/applications/{applicationId}/submit` first. See [Draft and Submit](https://developers.bead.xyz/onboarding/draft-and-submit.md).
* the applicant has already finished. The application is in `signed` or a later status.
* the invitation has expired and the application is in `expired`. Resend works only in `signing`. Contact your Bead team to reach the applicant again.
* the application is in `changesRequested`. Read the reason in the `applicationChangesRequested` webhook, correct what it names, and contact your Bead team to move it forward. See [Get Status](https://developers.bead.xyz/onboarding/get-status.md).
* you need to change the applicant. Resend always goes to the signer on the application.

#### Endpoint

```http
POST /merchant-onboarding/{applicationId}/resend-to-applicant
```

#### Path parameter

| Parameter       | Description                                                                      |
| --------------- | -------------------------------------------------------------------------------- |
| `applicationId` | The onboarding application identifier returned when the application was created. |

#### Authentication and headers

Onboarding requests use API key authentication. A partner user or API key with access to the application can call this endpoint. A caller without access to the application receives `403`.

```http
X-Api-Key: {apiKey}
Accept: application/json
```

#### Request

No request body is required.

```bash
curl --request POST \
  --url https://api.test.devs.beadpay.io/merchant-onboarding/app-123exampleid/resend-to-applicant \
  --header "X-Api-Key: {apiKey}" \
  --header "Accept: application/json"
```

#### Response

A successful resend returns `204 No Content` with no body. The application stays in `signing`. Continue tracking it with [Get Status](https://developers.bead.xyz/onboarding/get-status.md) or [webhooks](https://developers.bead.xyz/onboarding/partner-webhooks.md).

#### Typical resend pattern

1. Call `GET /merchant-onboarding/applications/{applicationId}` and confirm the status is `signing`.
2. If you corrected business or owner details, save them first.
3. Call `POST /merchant-onboarding/{applicationId}/resend-to-applicant`.
4. Tell the applicant to check their email, including spam.
5. Keep tracking the application until it reaches `signed`.

Resend does not create a second link. The original link keeps working and its expiry restarts, so you never leave more than one live link for an application.

#### Error handling

| Status | Meaning                                                                                                                            | What to do                                                                                                                   |
| ------ | ---------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| `204`  | The invitation was emailed again.                                                                                                  | Nothing more to do.                                                                                                          |
| `400`  | The application is not in `signing`, or has no invitation to resend. The message names the current status.                         | Check the status. If it is `prepared`, use [Send to Applicant](https://developers.bead.xyz/onboarding/send-to-applicant.md). |
| `401`  | The API key is missing or invalid.                                                                                                 | Check the `X-Api-Key` header.                                                                                                |
| `403`  | The caller does not have access to this application.                                                                               | Use a key or user with access to the application.                                                                            |
| `404`  | Unknown `applicationId`.                                                                                                           | Check the identifier.                                                                                                        |
| `409`  | Another resend of this application is already underway. Nothing was resent, so the applicant is not emailed twice.                 | Wait a moment and check status. Resend again only if needed.                                                                 |
| `422`  | The invitation or the updated details were refused. The response names each refused field with the reason, and nothing was resent. | Correct the named fields, then resend.                                                                                       |
| `503`  | A downstream provider failed. The response carries the `error_code` `WORTH_UNAVAILABLE`. Nothing was resent.                       | Retry after a short delay.                                                                                                   |

#### Best practices

* Check the status before every resend. Resend works only in `signing`.
* Treat `409` as a sign that a resend is already in progress. Do not retry in a loop.
* Show the applicant a clear message that the email was sent again, and mention checking spam.
* Do not call resend repeatedly. One email per request goes out, so repeated calls fill the applicant's inbox.
* Keep a record of your resend actions in your own system alongside the application history from `GET /merchant-onboarding/applications/{applicationId}/history`.

#### Related pages

* [Send to Applicant](https://developers.bead.xyz/onboarding/send-to-applicant.md)
* [Draft and Submit](https://developers.bead.xyz/onboarding/draft-and-submit.md)
* [Submit Application](https://developers.bead.xyz/onboarding/submit-application.md)
* [Application Attachments](https://developers.bead.xyz/onboarding/application-attachments.md)
* [Test the Full Onboarding Workflow in Sandbox](https://developers.bead.xyz/onboarding/test-the-full-onboarding-workflow-in-sandbox.md)
* [Get Status](https://developers.bead.xyz/onboarding/get-status.md)
* [Webhooks for Application Events](https://developers.bead.xyz/onboarding/partner-webhooks.md)
* [Sample Payload](https://developers.bead.xyz/onboarding/sample-payload.md)
* [Reference Guide](https://developers.bead.xyz/reference-guide)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developers.bead.xyz/onboarding/resend-application.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
