Pinterest Python API Docs | dltHub
Build a Pinterest-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Pinterest is a social media platform that provides a REST API for accessing pins, boards, ads, catalogs and related resources. The REST API base URL is https://api.pinterest.com/v5 and All requests require a Bearer token for 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 Pinterest data in under 10 minutes.
What data can I load from Pinterest?
Here are some of the endpoints you can load from Pinterest:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| pins | /pins | GET | items | Retrieve a list of pins. |
| boards | /boards | GET | items | Retrieve a list of boards. |
| ad_accounts | /ad_accounts | GET | items | Retrieve advertising accounts. |
| catalogs | /catalogs | GET | items | Retrieve catalog objects. |
| user_account | /user_account | GET | Get details of the authenticated user. |
How do I authenticate with the Pinterest API?
Pinterest uses OAuth 2.0. After creating an app you receive a client_id and client_secret, exchange them for an access token via POST https://api.pinterest.com/v5/oauth/token, and include the token in the Authorization header as 'Bearer '.
1. Get your credentials
- Sign in to the Pinterest Developer Portal.
- Create a new app (or select an existing one).
- Note the displayed App ID (client_id) and App Secret (client_secret).
- In your app settings, enable the required OAuth scopes (e.g., pins:read, boards:read).
- Use the client_id and client_secret to call POST https://api.pinterest.com/v5/oauth/token with grant_type=client_credentials or authorization_code to receive an access token.
- Store the access token for use in API calls.
2. Add them to .dlt/secrets.toml
[sources.pinterest_source] client_id = "your_client_id_here" client_secret = "your_client_secret_here" access_token = "your_access_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 Pinterest 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 pinterest_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline pinterest_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset pinterest_data The duckdb destination used duckdb:/pinterest.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline pinterest_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 pins and boards from the Pinterest 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 pinterest_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.pinterest.com/v5", "auth": { "type": "bearer", "token": access_token, }, }, "resources": [ {"name": "pins", "endpoint": {"path": "pins", "data_selector": "items"}}, {"name": "boards", "endpoint": {"path": "boards", "data_selector": "items"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="pinterest_pipeline", destination="duckdb", dataset_name="pinterest_data", ) load_info = pipeline.run(pinterest_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("pinterest_pipeline").dataset() sessions_df = data.pins.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM pinterest_data.pins LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("pinterest_pipeline").dataset() data.pins.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 Pinterest 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 – Returned when the access token is missing, expired, or invalid. Ensure the
Authorization: Bearer <token>header is present and the token is current.
Rate limiting
- 429 Too Many Requests – The API enforces request limits. When received, back‑off for the number of seconds indicated in the
Retry-Afterheader before retrying.
Pagination
- Responses that return large result sets include a
cursor(ornext_cursor) field. Use the value of this field as thecursorquery parameter on the next request to retrieve the following page.
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 Pinterest?
Request dlt skills, commands, AGENT.md files, and AI-native context.