Your webhook delivery log

The caller's own self-serve webhook delivery log -- every delivery for their own customer, most recent first.

Each entry carries the idempotency_key the delivery was sent with (also its X-Reqbeat-Idempotency-Key header, and the id of the billed unit on your invoice) plus the response_status your endpoint returned, so a charge can be matched to the delivery that earned it without a support thread. A NULL response_status means we observed no HTTP response: the delivery has not been attempted yet, the connection failed outright, or it was mailed to a hosted-email endpoint.

Requires the webhooks scope.

get/v1/webhook-deliveries

Request

  • Base URL: https://api.reqbeat.com
  • URL: https://api.reqbeat.com/v1/webhook-deliveries
  • Auth: one of:
    • API key in header X-API-Key
    • HTTP bearer

Response

Successful Response

idinteger required
statusstring required
attempt_countinteger required
watch_idinteger required
event_seqinteger required
idempotency_keystring required
event_typestring required
webhook_urlstring required
created_atstring date-time required
delivered_atstring date-time nullable required
response_statusinteger nullable required
response_msinteger nullable required

Changes

No recorded changes to this operation across all 1 revision of this API.