We connect business events in your system to any HTTPS endpoint you control, using webhooks.
A webhook is the simplest way to tell another system that something happened. Instead of that system asking every few minutes whether there is anything new, your business system sends a message the moment an invoice is created or an order changes status. It suits in-house tools, partner systems and automation platforms alike.
What we build with it
- Notifying another system when an invoice is created
- Triggering an external workflow on a stock or status change
- Feeding an internal dashboard in near real time
- Chaining into automation platforms
How it works
- An administrator registers the receiving URL and chooses which events it should receive.
- When one of those events happens, the system builds a message with the event type, time and record details.
- It signs the message with a shared secret and sends it to the URL as an HTTPS POST request.
- The receiver checks the signature and replies to confirm receipt; if it does not, the system retries later.
- Every delivery attempt is logged, so failures can be seen and resent.
Data exchanged
- Event type and timestamp
- The record payload for that event
- A signature header for verification
What is needed to set it up
- An HTTPS endpoint that can receive POST requests
- Event subscription selection
- A shared secret for signature verification
Good to know
- Retries mean a receiver may occasionally get the same event twice, so each event carries a unique ID the receiver can use to ignore repeats.
- Events may arrive slightly out of order. Receivers should rely on timestamps or fetch the latest record rather than assume order.
- Only HTTPS endpoints are accepted, so event data is encrypted in transit.
