Notion Python API Docs | dltHub

Build a Notion-to-database pipeline in Python using dlt with automatic cursor support.

Last updated:

Notion is a collaborative workspace platform that provides a REST API for programmatic access to pages, databases, blocks, and users. The REST API base URL is https://api.notion.com and All requests require a Bearer token in the Authorization header and the Notion-Version 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 Notion data in under 10 minutes.


What data can I load from Notion?

Here are some of the endpoints you can load from Notion:

ResourceEndpointMethodData selectorDescription
pagev1/pages/{page_id}GETRetrieve a single page by its ID
databasev1/databases/{database_id}GETRetrieve a database object by its ID
blockv1/blocks/{block_id}GETRetrieve a single block by its ID
block_childrenv1/blocks/{block_id}/childrenGETresultsList child blocks of a block (paginated)
usersv1/usersGETresultsList all workspace users (paginated)

How do I authenticate with the Notion API?

Include an Authorization: Bearer <token> header, a Notion-Version header with the API version, and a Content-Type: application/json header for JSON bodies.

1. Get your credentials

  1. Log in to Notion and go to Settings & Members → Integrations.
  2. Click + New integration and fill in the name, workspace, and capabilities.
  3. After creating the integration, open its detail view and locate the Internal Integration Token field.
  4. Click Copy to copy the token; store it securely for use in API requests.

2. Add them to .dlt/secrets.toml

[sources.notion_source] api_key = "your_notion_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 Notion 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 notion_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline notion_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 page and users from the Notion 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 notion_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.notion.com", "auth": { "type": "bearer", "token": api_key, }, }, "resources": [ {"name": "page", "endpoint": {"path": "v1/pages/{page_id}"}}, {"name": "users", "endpoint": {"path": "v1/users", "data_selector": "results"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="notion_pipeline", destination="duckdb", dataset_name="notion_data", ) load_info = pipeline.run(notion_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("notion_pipeline").dataset() sessions_df = data.page.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM notion_data.page LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("notion_pipeline").dataset() data.page.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 Notion data to?

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

DestinationExample 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 – Occurs when the Authorization header is missing, malformed, or contains an invalid token. Verify that the token is correct and that the Authorization: Bearer <token> header is present.

Rate Limiting

  • 429 Too Many Requests – Notion enforces rate limits per integration. When this response is received, pause requests and retry after the Retry-After header interval.

Pagination Issues

  • Responses include results and has_more. If has_more is true, use the next_cursor value returned in the response to fetch the next page. Failing to provide start_cursor will cause the API to return the first page repeatedly.

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 Notion?

Request dlt skills, commands, AGENT.md files, and AI-native context.