Sumsub Python API Docs | dltHub
Build a Sumsub-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
Sumsub is a full-stack verification platform providing REST APIs for identity and business verification, AML screening, and fraud monitoring. The REST API base URL is https://api.sumsub.com and all requests require X-App-Token, X-App-Access-Ts, and X-App-Access-Sig headers for HMAC-SHA256 request signing.
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 Sumsub data in under 10 minutes.
What data can I load from Sumsub?
Here are some of the endpoints you can load from Sumsub:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| audit_trail_events | /resources/auditTrailEvents/list | GET | Retrieve audit trail events using forward-only cursor pagination. | |
| applicant_actions | /resources/applicantActions/-;applicantId={applicantId} | GET | list.items | List paginated applicant actions. |
| questionnaires | /resources/api/questionnaires/list | GET | list.items | Retrieve a list of all questionnaires. |
| applicant_action | /resources/applicantActions/{actionId}/one | GET | Get a single applicant action (check result). | |
| applicant_data | /resources/applicants/{applicantId}/one | GET | Get applicant data for a specific applicant. |
How do I authenticate with the Sumsub API?
Authentication requires three headers: X-App-Token (the app token), X-App-Access-Ts (current Unix timestamp in seconds, UTC), and X-App-Access-Sig (a lowercase HEX HMAC-SHA256 signature). The signature is generated using the secret key on a concatenation of the timestamp, uppercase HTTP method, URI (with query params), and raw request body.
1. Get your credentials
- Log in to your Sumsub dashboard. 2. Navigate to the 'Dev space' or 'Integration' section (depending on your account dashboard version). 3. Select 'App Tokens'. 4. Click 'Generate app token'. 5. Enter a preferred name for the token and configure the required permissions. 6. Click 'Generate app token'. 7. Save the App Token and Secret Key immediately in a secure location, as they are displayed only once.
2. Add them to .dlt/secrets.toml
[sources.sumsub_source] api_key = "REPLACE_ME"
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 Sumsub 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 sumsub_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline sumsub_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset sumsub_data The duckdb destination used duckdb:/sumsub.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 POST /resources/accessTokens and GET /resources/applicants/{applicantId}/one from the Sumsub 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 sumsub_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.sumsub.com", "auth": {"type": "api_key", "api_key": api_key, "name": "X-App-Token", "location": "header"}, }, "resources": [ {"name": "audit_trail_events", "endpoint": {"path": "resources/auditTrailEvents/list", "data_selector": "items"}}, {"name": "questionnaires", "endpoint": {"path": "resources/api/questionnaires/list", "data_selector": "list.items"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="sumsub_pipeline", destination="duckdb", dataset_name="sumsub_data", ) load_info = pipeline.run(sumsub_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("sumsub_pipeline").dataset() sessions_df = data.audit_trail_events.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM sumsub_data.audit_trail_events LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("sumsub_pipeline").dataset() data.audit_trail_events.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 Sumsub data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example 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 Sumsub?
Request dlt skills, commands, AGENT.md files, and AI-native context.