Webhooks

Your server hears what happened.

A webhook is an endpoint Notifiable calls for one app and one environment. It posts when a notification is delivered, fails, is opened, or is clicked, and when an event you named is recorded.

01

You choose the events

Each endpoint listens for the delivery outcomes you select, and for up to 20 event names. An environment can store five endpoints. A disabled endpoint receives nothing. Development and production do not share them.

02

Every call is signed

Notifiable signs the raw body. The signing secret starts with whsec_ and is stored encrypted. The same webhook id is used on every retry, so a duplicate can be ignored. The push token is not included.

03

Failed calls are tried again

A 2xx response is success. Anything else is tried again immediately, after 1 minute, after 15 minutes, and after 1 hour. The response is kept so you can read what your server returned.

04

Replay the same message

Opening an endpoint shows the latest deliveries, the HTTP status, and the JSON that was posted. Replay sends that message again. The message id does not change. Production endpoints must use https.

Ready to send?

Your app users one notification away.

Connect your app and send your first Notification in minutes.