FrankieOne Python API Docs | dltHub

FrankieOne is an identity verification, compliance, and fraud prevention platform. The REST API base URL is https://api.frankie.one/v2 and All requests require an API key and Customer ID headers for authentication..

dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv pip install "dlt[workspace]" and start loading FrankieOne data in under 10 minutes.

---

What data can I load from FrankieOne?

Here are some of the endpoints you can load from FrankieOne:

---

How do I authenticate with the FrankieOne API?

FrankieOne uses header‑based API credentials: include api_key (your secret API key) and X-Frankie-CustomerID (your Customer ID) in request headers.

1. Get your credentials

1. Sign in to the FrankieOne Portal (production: https://portal.frankieone.com, sandbox: https://portal.kycaml.uat.frankieone.com).
2. Navigate to the API credentials section or your starter pack.
3. Copy the API Key (api_key) and Customer ID (X-Frankie-CustomerID) provided there.
4. Store these values securely and use them in request headers as described in the authentication section.

2. Add them to .dlt/secrets.toml

Copy
[sources.frankie_one_source]
api_key = "your_api_key_here"
customer_id = "your_customer_id_here"

dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.

---

How do I set up and run the pipeline?

Set up a virtual environment and install dlt:

Copy
uv venv && source .venv/bin/activate
uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

Copy
dlt ai init --agent <your-agent> # <agent>: claude | cursor | codex

This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →

2. Install the rest-api-pipeline toolkit:

Copy
dlt ai toolkit rest-api-pipeline install

This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →

3. Start LLM-assisted coding:

Use /find-source to load data from the FrankieOne API into DuckDB.

The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.

4. Run the pipeline:

Copy
python frankie_one_pipeline.py

If everything is configured correctly, you'll see output like this:

Copy
Pipeline frankie_one_pipeline load step completed in 0.26 seconds
1 load package(s) were loaded to destination duckdb and into dataset frankie_one_data
The duckdb destination used duckdb:/frankie_one.duckdb location to store data
Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

Copy
dlt pipeline frankie_one_pipeline show

This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.

---

Python pipeline example

This example loads workflows and kyc_ruok from the FrankieOne API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def frankie_one_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.frankie.one/v2",
            "auth": {
                "type": "api_key",
                "api_key": api_key,
            },
        },
        "resources": [
            {"name": "workflows", "endpoint": {"path": "v2/workflows", "data_selector": "workflows"}},
            {"name": "kyc_ruok", "endpoint": {"path": "v2/kyc/ruok", "data_selector": "status"}}
        ],
    }
    yield from rest_api_resources(config)


def get_data() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="frankie_one_pipeline",
        destination="duckdb",
        dataset_name="frankie_one_data",
    )
    load_info = pipeline.run(frankie_one_source())
    print(load_info)

To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.

---

How do I query the loaded data?

Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.

Python (pandas DataFrame):

Copy
import dlt

data = dlt.pipeline("frankie_one_pipeline").dataset()
sessions_df = data.workflows.df()
print(sessions_df.head())

SQL (DuckDB example):

Copy
SELECT * FROM frankie_one_data.workflows LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("frankie_one_pipeline").dataset()
data.workflows.df().head()

See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.

---

What destinations can I load FrankieOne data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.

---

Troubleshooting

Authentication failures

If you receive 401/403 responses, verify that both api_key and X-Frankie-CustomerID headers are present and correct. Use the /v2/kyc/ruok health endpoint to confirm credentials.

Empty workflows or missing resources

If GET /v2/workflows returns an empty workflows array, your account may not have any published workflows. Contact your Customer Success Manager to enable workflows for your Customer ID.

Pagination and large result sets

Many list endpoints return arrays under keys like workflows, entities, or checks. Use standard paging parameters if supported by the endpoint (see API reference for specific query params). If results appear truncated, ensure pagination parameters are supplied correctly.

Ensure that the API key is valid to avoid 401 Unauthorized errors. Also, verify endpoint paths and parameters to avoid 404 Not Found errors.

---

Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI Workbench:

• data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
• dlthub-runtime — Deploy, schedule, and monitor your pipeline in production.

Copy
dlt ai toolkit data-exploration install
dlt ai toolkit dlthub-runtime install

• How to deploy a pipeline
• How to explore your data in marimo Notebooks
• How to query your data in Python with dataset
• Join the dlt community on Slack