Docs/Alert webhooks

Alert webhooks

Push events to your tools from Domains, then Alert webhooks. Webhooks require a plan that includes them.

Alert webhooks list with subscriptions and delivery log
Alert webhooks—HTTPS endpoints and event subscriptions.

Add a webhook

  1. Open Domains -> Alert webhooks. If gated, upgrade via Billing & plans.
  2. Click Add Webhook, enter an HTTPS URL, then Save.
  3. Open Subscriptions for that webhook.
  4. Choose the scope and events you want, then Add subscription. To subscribe broadly, use Add all categories (account-wide).
  5. Click Test or Send sample — Aepto delivers immediately and shows success or the HTTP error (not only “queued”).
  6. Use Delivery log for history of successes and failures.

Google Chat, Slack, Discord, and classic Microsoft Teams incoming webhook URLs are supported — Aepto sends a readable text message those apps accept (generic HTTPS endpoints still get the full signed JSON). For payload shape, HMAC, and the Platform API, see Developers → Alert webhooks.

Example event families

Email remains available via Contacts - use Email alerts on the webhooks page as a shortcut back there.

FAQ

Where do I add an alert webhook?

Open Domains → Alert webhooks → Add Webhook, enter an HTTPS URL, and click Save. Plans that include webhooks are listed on Billing & plans.

How do I choose which events fire?

Open Subscriptions for the webhook, pick scope and event types, then Add subscription. Use Add all categories (account-wide) for broad coverage.

Do Google Chat, Slack, Discord, or Teams work?

Yes for common incoming-webhook URLs. Aepto adapts the body for chat.googleapis.com, hooks.slack.com, Discord (/api/webhooks/), and classic Office 365 connectors (webhook.office.com / Outlook hosts). Custom HTTPS receivers get the full structured JSON. Test / Send sample deliver immediately and show HTTP success or failure. Re-enable the webhook if it was auto-paused after repeated failures.

How do I test my endpoint?

Click Test or Send sample after adding a Subscription. Aepto posts immediately and shows the result (not only “queued”). Samples use the same subscription matching as live alerts. Custom receivers should verify the HMAC signature—see Developers → Alert webhooks.

Does Content Monitoring have webhook events?

Yes. Subscribe to content_monitoring (e.g. content_monitoring.monitoring_content_error, content_monitoring.monitoring_content_changed). Website monitoring downtime/recovery/SSL/slow are a separate website_monitoring subscription.

Deliveries are failing—where do I look?

Open Delivery log for the webhook to see HTTP status and retry history. Confirm your URL is HTTPS and returns success quickly.

More answers: FAQ hub.