Readme Python API Docs | dltHub

Build a Readme-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.

Last updated:

ReadMe is a documentation platform that lets developers create, host, and manage API docs and developer portals. The REST API base URL is https://{project}.readme.com/v3 and All requests require an API key sent in the Authorization 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 Readme data in under 10 minutes.


What data can I load from Readme?

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

ResourceEndpointMethodData selectorDescription
api_keys/api-keysGETRetrieve a list of API keys
guides/guidesGETRetrieve documentation guides
categories/categoriesGETList documentation categories
changelog/changelogGETRetrieve changelog entries
projects/projectsGETList projects under the account

How do I authenticate with the Readme API?

Provide your ReadMe API key in the Authorization header (e.g., Authorization: <your_api_key>) for every request.

1. Get your credentials

  1. Log in to your ReadMe account.
  2. Navigate to the Settings or Dashboard area.
  3. Select "API Keys" or "Authentication".
  4. Click "Create New API Key".
  5. Give the key a label and save.
  6. Copy the generated API key for use in your requests.

2. Add them to .dlt/secrets.toml

[sources.readme_source] api_key = "your_api_key_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 Readme 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 readme_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline readme_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 api_keys and guides from the Readme 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 readme_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://{project}.readme.com/v3", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "api_keys", "endpoint": {"path": "api-keys"}}, {"name": "guides", "endpoint": {"path": "guides"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="readme_pipeline", destination="duckdb", dataset_name="readme_data", ) load_info = pipeline.run(readme_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("readme_pipeline").dataset() sessions_df = data.api_keys.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM readme_data.api_keys LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("readme_pipeline").dataset() data.api_keys.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 Readme 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

If you receive a 401 Unauthorized response, ensure that your API key is correct and included in the Authorization header.

Pagination limits

ReadMe limits the number of records returned per request. Use the page and limit query parameters as described in the "Limiting API results" section to paginate through large result sets.

Rate limiting

When the API returns a 429 Too Many Requests status, pause your requests and retry after the time indicated in the Retry-After header.

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

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