Webhooks
Every decision as an event to an endpoint you run: the same id, the same reason codes and the same queue the app received, for your FRM, case manager or SIEM.
On this page
How it works
Every decision DeepID makes is sent as an event to an endpoint you run, with the same id, reasons and queue the app received. Your FRM, case manager or SIEM picks it up from there.
Act on the event in your backend rather than on what the app reports. If your backend needs the decision before the event arrives, it can ask for it by id, server to server.
What it sends
decision.created: every decision, with its action, reason codes, customer message key, queue and policy versionOther event types: agreed in the sandbox
Set-up
- Agree the endpoint in the sandbox
How events are delivered, signed and retried, and the headers your gateway will see, are agreed with your platform team before any contract.
- Receive decision.created
Route it to the system that should act: the FRM for the case, the SIEM for device signals.
- Look a decision up by id when you need it first
Your backend can fetch a decision server to server instead of waiting for the event.