Introduction to the API
The FrankieOne API enables seamless integration of comprehensive risk and compliance services into your applications, offering global identity verification and business validation capabilities.
Outbound IP Addresses
Traffic from FrankieOne originates from the following IP addresses.
You must whitelist the three Production IP addresses.
- 52.62.31.108
- 149.167.70.106
- 123.103.207.82
- 13.236.159.198
- 13.237.83.115
- 16.50.141.56
Inbound IP Addresses
We currently don’t support inbound IP address filtering, so you can’t limit what IP address would be able to authenticate using your FrankieOne API credentials.
Key Capabilities
Download our latest Swagger / OpenAPI definition here.
View our Swagger documentation here.
API Fundamentals
Core Principles
Authentication
The API follows RESTful conventions with JSON payloads over HTTPS. We’ve kept it simple with three main HTTP methods:
All API responses include unique IDs (UUIDs) for created resources. Store these IDs - you’ll need them for updates!
Working with Resources
Performing Verifications
Creates entity and runs basic checks
Comprehensive checks
Remember to handle API responses appropriately. All verification endpoints return detailed result objects that should be processed for a complete verification flow.
API Endpoints
Environment Access
Testing environment is available for all users, while UAT and Production environments are restricted to contracted customers only.
Testing / Sandbox
UAT Environment
Production
Use this environment for initial development and testing. It’s free to access and perfect for integration testing.