OneTrust Python API Docs | dltHub

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

Last updated:

OneTrust is a trust management platform that provides REST APIs for integrating external systems with its various cloud services. The REST API base URL is https://{hostname}/api/{microservice}/{version} and all requests require an 'Authorization' header with a Bearer token.

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 OneTrust data in under 10 minutes.


What data can I load from OneTrust?

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

ResourceEndpointMethodData selectorDescription
data_subjects/api/datasubject/v4/subjectsGETRetrieve list of data subjects
data_subjects_unordered/api/datasubject/v4/subjects/unorderedGETRetrieve unordered list of data subjects
receipt_details/api/consent/v1/receipts/listPOSTRetrieve list of receipts
privacy_requests/api/privacy/v1/requestsGETRetrieve list of privacy requests
consent_purposes/api/consent/v1/purposesGETRetrieve list of consent purposes

How do I authenticate with the OneTrust API?

Authentication is performed by passing an access token in the 'Authorization' header using the Bearer schema (e.g., 'Authorization: Bearer '). The access token can be obtained via the OAuth 2.0 client credentials flow or by using an OAuth 2.0 API Key.

1. Get your credentials

To set up your API credentials in the OneTrust dashboard, follow these steps: 1. Log in to your OneTrust application and click the gear icon in the top right-hand corner to access Global Settings. 2. Navigate to Access Management > Client Credentials. 3. Select either the Client Credentials tab or the API Keys tab based on your integration needs. 4. Click the Add button to create a new entry. 5. Fill in the required details, such as the name, and select the appropriate OAuth scopes for your use case. 6. Upon saving, download or save the generated credentials (client ID and secret for Client Credentials, or the API key token for API Keys) as they will not be visible again.

2. Add them to .dlt/secrets.toml

[sources.onetrust_source] api_key = "your_api_key_or_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 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 OneTrust 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 onetrust_pipeline.py

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

Pipeline onetrust_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset onetrust_data The duckdb destination used duckdb:/onetrust.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 /v1/oauth/token and GET /api/discovery-scan-config/v2/credentials from the OneTrust 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 onetrust_source(client_id=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://{hostname}/api/{microservice}/{version}", "auth": {"type": "bearer", "token": client_id}, }, "resources": [ {"name": "data_subjects", "endpoint": {"path": "api/datasubject/v4/subjects", "data_selector": "content"}}, {"name": "receipt_details", "endpoint": {"path": "api/consent/v1/receipts/list", "data_selector": "content"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="onetrust_pipeline", destination="duckdb", dataset_name="onetrust_data", ) load_info = pipeline.run(onetrust_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("onetrust_pipeline").dataset() sessions_df = data.data_subjects.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM onetrust_data.data_subjects LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("onetrust_pipeline").dataset() data.data_subjects.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 OneTrust 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 OneTrust?

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