Resend webhooks
Last updated: November 12, 2025
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, 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.
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:
- Admin
- Compliance operator
- Developer
- A custom role with the following permissions:
Create, edit and delete workflow notificationsView secret keysView the list of workflow notifications
Note
Resending a webhook manually may cause duplicates if any automatic retries are scheduled.
To resend failed webhooks:
Sign in to the Dashboard.
Select the Developers icon in the top navigation bar and open the Webhooks tab.
The Webhook configurations list displays all webhook configurations for your entity.
Configurations with failed webhooks display Failures in the Config status column.Select the configuration with failures to open its details page.
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.
Webhooks with failed attempts display Failed in the Status column.Select the failed webhook to open its details page.
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.
Select Retry now to initiate a new attempt.
To resend workflows associated with multiple events or multiple subjects, call the Reflow endpoint.
In the request body, provide one of the following sets of fields:
| Field name | Description |
|---|---|
required array | The list of IDs for the events you want to resend. |
optional array | The list of IDs for the workflows whose actions you want to re-initiate. If you don't provide any workflow IDs, all matching workflows are re-initiated. |
post
https://api.checkout.com/workflows/events/reflow
If successful, you receive a 202 response.
To resend a specific event and re-initiate the actions of any associated workflows, call the Reflow by event endpoint, and provide the event ID as the {eventId} path parameter.
post
https://api.checkout.com/workflows/events/{eventId}/reflow
If successful, you receive a 202 response.
To re-initiate all actions associated with a specific event and workflow combination, call the Reflow by event and workflow endpoint, and provide the following path parameters:
{eventId}{workflowId}
post
https://api.checkout.com/workflows/events/{eventId}/workflow/{workflowId}/reflow
If successful, you receive a 202 response.
To resend all events for a specific subject and re-initiate the actions of any associated workflows, call the Reflow by subject endpoint, and provide the subject ID as the {subjectId} path parameter.
post
https://api.checkout.com/workflows/events/subject/{subjectId}/reflow
If successful, you receive a 202 response.
To re-initiate all actions associated with a specific subject and workflow combination, call the Reflow by subject and workflow endpoint. Provide the following path parameters:
{eventId}{workflowId}
post
https://api.checkout.com/workflows/events/subject/{subjectId}/workflow/{workflowId}/reflow
If successful, you receive a 202 response.