Magnite Python API Docs | dltHub

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

Last updated:

Magnite's REST API supports JSON and is organized into three main sections. TLS 1.0 and 1.1 will be deprecated on September 23, 2025. For more details, refer to the official developer documentation. The REST API base URL is https://api.tremorhub.com/v1/resources and Cookie-based session authentication: establish a session with accessKey/secretKey at /sessions; subsequent requests must include ApiSession cookie (or sessionCode header/value)..

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


What data can I load from Magnite?

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

ResourceEndpointMethodData selectorDescription
sessions/resources/sessionsPOSTsessionCode (response object)Create session (login) — returns session entity and sets ApiSession cookie
sessions_delete/resources/sessions/{sessionCode}DELETETerminate session
query_sources/query/sourcesGET(top-level array)List available query sources for Query/Reporting
query_source_dimensions/query/sources/{sourceId}/dimensionsGET(top-level array)List dimensions for a query source
query_source_metrics/query/sources/{sourceId}/metricsGET(top-level array)List metrics for a query source
queries/queriesPOST(response object with executionCode)Start asynchronous query (returns execution id/code)
query_status/queries/{executionCode}GET(response object)Poll query status (RUNNING/COMPLETED/ERRORED)
query_results/queries/{executionCode}/results?fmt=jsonGET(top-level array)Retrieve query results in JSON (array of rows: name/value maps)
seats/seatsGET(top-level array)List seats (inventory root)
publishers/publishersGET(top-level array)List publishers under inventory
brands/brandsGET(top-level array)List brands
supply/supplyGET(top-level array)List supply entities
ad_units/adUnitsGET(top-level array)List ad units (collection responses are top-level arrays)
users/usersGET(top-level array)List users

How do I authenticate with the Magnite API?

Authenticate by POSTing JSON {"accessKey": "...","secretKey": "..."} to /resources/sessions. On success the API returns a session entity and sets an ApiSession cookie; include the ApiSession cookie or sessionCode in subsequent requests. Sessions time out and return HTTP 419 when expired.

1. Get your credentials

  1. Log in to Magnite Console (account-specific) as your Console user.
  2. Obtain your accessKey/secretKey pair bound to your Console user (Account Management / API credentials or contact your Account Manager if not visible).
  3. Use the accessKey and secretKey to POST to /resources/sessions to create a session.

2. Add them to .dlt/secrets.toml

[sources.magnite_streaming_source] access_key = "your_access_key_here" secret_key = "your_secret_key_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 Magnite 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 magnite_streaming_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline magnite_streaming_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 query_sources and queries from the Magnite 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 magnite_streaming_source(access_key, secret_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.tremorhub.com/v1/resources", "auth": { "type": "api_key", "api_session": access_key, secret_key, }, }, "resources": [ {"name": "query_sources", "endpoint": {"path": "query/sources"}}, {"name": "queries", "endpoint": {"path": "queries"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="magnite_streaming_pipeline", destination="duckdb", dataset_name="magnite_streaming_data", ) load_info = pipeline.run(magnite_streaming_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("magnite_streaming_pipeline").dataset() sessions_df = data.query_sources.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM magnite_streaming_data.query_sources LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("magnite_streaming_pipeline").dataset() data.query_sources.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 Magnite 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 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 Magnite?

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