Getting Started: Your First API Call

This guide will walk you through setting up your environment, authenticating, and making your first successful API call to the FrankieOne platform.

Welcome to the FrankieOne API! This guide provides the essential information to get you up and running. Our goal is to help you make your first successful API call in minutes.

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:

ResourceUAT / SandboxProduction
Portal URLhttps://portal.kycaml.uat.frankieone.comhttps://portal.frankieone.com
API Base URLhttps://api.uat.frankieone.com/v2https://api.frankieone.com/v2
Customer IDYour unique UAT Customer IDYour unique Production Customer ID
API KeyYour secret UAT API KeyYour 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.

HeaderRequiredDescription
api_keyYesYour secret API key for the specific environment (UAT or Production).
X-Frankie-CustomerIDYesThe unique identifier for your account.
X-Frankie-UsernameNoThe email address or identifier of the operator performing the action. Highly recommended for auditing purposes.
X-Frankie-ChannelNoThe channel the request originates from (e.g., API, PORTAL, ONESDK). Useful for analytics and routing.
Keep Your API Key Secure

Your api_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: /ruok. This endpoint doesn’t require a request body and is used purely to confirm successful authentication.

cURL
$curl --location '[https://api.uat.frankieone.com/v2/ruok](https://api.uat.frankieone.com/v2/ruok)' \
>--header 'api_key: {{your_uat_api_key}}' \
>--header 'X-Frankie-CustomerID: {{your_uat_customer_id}}'

A successful request will return a 200 OK status and the following JSON response, confirming your keys are valid.

Response
1{
2 "status": "OK"
3}

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.

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 GET /v2/workflows endpoint. This will list all the executable workflows available to you.

cURL
$curl --location '[https://api.uat.frankieone.com/v2/workflows](https://api.uat.frankieone.com/v2/workflows)' \
>--header 'api_key: {{your_uat_api_key}}' \
>--header 'X-Frankie-CustomerID: {{your_uat_customer_id}}'

You should receive a 200 OK response with a workflows array. If the array is empty, please contact your Customer Success Manager to get your workflows published.

Response
1{
2 "requestId": "req_01J...",
3 "workflows": [
4 {
5 "serviceName": "KYC",
6 "workflowId": "wf_01J...",
7 "workflowName": "Standard-KYC-AU",
8 "type": "SYSTEM",
9 "lifecyclePhase": "ONBOARDING"
10 }
11 ]
12}
3

3. Make Your First Verification Call

Now you’re ready to perform your first check. The most fundamental call is to create an individual and execute a workflow in a single request. This is the fastest way to verify a new customer.

You will need the serviceName and workflowName from the previous step.

For a detailed guide on this process, see our Electronic KYC with Government ID guide.


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.