Manage webhook endpoints
Add, test, edit and control endpoints that receive email events.
Use a sample event to check connectivity, authentication and parsing before using webhook notifications in your app.
Add an endpoint
- Open Webhooks and click Add endpoint.
- Enter a public Endpoint URL using HTTPS and a valid certificate.
- Add an optional Description, such as
Order service. - Choose Events to send and Sending domains.
- Configure an Auth header if your server requires it.
- Click Add endpoint.
| Setting | How to choose |
|---|---|
| Events to send | All events includes future event types; a selected set limits notifications to those types. |
| Sending domains | All domains covers the workspace; select domains to restrict the endpoint's notifications. |
| Auth header | Set a header name and secret value your server checks on every request. |
A workspace supports up to 10 endpoints; the same URL can't be added twice in one workspace. New endpoints receive events occurring after creation, not an automatic history of older messages.
Your server receives an HTTPS POST containing a JSON list of events. For payload fields, authentication and response requirements, see Webhooks and the event reference.
Send a test event
Click Test in the endpoint list, or open the endpoint and click Send test. SendMero sends a sample delivered event marked "test": true.
Review the result, Timing, and Your server's response. Use Show request body to inspect the sample, and Send again after a fix. A test event doesn't send an email or prove that a real email was delivered. Make sure your handler recognizes it as a test.
Resolve failed tests and calls →
Edit an endpoint
- Click the pencil icon in the list, or open the endpoint and click Edit.
- Update the URL, description, selected events or domains.
- Click Save changes, then send a test.
The auth value is encrypted and isn't shown again after saving. The dashboard shows a masked hint. To change it, click Replace value and enter the new secret; update your server to expect the same value. Turning off the auth-header toggle removes that header from future requests.
Understand endpoint status
| Status | Meaning |
|---|---|
| Active | The endpoint is enabled for event delivery. Check Last call and the log for individual results. |
| Paused | Repeated failures paused normal delivery. Waiting events are kept and periodic probes test recovery. |
| Disabled | No webhooks are being sent. The detail page explains whether this was manual, due to prolonged failures, or selected domains being removed. |
Lag shows how far delivery is behind, or Up to date. Last call shows the latest request result and time; it doesn't guarantee every earlier call succeeded.
Disable or enable delivery
Use the pause icon (Disable endpoint) in the list or Disable on the detail page, then confirm. Use Enable to start delivery again after resolving the issue.
When re-enabled, events within the last 24 hours can catch up; older events are skipped by automatic catch-up. Check the delivery log and use replay where available. Disabling an endpoint affects notifications, not email sending.
If a selected sending domain is deleted, it is removed from the endpoint filter. An endpoint left without any selected domains is disabled; review its domain selection before enabling it again.
Inspect logs and graphs
Click an endpoint row to open its details:
| Tab | What it shows |
|---|---|
| Delivery log | Individual calls, results, event counts, source and duration. Filter by success or failure and a time range. |
| Graphs | Calls by result and response-time trends for the selected period. |
Logs cover the last 30 days. Replay is available for calls from the last 7 days. See Troubleshoot webhook deliveries for inspection and replay steps.
Delete an endpoint
Click Delete endpoint and confirm Delete. This cannot be undone. No more webhooks are sent to that endpoint; its delivery log is kept for 30 days. Use Disable if you only need to stop it temporarily.
Actions depend on your workspace permissions. If a control is unavailable, ask your administrator to review Roles and permissions.
- Give each endpoint a description that identifies the receiving service.
- Test after changing the URL or auth header.
- Keep handlers safe for duplicate events and future event types if subscribed to all events.