Security

hmac verification for events klavi defaults to using the secretkey and sha 256 hmac algorithm to sign the payload the following parameter will be included in the request header that klavi post to you x klavi signature 11fad26ccd04a59085a738b8e20be5f4e01887a3c5cdc88cd37bf431e843083e x klavi timestamp 1740716924 we recommend that you verify the signature of the webhook tips for best practice create a sha 256 hmac of the request body using your secretkey as the key compare it to the signature included on the x klavi signature header if the two are equal then the request is valid, otherwise, it is spoofed store the eventid and ignore webhooks with an id that have already been processed to prevent replay attacks the x klavi signature and x klavi timestamp header gets added to every event sent allowed ip addresses to ensure webhook notifications reach your webhook listener server, you must add the following klavi ip addresses to your firewall’s allowlist environment ip address sandbox 18 231 92 86 testing 18 231 92 86 production 18 230 43 17 no matter how you receive shared data, the export ip addresses for klavi's various environments are as shown above if partners have stricter security requirements, you can only allow access to the above ip addresses