Your FrankieOne Starter Pack
When you partner with FrankieOne, your Customer Success Manager will provide you with a starter pack containing everything you need for each environment. You should have the following:| Resource | UAT / Sandbox | Production |
|---|---|---|
| Portal URL | https://portal.kycaml.uat.frankieone.com | https://portal.frankieone.com |
| API Base URL | https://api.uat.frankie.one/v2 | https://api.frankie.one/v2 |
| KYB API Base URL | https://api.uat.frankie.one/v2.1/organizations | https://api.frankie.one/v2.1/organizations |
| Customer ID | Your unique UAT Customer ID | Your unique Production Customer ID |
| API Key | Your secret UAT API Key | Your secret Production API Key |
Authentication Headers
All API requests to FrankieOne must be authenticated. You’ll use the credentials from your starter pack in the request headers.| Header | Required | Description |
|---|---|---|
api_key | Yes | Your secret API key for the specific environment (UAT or Production). |
X-Frankie-CustomerId | Yes | The unique identifier for your account. |
X-Frankie-CustomerChildId | No | The unique identifier for your child account. |
X-Frankie-Username | No | The email address or identifier of the operator performing the action. Highly recommended for auditing purposes. |
X-Frankie-Channel | No | The channel the request originates from (e.g., API, PORTAL, ONESDK). Useful for analytics and routing. |
Keep Your API Key Secure
Yourapi_key is a secret and should be treated like a password. Store it securely on your backend and never expose it in client-side code or public repositories. If you suspect a key has been compromised, contact support immediately.Quickstart in 3 Steps
Follow these steps to ensure your credentials are correct and your environment is ready for integration.1
1. Test Your Connection
The easiest way to verify that your credentials and connection are working is to call our simple health check endpoint: A successful request will return a If you receive an error, double-check that your API key and Customer ID are correct and that you are using the correct base URL for the environment.
/ruok. This endpoint doesn’t require a request body and is used purely to confirm successful authentication.200 OK status and the following JSON response, confirming your keys are valid.2
2. Confirm Your Workflow Setup
Before you can start verifying customers, your account needs to be configured with at least one workflow and one service profile. Your Customer Success Manager typically sets these up for you.You can confirm your setup by calling the You should receive a
GET /v2/workflows endpoint. This will list all the executable workflows available to you.200 OK response with a workflows array. If the array is empty, please contact your Customer Success Manager to get your workflows published.3
3. Make Your First KYB Call
Now you’re ready to onboard a business. You can start by looking up for a business and creating an
organization entity and then execute a workflow on it.You will need the serviceName and workflowName from the previous step.Next Steps
You’ve successfully authenticated and confirmed your setup. Now you’re ready to start building. Follow our implementation guides for common use cases.Lookup a Business
Learn how to search for a business.
Creating & Managing Organizations
Learn the complete lifecycle of an ‘organization’ entity, from creation and retrieval to deletion.
Executing a Workflow
A step-by-step guide to executing a verification workflow against an existing entity.
API Reference
Dive deep into every endpoint, parameter, and response object in our comprehensive API Reference.