Public APIs Python API Docs | dltHub

Public APIs is a collective directory of free public APIs, providing searchable listings and metadata for thousands of APIs. The REST API base URL is https://api.publicapis.org and No authentication required for public endpoints (no API key)..

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 Public APIs data in under 10 minutes.

---

What data can I load from Public APIs?

Here are some of the endpoints you can load from Public APIs:

---

How do I authenticate with the Public APIs API?

The Public APIs API is public — requests require no authentication or headers. Simply perform GET requests to endpoints under the base URL.

1. Get your credentials

No credentials required — skip this step.

2. Add them to .dlt/secrets.toml

Copy
[sources.public_apis_source]
# No secrets required for Public APIs

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 Public APIs 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 public_apis_pipeline.py

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

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

Inspect your pipeline and data:

Copy
dlt pipeline public_apis_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 entries and categories from the Public APIs 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 public_apis_source(=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.publicapis.org",
            "auth": {
                "type": "none",
                "": ,
            },
        },
        "resources": [
            {"name": "entries", "endpoint": {"path": "entries", "data_selector": "entries"}},
            {"name": "categories", "endpoint": {"path": "categories"}}
        ],
    }
    yield from rest_api_resources(config)


def get_data() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="public_apis_pipeline",
        destination="duckdb",
        dataset_name="public_apis_data",
    )
    load_info = pipeline.run(public_apis_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("public_apis_pipeline").dataset()
sessions_df = data.entries.df()
print(sessions_df.head())

SQL (DuckDB example):

Copy
SELECT * FROM public_apis_data.entries LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("public_apis_pipeline").dataset()
data.entries.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 Public APIs 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

Authentication failures

This API does not require authentication. If you receive 401/403 responses they likely originate from a networking proxy, WAF, or from a different upstream service — verify your request URL and proxy credentials.

Rate limits and 429 responses

Public APIs may enforce rate limits without API keys in some environments (e.g., hosted mirrors). If you receive 429 Too Many Requests, implement exponential backoff and reduce request frequency.

Pagination and large result sets

The /entries endpoint returns a count and an entries array. Use query filters (category, title, auth, https) to narrow results. There is no standard page/limit parameters on the main public API; if responses are large, apply client-side limiting.

Unexpected response shapes

The main endpoints use either a top-level array (e.g., /categories) or an object with an "entries" key (e.g., /entries and /random). Always inspect the root JSON before mapping selectors.

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