Amazon Advertising Python API Docs | dltHub

Amazon Ads API is a REST API that enables advertisers and partners to programmatically manage Amazon advertising resources (campaigns, ad groups, ads, keywords) and retrieve reporting data. The REST API base URL is https://advertising-api.amazon.com and All requests require OAuth2 Bearer tokens and Amazon-Advertising-API-ClientId header..

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

---

What data can I load from Amazon Advertising?

Here are some of the endpoints you can load from Amazon Advertising:

---

How do I authenticate with the Amazon Advertising API?

Use Login with Amazon (LwA) OAuth2: include Authorization: Bearer <access_token> and Amazon-Advertising-API-ClientId: <client_id>. For profile‑specific calls also include Amazon-Advertising-API-Scope: . Access tokens expire after 60 minutes and must be refreshed.

1. Get your credentials

1. Create a Login with Amazon (LwA) application in the Amazon developer console to obtain a client_id and client_secret.
2. Apply for Amazon Ads API access and wait for approval.
3. Assign API access to your LwA application in the Amazon Ads Advanced Tools/onboarding dashboard.
4. Perform the OAuth flow: get an authorization code from the advertiser, then exchange the code (with client_id and client_secret) for an access_token and refresh_token.
5. Call GET /v2/profiles with the Authorization and ClientId headers to retrieve profileId(s) and use Amazon-Advertising-API-Scope for subsequent calls.

2. Add them to .dlt/secrets.toml

Copy
[sources.amazon_advertising_source]
client_id = "your_lwa_client_id"
client_secret = "your_lwa_client_secret"
refresh_token = "your_refresh_token"

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:

Copy
uv venv && source .venv/bin/activate
uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

Copy
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:

Copy
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 Amazon Advertising 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:

Copy
python amazon_advertising_pipeline.py

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

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

Inspect your pipeline and data:

Copy
dlt pipeline amazon_advertising_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 profiles and campaigns from the Amazon Advertising API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def amazon_advertising_source(client_id=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://advertising-api.amazon.com",
            "auth": {
                "type": "oauth2",
                "refresh_token": client_id,
            },
        },
        "resources": [
            {"name": "profiles", "endpoint": {"path": "v2/profiles"}},
            {"name": "campaigns", "endpoint": {"path": "v2/campaigns"}}
        ],
    }
    yield from rest_api_resources(config)


def get_data() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="amazon_advertising_pipeline",
        destination="duckdb",
        dataset_name="amazon_advertising_data",
    )
    load_info = pipeline.run(amazon_advertising_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):

Copy
import dlt

data = dlt.pipeline("amazon_advertising_pipeline").dataset()
sessions_df = data.profiles.df()
print(sessions_df.head())

SQL (DuckDB example):

Copy
SELECT * FROM amazon_advertising_data.profiles LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("amazon_advertising_pipeline").dataset()
data.profiles.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 Amazon Advertising data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.

---

Troubleshooting

Authorization failures

Ensure the Authorization: Bearer <access_token> header and Amazon-Advertising-API-ClientId header are present. Missing or expired tokens return 401 Unauthorized; use the refresh_token to obtain a new access_token.

Rate limits and throttling

The API enforces request limits per resource. Exceeding limits results in 429 Too Many Requests. Implement exponential backoff and respect the Retry-After header.

Deprecated endpoints

Some snapshot and suggestion endpoints are marked deprecated in the Sponsored Products documentation. Use the newer export or reporting endpoints instead.

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.

Copy
dlt ai toolkit data-exploration install
dlt ai toolkit dlthub-runtime install

• How to deploy a pipeline
• How to explore your data in marimo Notebooks
• How to query your data in Python with dataset
• Join the dlt community on Slack