Notifications & Webhooks
FrankieOne provides real-time notifications through webhooks to keep your systems updated about important events and changes.
To set up webhooks, have your designated contact email help@frankieone.com. You can configure up to three separate endpoint collections for:
- Background function notifications
- Risk change events
- Check process results
Notification Triggers
Triggered when a background request (using X-Frankie-Background: 1
header)
completes.
Triggered when an entity’s state changes (for example, UNCHECKED → PASS, FAIL → PASS).
Triggered when an entity’s risk level changes (for example, LOW → HIGH, NULL → LOW).
A single API request may trigger multiple notifications. For example, a background entity verification request could generate three webhooks: 1. Final risk score change 2. Final status change 3. Background process completion
Webhook Structure
Endpoint Format
FrankieOne appends the requestID
to your configured webhook endpoint:
Payload Examples
Handling Notifications
Receive the Webhook
Your endpoint should respond with a 200 or 202 HTTP status code to acknowledge receipt.
Process the Notification Type
Check the notificationType
and function
fields to determine the appropriate action.
Retrieve Additional Data
For background operations, call the /retrieve
endpoint with the provided requestID
.
When can I `/retrieve` Data?
You can access cached API responses via the /retrieve/{requestID}
endpoint for 7 days. You can retrieve RequestID
s in two cases:
- Background/async calls that generate a FUNCTION webhook notification
- Regular synchronous API calls with a response
Additional Security (JWT Authentication)
We secure notification payloads through HTTPS and firewall IP whitelisting. You can also sign your requests with JSON Web Tokens to add an additional layer of security and verify message validity. Contact support to enable JWT verification for your account.
Retry Mechanism
When webhook delivery fails to more than half of the configured endpoints:
- The system retries delivery every 15 minutes, with up to 50 retries.
- If all 50 retries fail, the message moves to a Dead Letter Queue (DLQ) and notifies our support team