Get a single webhook registration visible to the authenticated machine principal. Access requires a machine API key with webhooks:read scope for the bound organization. Current producers emit transactions.sync_available and connection.status_changed, and test can be triggered explicitly via the API. The remaining spec-defined event types are reserved for upcoming producers.
Opaque API key passed as Authorization: Bearer <key>. Keys are organization-bound, environment-bound (live or test), scope-carrying, and expiring. Create and manage keys via the console.
Successful Response
Stable, immutable identifier for the webhook registration.
HTTPS URL where events are delivered via POST.
2048^https://.+Event types to subscribe to. Current producers emit transactions.sync_available and connection.status_changed, and test can be triggered explicitly via the API. The remaining spec-defined event types are reserved for upcoming producers.
connection.status_changed, account.created, account.updated, transactions.sync_available, transfer.status_changed, test HMAC-SHA256 signing secret for webhook delivery verification. The server includes a Waycore-Signature header on each delivery using the format t=<unix>,v1=<hex>, where v1 is the HMAC-SHA256 of <timestamp>.<raw_body>. Only returned in full on creation; subsequent reads return a masked value.
Whether this webhook registration is enabled. Deliveries are sent only to active webhook registrations.
When the webhook was registered.
When the webhook registration last changed.
Opaque client-defined metadata.