Replay a request
Changed onReplays a request through the full pipeline, creating a new request and new events. The original request and its events remain unchanged. Transformations, filters, and other pipeline rules are re-evaluated with the current configuration. By default, replays to all currently active connections on the request source — this also backfills traffic onto connections added after the original request was ingested. If the source has no active connections, the replay still creates a new request, rejected with cause NO_CONNECTION. Optionally specify source_id to target another source — alone it replays onto all of that source’s active connections, or combine it with webhook_ids to target specific connections on that source. webhook_ids without source_id may target any connections in the project; when they span multiple sources the replay fans out into one new request per target source.
Request
- Base URLhttps://api.hookdeck.com/2025-07-01
- Auth
- HTTP bearer
- or HTTP basic
Path parameters
Request ID
Request body
Response
The new requests and events created from the replay
Changes
- warning
added the new
CLI_BINARY_UNSUPPORTEDenum value to the//response property for the response status - info
added the optional property
///to the response with the status - info
added the optional property
///to the response with the status
- warning