Create webhook
Create a new webhook configuration. Maximum 50 webhooks per user.
name, url and events are required. url must be a valid URL and events must contain at least one event. Whitespace is trimmed from url before validation.
Webhooks are auto-disabled only once the endpoint has had no successful delivery for 3 days AND has either reached 20 consecutive terminal failures (each one an event that exhausted the full retry ladder) or been failing continuously for 3 days. The owner is emailed; re-enable it with isActive: true.
A restricted (zrk_) API key can only subscribe to events whose resource group the key holds; an event outside the key's groups is rejected with 403, so a restricted key can never create a subscription broader than itself.
disabledResourceGroups restricts the subscription itself, independently of which key or session later reads it. Events in a disabled group are dropped before delivery to this endpoint, on live delivery and on every replay path (test fire, redelivery, dead-letter requeue), even if they are listed in events. Omit it to receive everything in events, which is how existing subscriptions behave. A restricted key's own disabled groups are always unioned in.
profileIds pins the subscription to a set of profiles and accountIds to a set of connected accounts: only events attributable to one of the listed ids are delivered, and a subscription with both lists must match on both. Use them to send test accounts to a staging endpoint. Ids outside your team are rejected with 404 (profile_not_found, account_not_found).
Request body
Response
Webhook created successfully