Webhook
In Arabic الويب هوك (Webhook)
A webhook is an automatic HTTP call that one system sends to an address in another system as soon as a chosen event happens, carrying the event’s data.
In plain words
Instead of the other system asking every few minutes whether anything changed, a webhook tells it straight away. A new customer is created, and within seconds your middleware or another application has the record, with no polling and no nightly file.
The receiving end needs to know the call is genuine, so webhooks are usually signed with a shared secret and checked against a timestamp. Because the other end can be down, failed calls are retried and, if they still fail, kept so they can be replayed.
The common mistake is sending webhooks with no record of what was delivered. When the other system says it never got a customer, nobody can prove otherwise. Log every delivery, its answer and its retries.
- Event
- New customer created
- Attempt 1
- Timed out
- Attempt 2, a minute later
- 200 OK
- Deliveries logged
- 2
- Status
- Delivered on the second attempt
In Axon Suite
How Axon Suite handles it
Axon Suite posts each new customer to your own middleware over a signed webhook, through your field map. Failed calls are retried and kept in a dead-letter queue for you to replay.
Feature
Signed webhooks you can replay
Axon Suite posts each new customer to your own middleware through your field map, signed so you know it came from you. Failures are retried, kept for replay, and a kill switch stops sending while you fix the other end.
Open: Signed webhooks you can replay