Skip to content
Hardcount
Run it locally
Pre-1.0 · one maintainer · Stripe and cards only · no SDKs (client libraries) yet · no production users yet. Docs describe v0.9.1 (29 Oct 2026) · What’s new →

List an endpoint's recent deliveries

GET
/v1/webhook-endpoints/endpoints/{id}/deliveries
curl --request GET \
--url 'http://localhost:8080/v1/webhook-endpoints/endpoints/example/deliveries?limit=50&offset=0' \
--header 'Authorization: Bearer <token>'

The endpoint’s deliveries, newest first. Each row names the event it carried. A deleted or unknown endpoint returns 404. The endpoint itself is GET /v1/webhook-endpoints/endpoints/{id}.

id
required
string
limit
integer
default: 50 >= 1 <= 100

Rows per page, from 1 to 100. Default 50. Any other value, or one that is not a whole number, is a 422 with param: limit.

offset
integer
0

Rows to skip, 0 or more. Default 0. A negative value, or one that is not a whole number, is a 422 with param: offset.

Endpoint and its deliveries

Media typeapplication/json
object
data
required
Array<object>
object
id
required
string
event_id
required
string
event_type
required
string
is_replay
required

The delivery came from a replay.

boolean
replay_of_event_id
string
status
required
string
Allowed values: pending succeeded failed
status_code
required

HTTP status from the receiver. 0 when there was no response.

integer
attempt_count
required
integer
response_body
required

First 4 KB of the receiver’s response.

string
error
required
string
created_at
required
string format: date-time
completed_at
required
string format: date-time
nullable
next_retry_at
required
string format: date-time
nullable
total
required

How many rows match the request’s filters, on every page, not only this one. The audit log and the customer list’s search and name or email sort say where they stop counting.

integer

Example

{
"data": [
{
"status": "pending"
}
]
}

No such endpoint, or it was deleted

Media typeapplication/json
object
error
object
type

One of invalid_request_error, authentication_error, rate_limit_error or api_error. Every error the API answers has this shape, including an unknown path (404, code route_not_found) and a method the path does not take (405, code method_not_allowed, with an Allow header). The few exceptions are listed in docs/api-surface.md.

string
code
string
message
string
request_id
string
param

The request field the error is about. Sent only when the error names one. A request body may hold only the fields its operation lists, spelled and cased as listed: any other field, or one the server sets (such as id), is refused with 422 and param naming it. An operation with no request body lists no fields: send no body, {} or null. The Stripe and Postmark webhooks and the LiteLLM callback take their sender’s body as it comes.

string

Example

{
"error": {
"type": "invalid_request_error"
}
}

limit or offset is out of range or not a whole number, or the request sends the removed after cursor (param names it)

Media typeapplication/json
object
error
object
type

One of invalid_request_error, authentication_error, rate_limit_error or api_error. Every error the API answers has this shape, including an unknown path (404, code route_not_found) and a method the path does not take (405, code method_not_allowed, with an Allow header). The few exceptions are listed in docs/api-surface.md.

string
code
string
message
string
request_id
string
param

The request field the error is about. Sent only when the error names one. A request body may hold only the fields its operation lists, spelled and cased as listed: any other field, or one the server sets (such as id), is refused with 422 and param naming it. An operation with no request body lists no fields: send no body, {} or null. The Stripe and Postmark webhooks and the LiteLLM callback take their sender’s body as it comes.

string

Example

{
"error": {
"type": "invalid_request_error"
}
}