Skip to main content
Use this when your endpoint missed an event or returned a non-2xx response and you want Bachs to deliver the event again.

​
When To Use This Endpoint

Replay webhooks when:
  • Your endpoint was temporarily unavailable during earlier delivery attempts.
  • You fixed signature verification or payload handling and need a resend.
  • You need to re-drive downstream processing for a specific event.

​
Request

​
Method & Path

​
Required Headers

​
Request Fields

At least one lookup field is required.
​
string
Required: NoReplay this exact event ID directly.
​
string
Required: NoResolve the latest webhook event linked to this charge and replay it.
​
string
Required: NoResolve checkout by reference, then replay the latest event for the linked charge.

​
Resolution Priority

When multiple fields are provided, replay resolution behaves as:
  1. event_id (direct event lookup)
  2. charge_id
  3. reference

​
Request Example

​
Response

​
200 - Success

​
Response Fields

​
string
Webhook event selected for replay.
​
string
Newly created delivery attempt ID.
​
integer
Attempt sequence number for this event after replay was created.
​
string
Event type associated with the replayed event.

​
Error Responses

Cause: No supported lookup field was provided.Resolution: Provide at least one of event_id, charge_id, reference, or transaction_id.
Cause: Authorization is missing, invalid, or revoked.Resolution: Send a valid bearer credential.
Cause: No matching webhook event could be resolved for your lookup values.Resolution: Verify IDs/references and retry.