Yoti Python API Docs | dltHub

Build a Yoti-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.

Last updated:

Yoti provides various APIs for identity verification, age verification, and trust services through a RESTful interface. The REST API base URL is https://api.yoti.com and all requests require an Authorization header with a Bearer token and may require a Yoti-Sdk-Id header.

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 add "dlt[hub]" and start loading Yoti data in under 10 minutes.


What data can I load from Yoti?

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

ResourceEndpointMethodData selectorDescription
e_signature_envelopes/v2/organisations/envelopes/searchGETenvelopesSearch for eSignatures envelopes with filters
trust_api_profiles/accounts/{accountId}/profilesGETFetch profiles in an account
trust_api_moderations/accounts/{accountId}/moderationsGETFetch paged moderations
trust_api_groups/accounts/{accountId}/groupsGETFetch account groups
trust_api_group_profiles/accounts/{accountId}/groups/{groupId}/profilesGETFetch profiles in a specific group

How do I authenticate with the Yoti API?

The API utilizes Bearer authentication. Requests typically require an Authorization header with a Bearer token, and often a Yoti-Sdk-Id header for the SDK identifier.

1. Get your credentials

  1. Log into your account at the Yoti Hub (https://hub.yoti.com/). 2. Once inside your organisation, navigate to the services section or select the 'CREATE' button. 3. Choose the specific product you are integrating (e.g., Identity Verification, Age Verification, or Digital ID). 4. After creating the service, proceed to the 'Keys' tab within your service dashboard. 5. Click 'Generate key pair' to download your PEM file (private key). Ensure you store this file securely, as losing it will require generating a new key pair and reconfiguring your integration. 6. Copy the 'Yoti Client SDK ID' displayed on the dashboard for your backend initialization.

2. Add them to .dlt/secrets.toml

[sources.yoti_source] sdk_id = "your_yoti_client_sdk_id_here" private_key = "-----BEGIN RSA PRIVATE KEY-----\n...\n-----END RSA PRIVATE KEY-----"

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:

uv init uv add "dlt[hub]"

1. Install the dlt AI harness:

uv run dlthub 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:

uv run dlthub ai toolkit install rest-api-pipeline

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 Yoti 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:

uv run python yoti_pipeline.py

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

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

Inspect your pipeline and data:

uv run dlthub 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 /sessions and /oauth/token from the Yoti API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def yoti_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.yoti.com", "auth": {"type": "bearer", "token": api_key}, }, "resources": [ {"name": "e_signature_envelopes", "endpoint": {"path": "v2/organisations/envelopes/search", "data_selector": "envelopes"}}, {"name": "trust_api_profiles", "endpoint": {"path": "accounts/{accountId}/profiles"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="yoti_pipeline", destination="duckdb", dataset_name="yoti_data", ) load_info = pipeline.run(yoti_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):

import dlt data = dlt.pipeline("yoti_pipeline").dataset() sessions_df = data.e_signature_envelopes.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM yoti_data.e_signature_envelopes LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("yoti_pipeline").dataset() data.e_signature_envelopes.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 Yoti data to?

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

DestinationExample value
DuckDB (local, default)"duckdb"
PostgreSQL"postgres"
BigQuery"bigquery"
Snowflake"snowflake"
Redshift"redshift"
Databricks"databricks"
Filesystem (S3, GCS, Azure)"filesystem"

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


Next steps

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

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-platform — Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform

Was this page helpful?

Community Hub

Need more dlt context for Yoti?

Request dlt skills, commands, AGENT.md files, and AI-native context.