Notifications & Webhooks
FrankieOne provides real-time notifications through webhooks to keep your systems updated about important events and changes.
To set up webhooks, contact help@frankieone.com with your designated contact email. You can configure multiple webhook endpoints for different notification types. Ensure your endpoint is accessible via HTTPS.
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).
Triggered when an IDV biometrics event occurs (for example, token requested, results retrieved).
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. If your endpoint returns a 5xx
or 4xx
status code (other than 400
), the system retries delivery multiple times over a period. A 400
status code stops retries.
Process the Notification Type
Use the notificationType
and function
fields to determine the appropriate action.
Retrieve Workflow Execution Results
Retrieve workflow execution results post-execution by calling 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)
FrankieOne supports JSON Web Token (JWT) authentication to enhance the security of webhook notifications. By enabling JWT signing, you can verify the authenticity and integrity of the payloads sent to your webhook endpoint.
Notification payloads are secured through HTTPS and IP whitelisting. You can also enable JSON Web Token (JWT) signing for additional security. Contact support to enable JWT verification for your account.
JWT Structure
Security Features
- RSA-4096 bit private key encryption
- Customer-specific public key for verification
- HTTPS with secure algorithms
- IP whitelisting
Retry Mechanism
FrankieOne employs a robust retry mechanism to ensure reliable delivery of webhook notifications:
- Initial Retry: Immediately after the first failure.
- Exponential Backoff: Retries occur at increasing intervals.
- Maximum Retries: Up to 50 attempts over 24 hours.
If all retries fail, the message is moved to a Dead Letter Queue (DLQ), and FrankieOne’s support team is notified. Contact support to retrieve messages from the DLQ if necessary.