Load Pinterest - Ads data to DuckDB

Pinterest Ads API is a RESTful interface for managing marketing campaigns, ad groups, ads, and analytics on the Pinterest platform. Everything needed to build a working Pinterest - Ads → DuckDB pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.

---

Build your Pinterest - Ads to DuckDB pipeline

Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.

PromptCopy prompt
Run uvx dlthub-init@latest to build a pipeline from Pinterest - Ads to DuckDB and run it on dltHub

That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the Pinterest - Ads API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →

Prefer to write it yourself? Every fact the agent uses is below.

---

Pinterest - Ads API at a glance

These values come from the Pinterest - Ads API reference — the authoritative source if anything here looks out of date.

---

How do I authenticate with the Pinterest - Ads API?

All requests to the Pinterest Ads API require an 'Authorization' header with a Bearer token, formatted as 'Bearer {access_token}'.

1. Get your credentials

1. Navigate to the Pinterest Developer Portal at developers.pinterest.com and log in with your Pinterest business account. 2. Go to 'My apps' and click 'Connect app' to register a new application. 3. Once registered, you will receive your 'App ID' (client_id) and 'App secret' (client_secret). 4. In the app settings, configure your 'Redirect URIs' to match the callback URL your application uses. 5. Implement the OAuth 2.0 authorization code flow: redirect your users to the Pinterest authorization URL (https://www.pinterest.com/oauth/) with your client_id, redirect_uri, and requested scopes (e.g., 'ads:read', 'ads:write'). 6. After the user authorizes, exchange the returned authorization code for an access token and refresh token by sending a POST request to https://api.pinterest.com/v5/oauth/token with your client_id, client_secret, redirect_uri, and the code.

2. Add them to .dlt/secrets.toml

Copy
[sources.pinterest_ads_source]
access_token = "REPLACE_ME"

dlt reads this file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.

---

What Pinterest - Ads data can I load into DuckDB?

These are the Pinterest - Ads endpoints dlt can load into DuckDB:

---

How do I load only new Pinterest - Ads records?

Pinterest - Ads exposes bookmark on ad_accounts/{ad_account_id}/ads, so dlt can request only the records that changed since the last run. Set it as the cursor_path and dlt tracks the high-water mark for you between runs.

Copy
{"name": "ads", "endpoint": {
    "path": "ad_accounts/{ad_account_id}/ads",
    "data_selector": "items",
    "incremental": {"cursor_path": "bookmark", "initial_value": "2024-01-01T00:00:00Z"},
}}

On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.

---

What does the generated Pinterest - Ads pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading /ad_accounts and /ad_accounts/{ad_account_id}/ads from the Pinterest - Ads API into DuckDB:

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

@dlt.source
def pinterest_ads_source(access_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.pinterest.com/v5",
            "auth": {"type": "bearer", "token": access_token},
        },
        "resources": [
            {"name": "ads", "endpoint": {"path": "ad_accounts/{ad_account_id}/ads", "data_selector": "items"}},
            {"name": "campaigns", "endpoint": {"path": "ad_accounts/{ad_account_id}/campaigns", "data_selector": "items"}}
        ],
    }
    yield from rest_api_resources(config)


def load_pinterest_ads_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="pinterest_ads_pipeline",
        destination="duckdb",
        dataset_name="pinterest_ads_data",
    )
    load_info = pipeline.run(pinterest_ads_source())
    print(load_info)


if __name__ == "__main__":
    load_pinterest_ads_to_duckdb()

Run it with python pinterest_ads_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.

---

How do I query Pinterest - Ads data in DuckDB?

dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.

Python (pandas DataFrame):

Copy
import dlt

data = dlt.pipeline("pinterest_ads_pipeline").dataset()
df = data.ads.df()
print(df.head())

SQL:

Copy
SELECT * FROM pinterest_ads_data.ads LIMIT 10;

See querying your data with dataset and exploring it in marimo notebooks.

---

How do I deploy the Pinterest - Ads to DuckDB pipeline in production?

The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.

• Deploy & schedule — run the pipeline as a managed job with automatic retries.
• Monitor — observable job queues, alerting, and load metrics for every run.
• Transform — promote raw Pinterest - Ads loads into governed, documented models.
• Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.

Book a demo →

---

What other destinations can I load Pinterest - Ads data to?

dlt loads into any of these — only the destination argument changes:

Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.

---

Next steps

• Ready for production? Book a demo of the dltHub platform →
• dlt LLM-native workflow docs
• REST API source reference
• Join the dlt community on Slack