Sentry API Reference
Official vendor OpenAPI document · agent-readyDeveloper ToolsSource ControlDSN, bearer0 EndpointsREST
For Agents
Programmatically access API Reference resources.
Use for: I need to integrate with API Reference, Find available developer tools operations, Get the current status of API Reference resources, List all records from API Reference
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
API Reference provides programmatic access to developer tools functionality. The API exposes 0 endpoints secured with DSN, bearer authentication.
Install Jentic One Beta
Connect the API Reference to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the API Reference, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsentry.io%2Fsentry" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsentry.io%2Fsentry" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with API Reference API.
Access API Reference resources via REST API
Manage developer tools data programmatically
Integrate API Reference into automated workflows
Query and filter API Reference records by parameters
Monitor API Reference operational status and events
Use Cases
Patterns agents use API Reference API for, with concrete tasks.
★ Developer Tools Operations
The API provides 0 endpoints for developer tools operations.
Execute a primary operation against the API Reference
Data Retrieval and Monitoring
Query API Reference resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.
Poll the primary API Reference endpoint, compare response to last known state, and alert if changed
AI Agent Integration via Jentic
AI agents discover and call API Reference endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle DSN, bearer tokens manually.
Search Jentic for 'API reference', load the operation schema, and execute with Jentic-managed credentials
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Sentry by hand means choosing the right us or de region host, obtaining a bearer auth token or DSN, and attaching it to every organization and project call yourself. Through Jentic you install once, import Sentry from the API Directory, store the token once, and your agent calls it.
Permission scoping
Sentry puts the organization and project slugs in the URL path (/api/0/projects/{organization_id_or_slug}/{project_id_or_slug}/...), so a rule can pin your agent to one project: it can read that project's issues and events and nothing else. You choose the operations it may call, so it holds only the ones you grant.
Credential isolation
Your Sentry auth token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list a project's issues' or 'get an organization's releases', and Jentic returns the matching Sentry operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using API Reference API through Jentic.
What authentication does the API Reference use?
The API Reference uses DSN, bearer authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
What are the rate limits for the API Reference?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I use API reference through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'use API reference'. Jentic returns the matching API Reference operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the API Reference have?
The API Reference exposes 0 endpoints covering teams, organizations, projects operations.
Does the API Reference support pagination?
Pagination support depends on the specific endpoint. Check the endpoint parameters for page, limit, or offset fields. Through Jentic, the operation schema exposes all available parameters so agents can paginate automatically.
Can I limit what my agent is allowed to do with the Sentry API?
Yes. Because Sentry puts the organization and project slugs in the URL path (for example /api/0/projects/{organization}/{project}/...), your self-hosted Jentic One instance lets you write a rule that pins the agent to a single project, so it can read that project's issues and events and nothing else. You decide which operations the agent may call, so it holds only the ones you grant and cannot reach other projects or organizations. Since Jentic One is hosted by you, those scoping rules and the credentials they use stay under your own control.
GET STARTED