List webhook deliveries
GET/v1/webhooks/deliveries
List the deliveries of one webhook subscription. Requires the
connector:webhook_deliveries:list scope. filter[webhook_id] is required.
A delivery is the platform's attempt to send one event to one subscription, including
all its retries. Its id is the X-DAN-Delivery-Id header of the requests, and its
event_id is the UUID in X-DAN-Event-Id (the body id is evt_ followed by the same
UUID). Use this list to find events your endpoint did not acknowledge.
status values:
RETRYING: not yet acknowledged; waiting for its first attempt, in progress, or scheduled for a retry;DELIVERED: your endpoint answered2xx;FAILED: permanently failed (a non-retryable status, or the attempt limit was reached). The platform does not send it again.
Verification handshakes (webhook.verification) are not listed.
Filters are combined with AND. filter[created_after] and filter[created_before]
compare against the time the delivery was created and are exclusive.
Ordering and pagination. Newest first (by id, a time-ordered UUID). Use
page[size] (1 to 200, default 20) and follow links.next until it is absent.
Request
Responses
- 200
- 400
- 401
- 403
- 429
- 503
One page of deliveries for the subscription, newest first.
The request is malformed: invalid JSON syntax, an invalid path or query parameter, a
missing required header such as Idempotency-Key, or a single field that fails its own
format rule. Fix the request before retrying; retrying it unchanged fails again.
The bearer token is missing, malformed, expired, signed by an unknown key, or was not issued by the platform IAM for the Lyriq Connector. Obtain a new token and retry. See the Authentication section.
The token is valid but may not perform this request: it lacks the required scope, has
no bank membership, needs an x-dan-bank-id header to choose between several
memberships, names a bank in x-dan-bank-id it has no membership for, or the caller's
bank is suspended or terminated. A new token with the same configuration fails the same
way. See the Authentication section.
The request was refused because a rate limit was reached (code RATE_LIMITED). No
Retry-After header is sent; retry with exponential backoff.
The request could not be served right now. Either the network is not fully operational
(OUTBOUND_HALTED or READ_ONLY: mutations are refused while read endpoints keep
working; OPERATIONAL_STATE_UNKNOWN: the state could not be determined), or a platform
dependency is temporarily unavailable. No Retry-After header is sent; retry later with
backoff. When retrying a mutation, reuse the same Idempotency-Key and body.