Sentry

Retrieves detailed information for a Sentry project, given its existing organization and project ID or slug.

Tool to add a custom symbol source to a Sentry project. Use when configuring symbol sources for crash symbolication.

Invites a new member (or re-invites an existing non-accepted member) to a Sentry organization via email, allowing specification of organization and team roles.

Adds or removes a secondary email for an existing Sentry user, determined by whether the email already exists for that user.

Adds an existing member of an organization to one of its teams; the member must already belong to the organization, and the team must also belong to that organization.

Grants a Sentry team access to a Sentry project within the specified Sentry organization.

Bulk mutate various attributes on issues within an organization. Use when you need to update status, priority, assignment, or other attributes for multiple issues at once. Maximum of 1000 issues can be mutated, with a 100 issue limit per request.

Permanently removes issues from an organization. If IDs are provided, queries and filtering are ignored. Maximum of 1000 issues can be removed at once.

Creates a workflow alert for a Sentry organization using the New Monitors and Alerts system. Use when you need to set up automated alerting for issues based on trigger conditions and filters. Note: This endpoint is currently in beta and may change.

Creates a Sentry dashboard with widgets for an organization; `organization_id_or_slug` and specified `project` IDs must be valid, and `start`/`end` datetimes (if absolute range) must form a logical ISO 8601 range.

Links a Sentry user to an external identity provider's user within a Sentry organization; the Sentry user must be an organization member, an active integration for the provider must be configured, and `external_id` is typically required for the external user.

Creates a Sentry metric alert rule for an organization, mandating a 'critical' trigger, typically for a single project, where actions may require Sentry integrations.

Creates a new monitor (type 'cron_job') within a Sentry organization to track scheduled tasks, allowing configuration of its name, slug (which must be unique if provided), status, owner, and muting preferences for incidents.

Creates a new team in a Sentry organization, requiring either a 'slug' or 'name' to define the team.

Creates a new client key (DSN) for an existing Sentry project, with optional custom rate limit configuration.

Creates a Sentry project alert rule by defining conditions, actions, and optional filters using specific JSON structures (detailed in parameter descriptions) to automate responses to event patterns for an existing organization and project.

Registers a new webhook subscription for a Sentry project to send HTTP POST notifications to a specified URL for given events, provided the project has the 'servicehooks' feature enabled.

Creates a new deploy record in Sentry to track the introduction of a release version into a specific environment.

Creates a new Sentry release for an existing organization, associating it with specified projects that must belong to that organization.

Creates a new Sentry team (SCIM group) within an organization via the SCIM API. Requirements: - Organization must have SCIM enabled (requires Business Plan with SAML2) - Must use a SCIM bearer token (generated when SCIM is enabled) - Token must have 'team:admin' or 'team:write' scope Behavior: - A URL-friendly slug is auto-generated from displayName (e.g., 'My Team' → 'my-team') - Team is created with an empty member set - Members must be added separately through SCIM member operations - Returns SCIM 2.0 Group resource with unique ID Use this for SCIM provisioning workflows with identity providers like Okta or Azure AD.

Links an existing Sentry issue to an issue in an external service, or updates an existing link, requiring a configured Sentry App installation `uuid`.

Creates a new Sentry project for an existing organization and team, allowing configuration of its name, slug, platform, and default alert rules.

Creates a new Sentry organization member via a SCIM request for SAML integration; this action does not support setting secondary emails.

Deletes a custom integration (Sentry App) by its ID or slug. Use when you need to permanently remove a custom integration from your organization. Requires org:admin scope.

⚠️ This endpoint is currently in beta and may be subject to change. Deletes an alert. Use when you need to permanently remove an alert from an organization.

Bulk delete alerts for a given organization. Use when you need to delete multiple alerts at once. ⚠️ This endpoint is currently in beta and may be subject to change.

Permanently removes a specific Debug Information File (DIF), used for symbolicating crash reports, from the specified Sentry project and organization.

Unlinks an external issue (e.g., from Jira/GitHub), identified by `external_issue_id`, from the Sentry app installation specified by `uuid`.

Unlinks a previously established external team from a Sentry team; this action does not delete either the Sentry team or the external team.

Deletes the link between an external user (from an integration provider like GitHub, Slack, GitLab, or MS Teams) and a Sentry user within the specified organization. This removes the association but does not delete the Sentry user itself. Requires org:admin or org:write permissions.

