Notification Webhooks
List an organization's notification webhooks
List the organization’s registered notification webhooks in a stable order, so pagination is deterministic. The order is not a chronological contract: it keys on the projection row’s own creation time, which a projection rebuild would reset. Results are paginated with 50 items per page. The signing secret is never included — it is shown only once at creation and on rotation.
GET
List an organization's notification webhooks
Authorizations
The access token received from the authorization server in the OAuth 2.0 flow.
Path Parameters
The organization ID of the user's organization
Query Parameters
Required range:
x >= 1Required range:
x >= 1Previous
Register a notification webhookRegister a webhook for the organization, provision its signing secret, and
subscribe it to the given topics — all in one atomic append. The signing secret
is returned once in this response and never again, so the caller must store it
now. A malformed or disallowed URL (non-https outside dev, or an SSRF-blocked
address) is rejected and nothing is created.
Each call registers a new, independent endpoint; it is not idempotent — a retried
or repeated POST with the same URL creates a second webhook with its own secret,
so callers that retry must guard against duplicates. The response is built from
the just-committed create rather than re-read, so a transient read failure can
never strand the one-time secret.
Next
List an organization's notification webhooks
