Example Python API Docs | dltHub

GitHub is a platform for hosting and collaborating on source code repositories. The REST API base URL is https://api.github.com and All requests require a token passed 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 Example data in under 10 minutes.

---

What data can I load from Example?

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

---

How do I authenticate with the Example API?

Include an Authorization header with either "token <YOUR_TOKEN>" or "Bearer <YOUR_TOKEN>" for every request.

1. Get your credentials

1. Log in to your GitHub account.
2. Click your profile avatar → Settings.
3. In the left sidebar, select Developer settings → Personal access tokens → Tokens (classic).
4. Click Generate new token, choose scopes needed for the API, and generate the token.
5. Copy the generated token; it will not be shown again.

2. Add them to .dlt/secrets.toml

Copy
[sources.example_source_source]
api_token = "your_github_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:

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 Example 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 example_source_pipeline.py

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

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

Inspect your pipeline and data:

Copy
dlt pipeline example_source_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 repos and issues from the Example 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 example_source_source(api_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.github.com",
            "auth": {
                "type": "bearer",
                "token": api_token,
            },
        },
        "resources": [
            {"name": "repos", "endpoint": {"path": "users/{username}/repos"}},
            {"name": "issues", "endpoint": {"path": "issues"}}
        ],
    }
    yield from rest_api_resources(config)


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

SQL (DuckDB example):

Copy
SELECT * FROM example_source_data.repos LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("example_source_pipeline").dataset()
data.repos.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 Example 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 errors

• 401 Unauthorized – Returned when the token is missing, malformed, or invalid. Ensure the Authorization: token <YOUR_TOKEN> header is present and the token has required scopes.

Rate limiting

• GitHub enforces rate limits per hour. Responses contain X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset headers.
• When the limit is exceeded, the API returns 403 Forbidden with a message indicating rate limit exhaustion.

Pagination

• List endpoints use per_page (max 100) and page query parameters.
• The Link response header provides URLs for next, prev, first, and last pages. Follow the next link until it is absent to retrieve all records.

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