Events out, the moment they happen.
Subscribe to the events you care about, and Dika Ops calls your endpoint when they happen: an order is approved, stock drops below the minimum, an invoice is paid. Every message is signed, retried if your side is down, and logged.
Webhooks, piece by piece.
Hear about a change the moment it happens, instead of asking every minute.
What teams use it for.
Post to your chat channel when a big order is approved or a payment lands.
Update your website, BI tool or logistics partner the second a record changes.
Trigger a workflow in another tool without polling the API.
Connected in four steps.
- 01
Create a webhook in Settings and enter your endpoint URL.
- 02
Pick the events to send, and the token whose scope limits the data.
- 03
Check the signature on your side with the shared secret.
- 04
Send a test event, check the delivery log, then switch it on.
Webhooks, answered.
What if my endpoint is down?
Deliveries are retried with growing gaps for up to 24 hours, then marked as failed in the log so you can replay them.
Do events arrive in order?
Each event carries a timestamp and a sequence number, so you can put them back in order if they arrive out of sequence.
What data is in a webhook?
The event type, the record ID and the fields the token's scope allows. Fetch the full record over the API when you need more.
Can I filter events?
Yes. Subscribe per event type, and narrow by warehouse, company or status.
Run the whole company from one place.
Dika Ops is in closed beta. We onboard a few companies at a time and set everything up with you.