Skip to main content
GET
List webhook deliveries
Requires scope: view:webhooks — see Required scopes. Lists what was delivered to one of your webhooks and whether your endpoint accepted it, so a missed event can be debugged without contacting support. Filter by eventType, status and time. See Debugging deliveries.
Cursor pagination, not page/size — send nextPageCursor / previousPageCursor back exactly as received. How far back the history reaches is the delivery service’s retention window; treat older history as unavailable rather than as proof nothing was sent.
Per-attempt response codes and bodies are on Get a webhook delivery, not on this list.

Authorizations

FlowClient Credentials
Token URL
https://login-staging.venly.io/auth/realms/VenlyFinance/protocol/openid-connect/token

Headers

x-tenant-id
string<uuid>

Which tenant the request is scoped to, among those your token grants. Omit it when the token grants exactly one tenant; it is required when the token grants more than one. A supplied value must exactly match a tenant the token grants.

Absent when required, blank, malformed, or naming a tenant the token does not grant — each gets the same generic 403 forbidden, which reveals neither whether a tenant exists nor which ones you may use. Send the header once: a repeated header is rejected the same way.

Example:

"3fa85f64-5717-4562-b3fc-2c963f66afa6"

Path Parameters

webhookId
string
required

Unique webhook identifier

Query Parameters

eventType
enum<string>

Narrow to one event type Type of a delivered webhook event. Registration carries no event-type selection — a webhook receives every event your company produces — so switch on this value in your handler. The full catalogue, with each payload, is in Webhooks.

Available options:
PING,
PAY_IN_SETTLED,
PAY_IN_FAILED,
PAYOUT_PROCESSING,
PAYOUT_COMPLETED,
PAYOUT_REJECTED,
PAYOUT_FAILED,
PAYOUT_RETURNED,
PAYOUT_ROUTE_ACTIVATED,
PAYOUT_ROUTE_AWAITING_OWNERSHIP_PROOF,
PAYOUT_ROUTE_REJECTED,
VIRTUAL_BANK_ACCOUNT_CREATED,
ACCOUNT_WALLETS_PROVISIONED,
PARTY_VERIFICATION_COMPLETED,
TRANSFER_COMPLETED,
TRANSFER_FAILED
status
enum<string>

Narrow to one delivery status Outcome of a delivery. DISCARDED and FAILURE are different problems: DISCARDED means nothing was ever sent — the endpoint was inactive, or the event was filtered — while FAILURE means your endpoint was called and did not accept the delivery. Only these two can be resent.

  • SCHEDULED — queued for a first or further attempt
  • PROCESSING — an attempt is in flight
  • RETRY — a failed attempt is awaiting its automatic retry
  • SUCCESS — your endpoint accepted the delivery
  • FAILURE — every attempt failed; resendable
  • DISCARDED — never sent; resendable
Available options:
SCHEDULED,
PROCESSING,
RETRY,
SUCCESS,
FAILURE,
DISCARDED
from
string<date-time>

Earliest delivery time, inclusive

to
string<date-time>

Latest delivery time, inclusive

size
integer
default:20

Page size

Required range: 1 <= x <= 100
nextPageCursor
string

Opaque cursor from a previous page, to move forward. Send it back exactly as received — it is not a stable identifier and must not be constructed by hand. Supply either this or previousPageCursor, never both.

Maximum string length: 1024
previousPageCursor
string

Opaque cursor from a previous page, to move back

Maximum string length: 1024

Response

One page of deliveries

success
boolean

Indicates whether the request was successful

result
object

One cursor-delimited page of deliveries. Deliberately not the result/pagination/sort envelope the other list endpoints return — the feed is cursor-based and has no page numbers.