Gist Python API Docs | dltHub
Build a Gist-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Gist is a service for sharing code snippets and notes via GitHub gists; the Gist REST API allows listing, retrieving, creating, updating, forking, starring, and commenting on gists. The REST API base URL is https://api.github.com and All requests that read private or act on behalf of a user require a Bearer token (Personal Access Token or OAuth) with the gist scope; public gists are readable anonymously..
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 Gist data in under 10 minutes.
What data can I load from Gist?
Here are some of the endpoints you can load from Gist:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| gists | gists | GET | List gists for the authenticated user (top‑level array) | |
| public_gists | gists/public | GET | List public gists (top‑level array) | |
| starred_gists | gists/starred | GET | List gists starred by the authenticated user (top‑level array) | |
| gist | gists/{gist_id} | GET | Get a single gist by id (object) | |
| user_gists | users/{username}/gists | GET | List gists for a specific user (top‑level array) | |
| gist_comments | gists/{gist_id}/comments | GET | List comments on a gist (top‑level array) | |
| gist_commits | gists/{gist_id}/commits | GET | List commits for a gist (top‑level array) | |
| gist_forks | gists/{gist_id}/forks | GET | List forks for a gist (top‑level array) | |
| star_check | gists/{gist_id}/star | GET | Check if the authenticated user starred a gist (204 if starred, 404 if not) |
How do I authenticate with the Gist API?
Use an OAuth token or Personal Access Token in the Authorization header: Authorization: Bearer . Recommended headers: Accept: application/vnd.github+json and X-GitHub-Api-Version: 2022-11-28.
1. Get your credentials
- Sign into github.com.
- Go to Settings → Developer settings → Personal access tokens (or Fine-grained tokens).
- Click “Generate new token” (classic) or “Generate new fine‑grained token”.
- Name the token, set an expiration, and select the "Gist" scope (write for create/update/delete, read not required for public reads).
- Create the token and copy it (it cannot be viewed again).
2. Add them to .dlt/secrets.toml
[sources.gist_marketing_source] 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:
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 Gist 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 gist_marketing_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline gist_marketing_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset gist_marketing_data The duckdb destination used duckdb:/gist_marketing.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline gist_marketing_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 gists and public_gists from the Gist 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 gist_marketing_source(token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.github.com", "auth": { "type": "bearer", "token": token, }, }, "resources": [ {"name": "gists", "endpoint": {"path": "gists"}}, {"name": "public_gists", "endpoint": {"path": "gists/public"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="gist_marketing_pipeline", destination="duckdb", dataset_name="gist_marketing_data", ) load_info = pipeline.run(gist_marketing_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("gist_marketing_pipeline").dataset() sessions_df = data.gists.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM gist_marketing_data.gists LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("gist_marketing_pipeline").dataset() data.gists.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 Gist 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 failures
401 Unauthorized: missing/invalid Authorization header or token. Ensure Authorization: Bearer <TOKEN> is set and the token has the "Gist" scope when performing write actions.
Rate limiting
GitHub REST API uses rate limit headers: X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset. Exceeding limits returns 403 with rate limit information. Use conditional requests (If-None-Match) and respect pagination to reduce calls.
Pagination
List endpoints return paginated results. Use per_page and page query parameters and parse the Link response header for next, prev, last. Responses are top‑level arrays.
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 Gist?
Request dlt skills, commands, AGENT.md files, and AI-native context.