Sentry is an application monitoring and error-tracking platform that helps developers identify, triage, and resolve errors and performance issues across their applications. It captures crash reports, stack traces, releases, and event data, giving engineering teams real-time visibility into the health of their software. The Sentry connector lets Nexla ingest organizations, projects, teams, issues, events, releases, and usage statistics through the Sentry REST API.
Power end-to-end data operations for your Sentry API with Nexla. Our bi-directional Sentry connector is purpose-built for Sentry, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Sentry or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Sentry workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Sentry authenticates API requests with a bearer auth token that is sent in the Authorization header using the format Bearer <token>. Before creating a Sentry credential in Nexla, generate an auth token in Sentry and note the base URL of your Sentry instance.
Sentry offers more than one type of auth token. Choose the token type that fits how you intend to read data:
User Auth Token (personal token) — bound to your Sentry user account and able to access the organizations, projects, and teams your account can reach. To create one, sign in to sentry.io, open the account dropdown in the top-left corner, and select Personal Tokens. Click Create New Token, give the token a descriptive name, select the scopes it should have, and create the token.
Organization Auth Token — bound to a single organization and scoped to all projects within it. To create one, sign in to sentry.io and navigate to Settings > Developer Settings > Organization Tokens. Click Create New Token, provide a descriptive name, and create the token. Organization auth tokens carry the sntrys_ prefix.
When creating the token, grant only the read scopes your flows require (for example, org:read, project:read, team:read, member:read, and event:read). Sentry returns a 403 Forbidden response if a token is used to call an endpoint it is not scoped for.
For security reasons, Sentry displays an auth token only once, immediately after it is created. Copy the token and store it securely, as it cannot be retrieved again later.
If you connect to a self-hosted Sentry instance rather than sentry.io, use your instance URL as the base URL. The default API path prefix is /api/0.
After selecting the data source type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Enter your Sentry auth token in the API Token field. This token authenticates Nexla with the Sentry API and is sent as a bearer token in the Authorization header on every request. Treat this value as sensitive and keep it confidential.
Enter your Sentry instance URL in the Base URL field. Use https://sentry.io for Sentry's cloud service, or your own instance URL for a self-hosted deployment.
Enter the API path prefix in the API Path field. This is optional and defaults to /api/0, which is the standard path for the Sentry API.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source creation.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Sentry connector tile, then select the credential that will be used to connect to Sentry, and click Next; or, create a new Sentry credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Sentry endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu, then supply any required parameters for that endpoint. Available endpoint templates are listed in the expandable boxes below.
[Rest API] Get Organizations
Retrieve all organizations accessible to the authenticated user.
This endpoint requires no additional parameters. It returns the organizations that the credential's auth token can access, using link header pagination to fetch all pages of results.
[Rest API] Get Organization Details
Retrieve details for a specific organization.
Organization Slug (required): The slug of the organization (e.g., my-org).
[Rest API] Get Organization Projects
Retrieve all projects for a specific organization.
Organization Slug (required): The slug of the organization (e.g., my-org).
Items Per Page (optional): Number of items to return per page (max 100). Defaults to 100.
[Rest API] Get Organization Teams
Retrieve all teams in an organization.
Organization Slug (required): The slug of the organization.
Items Per Page (optional): Number of items to return per page. Defaults to 100.
[Rest API] Get Organization Members
Retrieve all members of an organization.
Organization Slug (required): The slug of the organization.
Items Per Page (optional): Number of items to return per page (max 100). Defaults to 100.
[Rest API] Get Organization Releases
Retrieve releases for an organization.
Organization Slug (required): The slug of the organization.
Items Per Page (optional): Number of items to return per page. Defaults to 100.
[Rest API] Get Release Details
Retrieve details for a specific release.
Organization Slug (required): The slug of the organization.
Release Version (required): The version identifier of the release.
[Rest API] Get Organization Issues
Retrieve issues across all projects in an organization.
Organization Slug (required): The slug of the organization.
Query Filter (optional): Filter issues. Defaults to is:unresolved.
Stats Period (optional): Time range for statistics (e.g., 24h, 14d). Defaults to 24h.
Items Per Page (optional): Number of items to return per page. Defaults to 100.
[Rest API] Get Issue Details
Retrieve details for a specific issue.
Organization Slug (required): The slug of the organization.
Issue ID (required): The ID of the issue.
[Rest API] Get Issue Events
Retrieve events related to a specific issue.
Organization Slug (required): The slug of the organization.
Issue ID (required): The ID of the issue.
Items Per Page (optional): Number of items to return per page. Defaults to 100.
[Rest API] Get Project Details
Retrieve details for a specific project.
Organization Slug (required): The slug of the organization.
Project Slug (required): The slug of the project.
[Rest API] Get Project Issues
Retrieve issues for a specific project.
Organization Slug (required): The slug of the organization.
Project Slug (required): The slug of the project.
Query Filter (optional): Filter issues. Defaults to is:unresolved.
Stats Period (optional): Time range for statistics. Defaults to 24h.
Items Per Page (optional): Number of items to return per page. Defaults to 100.
[Rest API] Get Project Events
Retrieve error events for a specific project.
Organization Slug (required): The slug of the organization.
Project Slug (required): The slug of the project.
Items Per Page (optional): Number of items to return per page. Defaults to 100.
[Rest API] Get Event Details
Retrieve details for a specific event.
Organization Slug (required): The slug of the organization.
Project Slug (required): The slug of the project.
Event ID (required): The ID of the event.
[Rest API] Get Project Users
Retrieve users who have been affected by issues in a project.
Organization Slug (required): The slug of the organization.
Project Slug (required): The slug of the project.
Items Per Page (optional): Number of items to return per page. Defaults to 100.
[Rest API] Get Project User Feedback
Retrieve user feedback submissions for a project.
Organization Slug (required): The slug of the organization.
Project Slug (required): The slug of the project.
Items Per Page (optional): Number of items to return per page. Defaults to 100.
[Rest API] Get Project Tags
Retrieve tag keys and values for a project.
Organization Slug (required): The slug of the organization.
Project Slug (required): The slug of the project.
Items Per Page (optional): Number of items to return per page. Defaults to 100.
[Rest API] Get Project Tag Values
Retrieve values for a specific tag key.
Organization Slug (required): The slug of the organization.
Project Slug (required): The slug of the project.
Tag Key (required): The key of the tag to retrieve values for.
Items Per Page (optional): Number of items to return per page (max 100). Defaults to 100.
[Rest API] Get Project Teams
Retrieve teams associated with a project.
Organization Slug (required): The slug of the organization.
Project Slug (required): The slug of the project.
Items Per Page (optional): Number of items to return per page (max 100). Defaults to 100.
[Rest API] Get Team Details
Retrieve details for a specific team.
Organization Slug (required): The slug of the organization.
Team Slug (required): The slug of the team.
[Rest API] Get Team Members
Retrieve members of a specific team.
Organization Slug (required): The slug of the organization.
Team Slug (required): The slug of the team.
Items Per Page (optional): Number of items to return per page (max 100). Defaults to 100.
[Rest API] Get Team Projects
Retrieve projects associated with a team.
Organization Slug (required): The slug of the organization.
Team Slug (required): The slug of the team.
Items Per Page (optional): Number of items to return per page (max 100). Defaults to 100.
[Rest API] Get Team Stats
Retrieve statistics for a team.
Organization Slug (required): The slug of the organization.
Team Slug (required): The slug of the team.
Stat Type (required): The type of statistic to retrieve (received or rejected). Defaults to received.
Since (optional): Start timestamp (ISO 8601 format).
Until (optional): End timestamp (ISO 8601 format).
Resolution (optional): The resolution of the stats (10s, 1h, or 1d). Defaults to 1h.
[Rest API] Get Organization Stats
Retrieve statistical data for an organization.
Organization Slug (required): The slug of the organization.
Group By (required): Field to group statistics by (outcome, project, or category). Defaults to category. Grouping by outcome or project requires a category filter.
Field (required): Statistical field to retrieve. Defaults to sum(quantity).
Stats Period (optional): Time range for statistics. Defaults to 24h.
Category Filter (optional): Event category, required when grouping by outcome or project (error, transaction, security, session, attachment, profile, or replay). Defaults to error.
[Rest API] Get Organization Stats Summary
Retrieve summary statistics for an organization.
Organization Slug (required): The slug of the organization.
Field (required): Statistical field to retrieve. Defaults to sum(quantity).
Start Time (optional): Start timestamp (ISO 8601 format).
End Time (optional): End timestamp (ISO 8601 format).
[Rest API] Get Organization Repositories
Retrieve repositories connected to an organization.
Organization Slug (required): The slug of the organization.
Items Per Page (optional): Number of items to return per page (max 100). Defaults to 100.
[Rest API] Get Sentry App Installations
Retrieve Sentry app installations for an organization.
Organization Slug (required): The slug of the organization.
Items Per Page (optional): Number of items to return per page (max 100). Defaults to 100.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Most Sentry list endpoints use link header pagination. Nexla automatically follows the Link header to fetch subsequent pages of data. For detailed information about Sentry API endpoints, response structures, and pagination, see the Sentry API documentation.
Sentry data sources can also be manually configured to ingest data from any valid Sentry API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Sentry data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
