Managing Webhooks

Once a webhook exists, you manage it from the Webhooks list and its details page: turn delivery on and off, keep alert emails current, copy the secret or public key, and delete webhooks you no longer need.

Webhook list

The Webhooks page (Developer > Webhooks) shows every webhook in the Space.

A warning icon appears next to the URL when a webhook is Active but has no alert emails. Add at least one, so someone hears about failing deliveries.

Webhook details page

Open a webhook to see its configuration and delivery history.

The header shows the name, status (Active or Inactive), a copyable ID, the creation time, and the Enable or Disable and Delete actions. Below it:

Further down, the Event Deliveries table lists every delivery. See Monitoring and debugging.

Enable and disable

Disable a webhook to pause it without losing its configuration, for example while your endpoint is under maintenance, before you delete it, or while you debug something else.

1. Open the webhook details page.
2. Click Disable (or Enable).
3. Confirm in the dialog.

Replay is unavailable while a webhook is disabled.

Edit alert emails

1. Open the webhook details page.
2. In Alert Emails, click Edit (or Add if none are set).
3. Add, remove or change addresses, up to two in total.
4. Click Save.

Changes apply to future failure alerts at once; past alerts are not resent. If alerts stop arriving, check spam folders, confirm the addresses, and check that deliveries are actually failing: no failures, no alerts.

Copy the secret or public key

Verification credentials are on the details page, under Security.

• HMAC-SHA256: the secret is masked. Show it or copy it, and keep it secret. If it may have leaked, create a new webhook with a fresh secret and delete the old one.
• ECDSA P-256: click View Public Key and copy the whole PEM, including its header and footer lines. The public key isn't secret; only Monime holds the private key.

Delete

Deleting is permanent. Consider disabling instead if you might need the webhook again.

1. Open the webhook details page.
2. Click Delete.
3. Confirm in the dialog.

The webhook is removed, no new deliveries are created, scheduled deliveries are dropped, and its delivery logs become inaccessible. To undo a deletion, create a new webhook with the same configuration.

Organise multiple webhooks

• By environment: one webhook per environment (development, staging, production). With a single endpoint that routes events by name, this is the simplest setup.
• By system: one webhook per downstream system (accounting, CRM, notifications), each with its own events, secret and alert emails.
• By event group: separate high-volume events from low-volume, critical ones.
• By release: one webhook per API release, if you use more than one.

Avoid many webhooks pointing at the same endpoint: each adds configuration and makes monitoring harder.

Create a new webhook or update?

Next steps

• Monitoring and debugging
• Delivery and retries