Replay Failed Webhook Deliveries
Try sending your failed webhook notifications again.
Sometimes a notification can’t reach your server (for example, your server was briefly down). This endpoint takes those failed notifications and tries to send them again right away.
Choosing what to resend
You can add one or more of these optional filters to control what gets resent:
delivery_id— resend just one specific notificationevent_id— resend every failed notification for one specific eventendpoint_id— resend every failed notification for one specific webhooklimit— the most notifications to resend at once (default 100, up to 500)
If you don’t add any filters, the most recent failed notifications are
resent, up to the limit.
Authorizations
The access token received from the authorization server in the OAuth 2.0 flow.
Body
Replay selector for failed webhook deliveries (platform API).
Provide at least one filter, or omit all to replay up to limit
most-recent failures.
Replay a single delivery by UUID.
"a1b2c3d4-e5f6-7890-abcd-ef1234567890"
Replay all failed deliveries for a specific event.
"d4e5f6a7-b8c9-0123-4567-89abcdef0123"
Replay all failed deliveries for a specific endpoint.
"c3a1e8b2-4f6d-4a9c-b2e1-8f3d5a7c9e01"
Maximum number of deliveries to replay.
1 <= x <= 50050
Response
Successful Response
Standard response wrapper for single-object responses and errors.
Generic over the payload type. A route that declares
CommonResponse[SomeModel] gets the real data schema rendered in
OpenAPI/Swagger; a bare CommonResponse leaves data untyped.

