---
title: "Replay a webhook event"
method: POST
path: "/v1/webhooks/replay"
tags: ["Webhooks"]
---

# Replay a webhook event

`POST /v1/webhooks/replay`

Replay a previously generated webhook event by creating a new outbound delivery attempt. Use this when your endpoint missed or rejected an earlier delivery and you need Bachs to send that event again.

Common errors:
- `400 BAD_REQUEST`: No supported lookup field was provided. Resolution: provide at least one of `event_id`, `charge_id`, or `reference`.
- `401 UNAUTHORIZED`: Authorization is missing, invalid, or revoked. Resolution: send a valid bearer credential.
- `404 NOT_FOUND`: No matching webhook event could be resolved for your lookup values. Resolution: verify IDs/references and retry.

## Request body

- union — Provide at least one identifier. If `event_id` is provided, that exact event is replayed. Otherwise, the replay target is resolved by `charge_id` or `reference`.
  - object
    - `event_id` string, required — Webhook event ID to replay directly.
    - `charge_id` string — Charge ID used to resolve the latest webhook event for that charge.
    - `reference` string — Checkout reference used to resolve charge and replay latest webhook event.
  - object
    - `event_id` string — Webhook event ID to replay directly.
    - `charge_id` string, required — Charge ID used to resolve the latest webhook event for that charge.
    - `reference` string — Checkout reference used to resolve charge and replay latest webhook event.
  - object
    - `event_id` string — Webhook event ID to replay directly.
    - `charge_id` string — Charge ID used to resolve the latest webhook event for that charge.
    - `reference` string, required — Checkout reference used to resolve charge and replay latest webhook event.

## Response `200`

Success - replay request accepted and a new delivery attempt was created.

- object
  - `success` boolean, required — Replay enqueue result.
  - `event_id` string, required — Event ID replayed.
  - `attempt_id` string, required — New webhook attempt ID.
  - `attempt_no` integer, required — Attempt sequence number for that event.
  - `event_type` string, required — Webhook event type replayed.

## Other responses

- `400` — Bad Request - Validation errors or invalid request format. Check the `details` object for field-specific validation errors. Common causes: missing required fields, invalid data types, values outside allowed ranges, or invalid formats.
- `401` — Unauthorized - Invalid, missing, or expired API key. Verify your API key is correctly formatted and included in the Authorization header as `Bearer sk_sandbox_...` or `Bearer sk_live_...`. Check that your key hasn't been revoked.
- `403` — Forbidden - API key does not have permission for the requested resource. Verify you're using the correct organization's API key and that you're not trying to access another organization's data.
- `404` — Not Found - The requested resource does not exist. Verify the resource ID is correct and that it belongs to your organization.
- `429` — Too Many Requests - Rate limit exceeded. Standard tier allows 100 requests per minute per API key. Wait a few seconds before retrying. Check X-RateLimit-Reset header for when the window resets.
- `500` — Internal Server Error - An unexpected error occurred while processing the request. Retry with exponential backoff. If the issue persists, contact support with your request context.

---

[API](https://skmtc.dev/bachs/apis/bachs-api.md) · [All operations](https://skmtc.dev/bachs/apis/bachs-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/bachs/bachs-api/revisions/f29efa8a22df/schema)