Signed webhooks

1. 11. In Integrations, click New webhook.
2. 22. Paste in Address the one the other application gives you.
3. 33. Choose the Events you want to receive and click Save.
4. 44. Copy the signing secret and save it in the destination.

The address has to start with https://. The secret is only shown when the webhook is created. You can have up to 20 webhooks per store.

You can receive sales, refunds, new and cancelled subscriptions, leads, granted and withdrawn access and invoices. Choose only the ones your destination is going to use.

1. 11. Click See deliveries on the webhook's row.
2. 22. Click Send test event.
3. 33. Check under Deliveries that the test appears as Delivered.

Each delivery carries a signature calculated with the secret. The destination recalculates it and compares it before trusting the notice. The code to verify it is in the developer reference. If you lose the secret, click Rotate secret and put the new one in the destination.

If the destination does not answer, OnBio retries up to 8 times with growing waits. If all fail, the delivery stays as Undelivered. When the destination answers again, click Resend the undelivered deliveries. Each one goes out with its original event identifier so the destination recognises the ones it already had.

If deliveries fail many times in a row, OnBio turns the webhook off and lets you know. My webhook is turned off explains it.

Your store tells your tools at once. In the next chapter you automate with Zapier.