Security
Principles
-
We never send back analysis results or transaction data over webhooks. An API client has to explicitly request that data through the Navigator API. From our perspective, we cannot ensure that the webhook endpoint belongs to you, even though it is specified by you. Therefore, we only ever send out minimally useful information (events).
-
A webhook request contains a signature in the
X-Navigator-Signature
HTTP-header that can be verified with the code below. It allows you to ensure that the request came from RiskQuest Navigator and not some other party. -
The webhook URL can only be called over HTTPS. We do not allow creating a webhook with HTTP.
Verifying request authenticity
The Python script below encapsulates our response payload signature and verification code. It can be used to validate our signatures from your side.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 |
|