Outbrain Amplify Python API Docs | dltHub
Build a Outbrain Amplify-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Outbrain Amplify is a native advertising platform that provides targeted content recommendation via its API. The REST API base URL is https://api.outbrain.com/amplify/v0.1/ and All requests require an OB‑TOKEN‑V1 header containing a token obtained via Basic 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 Outbrain Amplify data in under 10 minutes.
What data can I load from Outbrain Amplify?
Here are some of the endpoints you can load from Outbrain Amplify:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| advertisers | /advertisers | GET | advertisers | List of advertiser objects |
| campaigns | /campaigns | GET | campaigns | List of campaign objects |
| publishers | /publishers | GET | publishers | List of publisher objects |
| performance | /performance | GET | performance | Performance statistics per campaign |
| reports | /reports | GET | reports | Generated reports for a given period |
How do I authenticate with the Outbrain Amplify API?
Obtain a token by calling the token endpoint with HTTP Basic Authentication (username and password encoded in the Authorization header). Include the received token in every request using the OB-TOKEN-V1 header.
1. Get your credentials
- Log in to the Outbrain dashboard.
- Navigate to the "API Credentials" or "Integrations" section.
- Locate your username and password for Amplify API access.
- Encode "username:password" in Base64.
- Send a POST request to the token endpoint (e.g., https://api.outbrain.com/amplify/v0.1/auth/token) with the header
Authorization: BASIC <base64>. - The response will contain the OB‑TOKEN‑V1 value to use in subsequent calls.
2. Add them to .dlt/secrets.toml
[sources.outbrain_amplify_source] token = "your_ob_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 Outbrain Amplify 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 outbrain_amplify_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline outbrain_amplify_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset outbrain_amplify_data The duckdb destination used duckdb:/outbrain_amplify.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline outbrain_amplify_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 advertisers and performance from the Outbrain Amplify 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 outbrain_amplify_source(token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.outbrain.com/amplify/v0.1/", "auth": { "type": "bearer", "token": token, }, }, "resources": [ {"name": "advertisers", "endpoint": {"path": "advertisers", "data_selector": "advertisers"}}, {"name": "performance", "endpoint": {"path": "performance", "data_selector": "performance"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="outbrain_amplify_pipeline", destination="duckdb", dataset_name="outbrain_amplify_data", ) load_info = pipeline.run(outbrain_amplify_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("outbrain_amplify_pipeline").dataset() sessions_df = data.advertisers.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM outbrain_amplify_data.advertisers LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("outbrain_amplify_pipeline").dataset() data.advertisers.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 Outbrain Amplify 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
- 401 Unauthorized – The
OB-TOKEN-V1header is missing, malformed, or the token has expired. Obtain a fresh token as described in the authentication section.
TLS Requirement
- The API enforces TLS 1.2. Requests made with older TLS versions will be rejected.
Rate Limiting
- If the API returns a 429 Too Many Requests response, back off for the period indicated in the
Retry-Afterheader before retrying.
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 Outbrain Amplify?
Request dlt skills, commands, AGENT.md files, and AI-native context.