Removes an organization member from a Sentry team, revoking their team-specific permissions, provided the member is currently part of that team.

Permanently deletes a metric alert rule from a Sentry organization. This action removes the specified metric alert rule, stopping all monitoring and notifications associated with it. The deletion is immediate and cannot be undone. Metric alert rules monitor aggregated metrics (like error rates, latency, or custom metrics) and are different from issue alert rules which trigger on individual events. **Important**: Metric alert rules require a Sentry Business or Enterprise plan. If your organization is on a different plan, this endpoint will return a 404 Not Found error. **Common Use Cases**: - Cleaning up outdated or unnecessary alert rules - Removing test alert rules after validation - Decommissioning monitoring for deprecated services **Returns**: Success message on deletion (HTTP 202), or error details if the rule doesn't exist or cannot be deleted.

Deletes a custom dashboard or tombstones (marks as deleted) a pre-built dashboard within a Sentry organization.

Permanently removes a specific saved Discover query (a configuration for exploring event data) from a Sentry organization. This action requires one of the following scopes: org:admin, org:read, or org:write. The Discover saved queries feature is only available on Business and Enterprise plans.

Permanently removes an integration installation from a Sentry organization. This action requires the numeric integration ID, which can be obtained by first calling retrieve_organization_integrations_list. Required permissions: org:admin or org:integrations scope.

Permanently deletes a specific Sentry issue, identified by its ID, from an organization; this operation is irreversible and idempotent.

Permanently removes a member from a Sentry organization, revoking their access to that organization and all its associated projects.

Deletes a Sentry cron monitor or, if `environment` is specified, only specific environments within that monitor.

Permanently and irreversibly removes a Sentry release, including all its associated files, identified by its version from the specified organization.

Tool to delete a file from an organization release. Use when you need to remove a specific file associated with a release version in an organization.

Deletes a specific Spike Protection Notification Action for a Sentry organization, where `action_id` must be a valid action associated with the `organization_id_or_slug`.

Schedules a Sentry project for asynchronous deletion within a specified organization, hiding it from most public views once the process begins.

Deletes a specific service hook from a Sentry project using its organization, project, and hook identifiers.

Permanently removes specified issues from a Sentry project; if no issue IDs are provided, it removes the oldest 1000 issues.

Permanently deletes a specific client key (DSN) for a project, preventing it from being used to send events to Sentry.

Deletes a Sentry monitor, or optionally only its specified environments, for a given project.

Permanently deletes a specific Sentry session replay (a video-like reproduction of user interactions, including console logs and network activity) from the specified project and organization.

Permanently deletes a specific issue alert rule from an existing project within an existing Sentry organization.

Revokes a team's access to a Sentry project; this operation is idempotent.

Permanently deletes a specific build artifact (e.g., source map, application bundle) associated with a project release.

Deletes a custom symbol source from a Sentry project. Use when you need to remove a symbol source that is no longer needed or needs to be reconfigured.

Schedules a Sentry team for asynchronous deletion, which releases the team's slug for reuse upon successful scheduling.

Permanently and irreversibly deletes a specific team from a Sentry organization via a SCIM v2 request, provided SCIM integration is enabled for the organization.

Permanently removes a Sentry user's email address; if multiple emails exist, Sentry's API logic (e.g., primary or previously marked) determines which is deleted.

Removes a SCIM-managed member from a Sentry organization that has SCIM enabled, permanently revoking their access.

Disables Spike Protection feature for specified projects within a Sentry organization. Use this when you need to turn off spike protection for one or more projects.

Retrieves a list of alerts (workflows) for a Sentry organization. Use to get alert configurations, statuses, and trigger details. ⚠️ Note: This endpoint is currently in beta and may be subject to change. It is supported by New Monitors and Alerts and may not be viewable in the UI today.

Fetches detailed information for a specific monitor (detector) within an organization. Use when you need to retrieve monitor configuration, status, or settings. This endpoint is currently in beta and is supported by New Monitors and Alerts.

Retrieves detailed information for a specific alert workflow. Use when you need to get alert configuration, triggers, action filters, or monitoring status. This endpoint is currently in beta and supported by New Monitors and Alerts.

Retrieves monitors (detectors) for a Sentry organization. This endpoint is currently in beta and may be subject to change. Use when you need to list or query monitors for an organization.