Webhooks
HTTP callbacks to your server when a delivery status changes: no polling, real-time data.
Key points
- Always verify the HMAC signature of incoming requests: it guarantees the payload really comes from NotifyHub.
- Respond 2xx quickly and process the payload asynchronously: slow responses get retried.
- Use the webhook deliveries log for debugging: it shows the payload, your server's response and the retries.
What this page is for
Webhooks notify your system when something happens in NotifyHub, typically delivery status changes (delivered, failed...). You register your server's URL and the events you care about: on each event NotifyHub sends a signed HTTP request with the full payload.
How to use it
The table lists the endpoints with URL, subscribed events, status and last trigger. You can enable/disable an endpoint with the toggle (useful during maintenance on your server) or delete it. Requests are HMAC-signed: the secret for verification is provided when the endpoint is created.
Deliveries and retries
Every call to your endpoint is tracked on the webhook deliveries page, with the payload sent, the response code and the number of attempts: if your server errors, NotifyHub retries automatically, and you can also manually replay a failed delivery. If your endpoint stays down for a long time, check the log to recover the missed events.