Webhooks
VeriflowAPI can monitor registered providers continuously and send webhook notifications when their license status changes or approaches expiry. This eliminates the need to run periodic manual checks.How webhook monitoring works
- You register a provider using the
/v1/monitorendpoint - VeriflowAPI checks that provider’s license status every 24 hours
- When a status change is detected — or expiry is approaching — VeriflowAPI sends a POST request to your webhook URL
- You receive real-time alerts without any polling on your end
Register a provider for monitoring
Request body
Parameters
Response
Webhook event payload
When a status change or expiry alert is triggered, VeriflowAPI sends a POST request to yourwebhook_url with this payload:
Webhook event types
Verifying webhook signatures
Every webhook request includes aVeriflow-Signature header. You must verify this signature to ensure the request is genuinely from VeriflowAPI and has not been tampered with.
The signature is computed as an HMAC-SHA256 hash of the raw request body using your webhook_secret.
Verification example — Python
Verification example — Node.js
Retry policy
If your webhook endpoint returns a non-2xx response or times out, VeriflowAPI will retry with exponential backoff:
After 5 failed attempts, the event is marked as failed and you will receive an email notification at your account email address.
Responding to webhooks
Your webhook endpoint must:- Return a
2xxstatus code within 10 seconds - Return
200 OKfor events you have successfully processed - Return
200 OKeven for event types you choose to ignore (to prevent unnecessary retries)