Outgoing webhooks

Telling another system of yours when something happens here — a new invoice, a signed contract, whatever event you choose — by having the product call a URL you give it.

Why "outgoing": a payment gateway's own callback into the product is a webhook too, going the other direction, and lives under Payment gateways in Settings, not here — two screens using the same word for opposite directions is confusing enough that this one is named to avoid it deliberately.

Adding an endpoint: a URL, and which events should call it. Each endpoint gets its own signing secret, shown once at creation with its own rotate action if it ever needs replacing — the same shape as an API key's own single reveal.

Deliveries: every attempt to call your endpoint, whether it succeeded or failed, is listed and searchable — useful for confirming an integration is actually receiving what you think it is, or for diagnosing one that has gone quiet.

Automatic disabling: an endpoint that keeps failing is disabled automatically rather than retried forever against a URL that is clearly not listening; the reason is recorded on the endpoint itself, and re-enabling it is a deliberate action once you have fixed whatever was wrong on your end.

A narrower view: none — managing endpoints and reading their deliveries share the one capability.

When it refuses: no Outgoing webhooks item in your menu means either you lack the API permission or your firm's plan does not include the API module — see API keys, which share both gates.