Taboola Backstage Python API Docs | dltHub
Build a Taboola Backstage-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Taboola Backstage is a campaign management and reporting API for the Taboola advertising platform. The REST API base URL is https://backstage.taboola.com/backstage/api/1.0 and All requests require a Bearer access token (OAuth2)..
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 Taboola Backstage data in under 10 minutes.
What data can I load from Taboola Backstage?
Here are some of the endpoints you can load from Taboola Backstage:
| ## Endpoints |
|---|
| Resource |
| --- |
| campaigns |
| reports |
| items |
| advertisers |
| accounts |
How do I authenticate with the Taboola Backstage API?
Taboola Backstage uses OAuth2; include an "Authorization: Bearer [access-token]" header on every API call.
1. Get your credentials
- Sign in to Taboola Backstage.
- Navigate to the Integrations or API Access section.
- Create a new API client to obtain a client_id and client_secret.
- Use the client credentials to request an access token via the OAuth2 client‑credentials endpoint.
- Store the returned Bearer token for use in the Authorization header.
2. Add them to .dlt/secrets.toml
[sources.taboola_backstage_source] access_token = "your_bearer_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 Taboola Backstage 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 taboola_backstage_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline taboola_backstage_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset taboola_backstage_data The duckdb destination used duckdb:/taboola_backstage.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline taboola_backstage_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 campaigns and reports from the Taboola Backstage 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 taboola_backstage_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://backstage.taboola.com/backstage/api/1.0", "auth": { "type": "bearer", "access_token": access_token, }, }, "resources": [ {"name": "campaigns", "endpoint": {"path": "{account_id}/campaigns/", "data_selector": "results"}}, {"name": "reports", "endpoint": {"path": "{account_id}/reports/campaign-summary/dimensions/day", "data_selector": "results"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="taboola_backstage_pipeline", destination="duckdb", dataset_name="taboola_backstage_data", ) load_info = pipeline.run(taboola_backstage_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("taboola_backstage_pipeline").dataset() sessions_df = data.campaigns.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM taboola_backstage_data.campaigns LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("taboola_backstage_pipeline").dataset() data.campaigns.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 Taboola Backstage 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 failures
- A missing, invalid, or expired token returns 401 Unauthorized. Refresh the token using the OAuth2 client‑credentials flow and retry.
Rate limiting
- Excessive request volume may lead to 429 Too Many Requests. Implement exponential back‑off and respect any
Retry-Afterheader.
Pagination and data freshness
- List endpoints return a
resultsarray and may includerecordCountor other metadata. Uselimit/offsetquery parameters (or the report‑specific date range parameters) to page through large result sets. Report endpoints return all data for the requested date range in a singleresultsarray.
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 Taboola Backstage?
Request dlt skills, commands, AGENT.md files, and AI-native context.