Replays every settled delivery the filter selects, up to the per-request cap. This is the recovery path after an outage at the receiving end. At least one filter is required; an empty body returns 400. The five filters are the same ones the history endpoint accepts, so an organisation can review a page and then replay exactly what it saw.
This form is lenient, where the single-event form is strict. A delivery that cannot be replayed is reported in skipped with the reason, and the rest are still queued. A status or webhookId filter applies to each delivery's latest generation, so status=PARKED means the deliveries that are parked now.
A single call queues at most 500 events and examines at most 2000 looking for them. Only an event that yields something to queue counts against the cap. truncated: true means the call stopped with matches still unqueued, and calling again makes progress rather than repeating itself.
Separately, an organisation may queue at most 1000 replays per hour; exceeding that returns 429 Too Many Requests and queues nothing. status=PARKED is the usual filter after an outage. It selects the deliveries that exhausted their attempts while the destination was down, and leaves alone anything still working through the ladder.