View as markdown
Endpoints · Webhooks

Delivery history

GEThttps://api.tickerbot.io/v2/webhooks/{id}/deliveries

Recent deliveries for one webhook — what was sent, and what came back.

stringrequired

Webhook id.

enum

Filter by delivery status.

pendingQueued or mid-retry; not yet accepted by your target.
deliveredYour target answered 2xx.
permanent_failureGave up after the retry schedule was exhausted, or the target answered 4xx.
string

Only deliveries created at/after this moment — epoch seconds, epoch milliseconds (13+ digits), or an ISO datetime (since is accepted as an alias). Delivery history is retained for 90 days; deleting a webhook deletes its delivery history with it.

string

Only deliveries created at/before this moment — same value grammar as from. A date-only value means through the end of that UTC day. from after to is a 400.

integerdefault 50

Page size. Max 100.

string

Opaque cursor.

as_ofstring

Server time this response was assembled (ISO 8601).

countnumber

Rows in this page.

next_cursorstring

Opaque token for the next page; `null` on the last page. Pass it back as `cursor`.

deliveriesarray

Attempts, newest first: status, attempt, response code, error, and `body_string` — the exact JSON POSTed.

200
Success — the response shape is documented under Returns above.
400
Invalid webhook id format, invalid ?status value, or a malformed from/to (or from after to).
404
Webhook not found, or owned by another account.
  • Pings and fires, newest first by created_at. Each row carries the metadata (status, attempt, response code, error) plus body_string, the exact JSON POSTed to your target, kept so you can replay or inspect what was sent.
  • Account-scoped: any key on the same account can read any webhook's deliveries.
  • Two separate counters govern failure. Per delivery: after the 6th failed POST (first attempt + 5 retries) the delivery is marked permanent_failure. Per webhook: after 5 *consecutive* deliveries each end in permanent_failure, the webhook is flipped to disabled.
  • Retry schedule: 30s, 2m, 10m, 1h, 6h (5 retries → 6 total POSTs). See /docs/endpoints/webhooks for full delivery semantics.