# Resend webhooks

You can resend past webhook events to re-initiate associated workflow actions using the Dashboard and the API. This enables you to test workflows that have failed.

> **Information**
>
> You can only resend webhooks for events that occurred within the last 90 days.

Using the [Workflows API](https://www.checkout.com/docs/developer-resources/event-notifications/receive-webhooks/manage-webhooks-using-the-api.md), you can do the following:

- Resend workflows associated with multiple events or multiple subjects (for example, payment IDs or dispute IDs).
- Resend a specific event and re-initiate the actions of any associated workflows.
- Resend a specific workflow and event combination.
- Resend a specific subject and re-initiate the actions of any associated workflows.
- Resend a specific workflow and subject combination.

---

## Resend webhooks in the Dashboard

If a webhook fails, you can check why it failed, and manually resend it in the Dashboard.

You must have one of the following [user roles](https://www.checkout.com/docs/business-operations/use-the-dashboard/manage-users/user-permissions.md):

- Admin
- Compliance operator
- Developer
- A custom role with the following permissions:
   - `Create, edit and delete workflow notifications`
   - `View secret keys`
   - `View the list of workflow notifications`

> **Note**
>
> Resending a webhook manually may cause duplicates if any [automatic retries](https://www.checkout.com/docs/developer-resources/event-notifications/receive-webhooks.md#Automatic_retries) are scheduled.

To resend failed webhooks:

**Resend single webhook**

1. Sign in to the [Dashboard](https://dashboard.checkout.com).
2. Select _Developers_ in the left navigation bar and open the _Webhooks_ tab.<br>
   The _Webhook configurations_ list displays all webhook configurations for your entity.<br>
   Configurations with failed webhooks display _Failures_ in the _Config status_ column.
3. Select the configuration with failures to open its details page.<br>
   By default, the _Webhooks_ tab displays a list of all webhooks we sent in the previous two weeks, from oldest to newest. You can use the date picker tool to edit the date range, and the filter to find webhooks with a specific status.<br>
   Webhooks with failed attempts display _Failed_ in the _Status_ column.
4. Select the failed webhook to open its details page.<br>
   The _Attempt details_ page displays all attempts for the webhook, from oldest to newest. You can view the following details for each attempt:

   - The date and time of the attempt
   - The response code returned
   - The custom response message you configured
   - The status

   Failed attempts display _Failed_ in the _Status_ column.
5. Select _Retry now_ to initiate a new attempt.

**Resend multiple webhooks**

1. Sign in to the [Dashboard](https://dashboard.checkout.com).
2. Select _Developers_ in the left navigation bar and open the _Webhooks_ tab.<br>
   The _Webhook configurations_ list displays all webhook configurations for your entity.<br>
   Configurations with failed webhooks display _Failures_ in the _Config status_ column.
3. Select the configuration with failures to open its details page.<br>
   By default, the _Webhooks_ tab displays a list of all webhooks we sent in the previous two weeks, from oldest to newest. You can use the date picker tool to edit the date range, and the filter to find webhooks with a specific status.<br>
   Webhooks with failed attempts display _Failed_ in the _Status_ column.
4. Select the checkbox for each failed webhook you want to resend.
5. Select _Retry selected_.

**Resend all webhooks**

1. Sign in to the [Dashboard](https://dashboard.checkout.com).
2. Select _Developers_ in the left navigation bar and open the _Webhooks_ tab.<br>
   The _Webhook configurations_ list displays all webhook configurations for your entity.<br>
   Configurations with failed webhooks display _Failures_ in the _Config status_ column.
3. Select the configuration with failures to open its details page.<br>
   By default, the _Webhooks_ tab displays a list of all webhooks we sent in the previous two weeks, from oldest to newest. You can use the date picker tool to edit the date range, and the filter to find webhooks with a specific status.<br>
   Webhooks with failed attempts display _Failed_ in the _Status_ column.
4. Select _Retry all_.

**Resend webhooks by date**

1. Sign in to the [Dashboard](https://dashboard.checkout.com).
2. Select _Developers_ in the left navigation bar and open the _Webhooks_ tab.<br>
   The _Webhook configurations_ list displays all webhook configurations for your entity.<br>
   Configurations with failed webhooks display _Failures_ in the _Config status_ column.
3. Select the configuration with failures to open its details page.<br>
   By default, the _Webhooks_ tab displays a list of all webhooks we sent in the previous two weeks, from oldest to newest. You can use the date picker tool to edit the date range, and the filter to find webhooks with a specific status.<br>
   Webhooks with failed attempts display _Failed_ in the _Status_ column.
4. Select _Retry by date_.
5. Select a date range.
6. Select _Retry_.

---

## Resend workflows by events or subjects

To resend workflows associated with multiple events or multiple subjects, call the [Reflow](https://api-reference.checkout.com/tag/Workflows/#operation/reflowEvents) endpoint.

In the request body, provide one of the following sets of fields:

**Workflows and events**

| Field name | Description |
| --- | --- |
| `events`<br><br>`required`<br><br>array | The list of IDs for the events you want to resend. |
| `workflows`<br><br>`optional`<br><br>array | The list of IDs for the workflows whose actions you want to re-initiate.<br><br>If you don't provide any workflow IDs, all matching workflows are re-initiated. |

**Workflows and subjects**

| Field name | Description |
| --- | --- |
| `events`<br><br>`required`<br><br>array | The list of IDs for the subjects you want to resend the associated events for. |
| `workflows`<br><br>`optional`<br><br>array | The list of IDs for the workflows whose actions you want to re-initiate.<br><br>If you don't provide any workflow IDs, all matching workflows are re-initiated. |

> **Information**
>
> Your base URL's `{prefix}` value is unique to your account and environment. To learn how to retrieve your base URLs for the sandbox and production environments, see [API endpoints](https://www.checkout.com/docs/developer-resources/api/api-endpoints.md).

**Production**

`POST` `https://{prefix}.api.checkout.com/workflows/events/reflow`

**Sandbox**

`POST` `https://{prefix}.api.sandbox.checkout.com/workflows/events/reflow`

### Request examples

**Workflows and events**

```json
{
  "events": ["evt_lzmo6p0i3612judj754w1ngtil", "evt_05z6xuagtti48ajyfbuekg6a0a"],
  "workflows": ["wf_sq8jnqi9i749hhb470bu308uk2", "wf_bz91q7i4ks4sr0kasmas2xhp56"]
}
```

**Workflows and subjects**

```json
{
  "subjects": ["pay_lzmo6p0i3612judj754w1ngtil", "pay_ol88zt9jviq4mkark1bo5b4i9sk"],
  "workflows": ["wf_sq8jnqi9i749hhb470bu308uk2", "wf_bz91q7i4ks4sr0kasmas2xhp56"]
}
```

If successful, you receive a `202` response.

---

## Resend by event

To resend a specific event and re-initiate the actions of any associated workflows, call the [Reflow by event](https://api-reference.checkout.com/tag/Workflows/#operation/reflowByEvent) endpoint, and provide the event ID as the `{eventId}` path parameter.

> **Information**
>
> Your base URL's `{prefix}` value is unique to your account and environment. To learn how to retrieve your base URLs for the sandbox and production environments, see [API endpoints](https://www.checkout.com/docs/developer-resources/api/api-endpoints.md).

**Production**

`POST` `https://{prefix}.api.checkout.com/workflows/events/{eventId}/reflow`

**Sandbox**

`POST` `https://{prefix}.api.sandbox.checkout.com/workflows/events/{eventId}/reflow`

If successful, you receive a `202` response.

---

## Resend by workflow and event

To re-initiate all actions associated with a specific event and workflow combination, call the [Reflow by event and workflow](https://api-reference.checkout.com/tag/Workflows/#operation/reflowByEventAndWorkflow) endpoint, and provide the following path parameters:

- `{eventId}`
- `{workflowId}`

> **Information**
>
> Your base URL's `{prefix}` value is unique to your account and environment. To learn how to retrieve your base URLs for the sandbox and production environments, see [API endpoints](https://www.checkout.com/docs/developer-resources/api/api-endpoints.md).

**Production**

`POST` `https://{prefix}.api.checkout.com/workflows/events/{eventId}/workflow/{workflowId}/reflow`

**Sandbox**

`POST` `https://{prefix}.api.sandbox.checkout.com/workflows/events/{eventId}/workflow/{workflowId}/reflow`

If successful, you receive a `202` response.

---

## Resend by subject

To resend all events for a specific subject and re-initiate the actions of any associated workflows, call the [Reflow by subject](https://api-reference.checkout.com/tag/Workflows/#operation/reflowBySubject) endpoint, and provide the subject ID as the `{subjectId}` path parameter.

> **Information**
>
> Your base URL's `{prefix}` value is unique to your account and environment. To learn how to retrieve your base URLs for the sandbox and production environments, see [API endpoints](https://www.checkout.com/docs/developer-resources/api/api-endpoints.md).

**Production**

`POST` `https://{prefix}.api.checkout.com/workflows/events/subject/{subjectId}/reflow`

**Sandbox**

`POST` `https://{prefix}.api.sandbox.checkout.com/workflows/events/subject/{subjectId}/reflow`

If successful, you receive a `202` response.

---

## Resend by workflow and subject

To re-initiate all actions associated with a specific subject and workflow combination, call the [Reflow by subject and workflow](https://api-reference.checkout.com/tag/Workflows/#operation/reflowBySubjectAndWorkflow) endpoint.
Provide the following path parameters:

- `{eventId}`
- `{workflowId}`

> **Information**
>
> Your base URL's `{prefix}` value is unique to your account and environment. To learn how to retrieve your base URLs for the sandbox and production environments, see [API endpoints](https://www.checkout.com/docs/developer-resources/api/api-endpoints.md).

**Production**

`POST` `https://{prefix}.api.checkout.com/workflows/events/subject/{subjectId}/workflow/{workflowId}/reflow`

**Sandbox**

`POST` `https://{prefix}.api.sandbox.checkout.com/workflows/events/subject/{subjectId}/workflow/{workflowId}/reflow`

If successful, you receive a `202` response.