List webhook endpoints
Active endpoints only — revoked ones are excluded. Never returns a secret.
Answers { data, endpoints, nextCursor }: read data, the field the checkout and buyer-profile lists also use. endpoints is the same array under its original name, and nextCursor is always null because this collection is not paged.
Requires the webhooks.read scope.
A subject-bound key cannot manage webhook endpoints. One endpoint receives the transitions of every checkout the tenant runs, for every end user, so registering or reading them from a single person’s key would be a way to subscribe to everyone else’s activity. 403.
Authorizations
Authorization: Bearer ck_test_… or ck_live_…. There is no other auth scheme — no query-string keys, no request signing, no OAuth.
Response
Active endpoints, newest first. Revoked ones are excluded. Not paged.
The collection. Read this one — it is the field the checkout and buyer-profile lists answer with too. (GET /v1/buyer-sessions is the one list route that has not converged: it answers { sessions, vaultEnabled }.)
The same array under the field's original name, kept because existing callers read it. Identical contents; prefer data in new code.
Always null here — the collection is small and tenant-bounded, so there is nothing to page. Present so a generic list client needs no special case.