Code42 Python API Docs | dltHub
Build a Code42-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Code42 REST API enables automated actions and system integration. Use the official Code42 Developer Portal for detailed documentation. The API supports data loss detection and response. The REST API base URL is https://api.us.code42.com and All requests require a Bearer access token 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 Code42 data in under 10 minutes.
What data can I load from Code42?
Here are some of the endpoints you can load from Code42:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| customers | v1/customer | GET | Get tenant/customer information (returns tenantId). | |
| users | v1/users | GET | users | List/search users; returns a users array. |
| sessions | v1/sessions | GET | sessions | Search sessions/alerts; returns a sessions array. |
| session_events | v1/sessions/{id}/events | GET | queryResult | Get events for a session; returns a queryResult object. |
| watchlists | v2/watchlists | GET | watchlists | List watchlists. |
| orgs | v1/orgs | GET | orgs | Get organizations list. |
| trusted_activities | v2/trusted-activities | GET | activities | List trusted activities. |
| oauth_token | v1/oauth | POST | access_token | Obtain OAuth2 token; returns access_token. |
How do I authenticate with the Code42 API?
Create an API client (client_id and client_secret) in the Code42 console, POST to /v1/oauth with those credentials to receive an access_token, then include Authorization: Bearer <token> in all subsequent requests.
1. Get your credentials
- In the Code42 admin console create an API client and grant the needed scopes (e.g., Alerts:Read, Users:Read). 2) Record the client ID and client secret. 3) Request a token by POSTing to https://api.us.code42.com/v1/oauth?grant_type=client_credentials using HTTP Basic authentication with : (or send the credentials in the form body). 4) Extract the
access_tokenfrom the JSON response and use it as a Bearer token in theAuthorizationheader for all API calls.
2. Add them to .dlt/secrets.toml
[sources.code42_source] client_id = "your_client_id_here" client_secret = "your_client_secret_here" base_url = "https://api.us.code42.com"
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 Code42 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 code42_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline code42_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset code42_data The duckdb destination used duckdb:/code42.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline code42_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 sessions and users from the Code42 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 code42_source(client_id, client_secret=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.us.code42.com", "auth": { "type": "bearer", "access_token": client_id, client_secret, }, }, "resources": [ {"name": "sessions", "endpoint": {"path": "v1/sessions", "data_selector": "sessions"}}, {"name": "users", "endpoint": {"path": "v1/users", "data_selector": "users"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="code42_pipeline", destination="duckdb", dataset_name="code42_data", ) load_info = pipeline.run(code42_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("code42_pipeline").dataset() sessions_df = data.sessions.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM code42_data.sessions LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("code42_pipeline").dataset() data.sessions.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 Code42 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 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 Code42?
Request dlt skills, commands, AGENT.md files, and AI-native context.