tickerbot.io
View as markdown
Endpoints › Webhooks

Resend a delivery

POSThttps://api.tickerbot.io/v2/webhooks/{id}/deliveries/{delivery_id}/redeliver

Resend a past delivery, with the exact body it carried, to the webhook's current target.

View as markdown

Body parameters

stringrequired

Webhook id.

stringrequired

The delivery to resend, from GET /v2/webhooks/{id}/deliveries.

Returns

as_ofstring

Server time this response was assembled (ISO 8601).

idstring

The new delivery's id — dlv_…, listed on the deliveries route with its outcome.

webhook_idstring

The webhook it belongs to.

redelivery_ofstring

The original delivery's id. Resending a resend still names the first one. It is the X-Tickerbot-Delivery-Id your endpoint receives.

statusstring

pending — queued, sent on the next delivery pass with the full retry ladder.

created_atnumber

When the resend was queued, in epoch seconds.

Status codes

CodeMeaning
202Queued. The new delivery appears on the deliveries route and runs the full retry ladder like any other.
400Malformed id, a test fire (call /test again instead), or an in-app webhook (nothing goes over the wire).
404Webhook or delivery not found. Deliveries are kept for 90 days.
409webhook_disabled — turn the webhook back on with POST /v2/webhooks/{id}/enable first; or delivery_pending — the delivery is still being retried.

Notes

  • The body is byte-identical to the original delivery. It goes to the webhook's current target_url (or Discord URL) and is signed with its current secret, so a resend after you moved your endpoint lands at the new one.
  • X-Tickerbot-Delivery-Id carries the ORIGINAL delivery id, the same value every retry of it carried. If your receiver dedupes on that header, a resend of something it already processed is recognized as a duplicate.
  • Delivered and failed deliveries can both be resent; test fires cannot. Send an Idempotency-Key header to make a retried call safe: the same key returns the first response instead of queueing a second resend.