Orange KYC Match Python API Docs | dltHub
Build a Orange KYC Match-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Orange KYC Match – CAMARA API is a service that validates a user's identity attributes by matching them against KYC data held by mobile network operators. The REST API base URL is https://api.orange.com/camara/ofr/kyc-match/v0.2 and All requests require a Bearer access token obtained via CIBA OAuth..
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 Orange KYC Match data in under 10 minutes.
What data can I load from Orange KYC Match?
Here are some of the endpoints you can load from Orange KYC Match:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| match | /match | POST | Submits identity attributes and returns match result fields. | |
| No additional GET endpoints were identified in the provided documentation. |
How do I authenticate with the Orange KYC Match API?
The API uses CIBA 3‑legged OAuth to obtain a Bearer access token. Every request must include the header Authorization: Bearer {access_token}.
1. Get your credentials
- POST to
https://api.orange.com/es/openapi/oauth/v2/bc-authorizewith client credentials to obtain anauth_req_id. - Poll
https://api.orange.com/es/openapi/oauth/v2/tokenusing theauth_req_iduntil anaccess_tokenis returned. - Store the
access_tokenand use it in theAuthorization: Bearerheader for API calls.
2. Add them to .dlt/secrets.toml
[sources.orange_kyc_match_source] access_token = "your_access_token_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:
uv venv && source .venv/bin/activate uv pip install "dlt[workspace]"
1. Install the dlt AI Workbench:
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:
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 Orange KYC Match 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:
python orange_kyc_match_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline orange_kyc_match_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset orange_kyc_match_data The duckdb destination used duckdb:/orange_kyc_match.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline orange_kyc_match_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 match and health from the Orange KYC Match 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 orange_kyc_match_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.orange.com/camara/ofr/kyc-match/v0.2", "auth": { "type": "bearer", "access_token": access_token, }, }, "resources": [ {"name": "match", "endpoint": {"path": "match"}}, {"name": "health", "endpoint": {"path": "health"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="orange_kyc_match_pipeline", destination="duckdb", dataset_name="orange_kyc_match_data", ) load_info = pipeline.run(orange_kyc_match_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("orange_kyc_match_pipeline").dataset() sessions_df = data.match.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM orange_kyc_match_data.match LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("orange_kyc_match_pipeline").dataset() data.match.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 Orange KYC Match 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.
Troubleshooting
Authentication errors
If the Bearer token is missing, expired, or invalid, the API returns 401 Unauthorized with an error object containing a code and message describing the authentication failure.
Validation errors
When required request fields are absent or malformed, the service responds with 400 Bad Request and provides an error model { "code": ..., "message": ..., "description": ... } detailing the problem.
Server errors
Unexpected conditions result in 5xx responses. The error payload follows the same structure as above.
Note: Pagination quirks and rate‑limit details were not found in the provided documentation.
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.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install
Was this page helpful?
Community Hub
Need more dlt context for Orange KYC Match?
Request dlt skills, commands, AGENT.md files, and AI-native context.