Webhooks allows you to receive a notification over HTTP when an event occurs. Currently we support webhooks for one event:
- notification/sent - This event occurs after a customer has been sent a Back in Stock notification email.
Webhooks can be used to integrate Back in Stock with other communication channels you might use with your store. For example, you could receive a webhook when a customer is notified so you can display a notification to the customer in a mobile app.
Webhooks are available to accounts on the Medium store, Large store, and Enterprise plans.
Receiving a webhook
To receive a webhook you’ll need to create a subscription in your Back in Stock account.
- From you Back in Stock dashboard choose Account, Webhooks
- Enter the URL where the webhook notification will be sent.
- Hit Create Webhook
- Enable the webhook by tapping the ‘On/Off’ toggle switch.
The URL you specify should meet the following criteria:
- Is publicly accessible over HTTPS
- Accepts a POST request
- Returns a 200 OK response.
The webhook will be delivered shortly after the email is sent to the customer. If the URL does not return an HTTP 200 response the webhook will be retried several times. A webhook that consistently fails to return a 200 response will be deactivated by the system.
Tip: RunScope offer a handy service called Request Captures which makes it easy to view and debug webhook requests.
A webhook is sent as POST request in JSON format. Here’s an example of the body of the request:
Verifying a webhook request
When your systems receives a webhook you should validate it to ensure it is a genuine request from Back in Stock. You can verify the authenticity by calculating a signature and comparing it to the signature contained in the ‘X-BIS-Signature’ header.
You will need your Back in Stock API key to calculate the signature. You can find your API key from your dashboard under Account, API
The signature calculation uses the same method as a Shopify webhook request: