Sentry Python API Docs | dltHub
Build a Sentry-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Sentry is an error‑monitoring and observability platform that exposes a REST API (v0) for managing organizations, projects, teams, issues, events and users. The REST API base URL is https://sentry.io/api/0 and All requests require a Bearer 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 Sentry data in under 10 minutes.
What data can I load from Sentry?
Here are some of the endpoints you can load from Sentry:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| organizations | /organizations/ | GET | List of organizations the token has access to. | |
| projects | /organizations/{org_slug}/projects/ | GET | List of projects in an organization. | |
| teams | /organizations/{org_slug}/teams/ | GET | List of teams within an organization. | |
| issues | /issues/ | GET | Collection of issues across projects. | |
| events | /issues/{issue_id}/events/ | GET | Events belonging to a specific issue. |
How do I authenticate with the Sentry API?
Provide a Bearer token in the Authorization header (e.g., Authorization: Bearer ) for all API calls.
1. Get your credentials
- Log in to your Sentry account at https://sentry.io.
- For a personal token: Open User Settings → Personal Tokens → Create New Token, assign the required scopes, and copy the generated token.
- For an internal integration token: Navigate to Settings → Integrations → Internal Integrations → Create New Integration, then generate a token for the integration and copy it.
- Store the token securely; it will be used as the Bearer token in API requests.
2. Add them to .dlt/secrets.toml
[sources.sentry_error_tracking_source] token = "your_sentry_bearer_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 Sentry 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 sentry_error_tracking_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline sentry_error_tracking_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset sentry_error_tracking_data The duckdb destination used duckdb:/sentry_error_tracking.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline sentry_error_tracking_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 organizations and projects from the Sentry 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 sentry_error_tracking_source(api_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://sentry.io/api/0", "auth": { "type": "bearer", "token": api_token, }, }, "resources": [ {"name": "organizations", "endpoint": {"path": "organizations/"}}, {"name": "projects", "endpoint": {"path": "organizations/{org_slug}/projects/"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="sentry_error_tracking_pipeline", destination="duckdb", dataset_name="sentry_error_tracking_data", ) load_info = pipeline.run(sentry_error_tracking_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("sentry_error_tracking_pipeline").dataset() sessions_df = data.issues.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM sentry_error_tracking_data.issues LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("sentry_error_tracking_pipeline").dataset() data.issues.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 Sentry 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 Errors
- 401 Unauthorized – Occurs when the Bearer token is missing, malformed, or lacks required scopes. Verify that the token is correct and includes the
project:readororg:readscopes as needed.
Rate Limiting
- 429 Too Many Requests – Sentry enforces rate limits per organization. The response includes a
Retry-Afterheader indicating when to retry. Implement exponential backoff and respect the header.
Pagination
- Responses are paginated using
Linkheaders (rel="next"). Continue fetching subsequent pages until thenextlink is absent. The documentation notes that each page contains up to 100 items.
Common Request Issues
- 400 Bad Request – Invalid query parameters or malformed URLs. Double‑check endpoint paths and query syntax.
- 403 Forbidden – Token does not have permission for the requested resource. Ensure the token’s scopes cover the targeted endpoint.
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 Sentry?
Request dlt skills, commands, AGENT.md files, and AI-native context.