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.

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

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 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.

Links an external team or channel (e.g., Slack, GitHub) to an existing Sentry team, using a pre-configured integration for the specified provider and its valid Sentry integration ID.

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.

Deactivates and permanently deletes a Sentry organization member by using a SCIM PATCH operation to set their 'active' attribute to 'false'.

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.

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.

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

⚠️ 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.

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

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`.

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.

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`.

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.

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.

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

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.

Enables or updates Spike Protection for specified projects (or all projects using `['$all']`) within an existing Sentry organization, to which the projects must belong.

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 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.

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.

Retrieves the 'latest', 'oldest', or 'recommended' event for a Sentry issue within an organization, optionally filtered by environment(s).

Retrieves a list of active metric alert rules for an existing Sentry organization, identified by its ID or slug. Note: This endpoint returns metric alert rules only. If no metric alert rules exist for the organization, the API may return a 404 response which is handled gracefully by returning an empty list. For issue alert rules, use the project-level rules endpoint instead.

Retrieves derived health statuses for release thresholds in a Sentry organization for a given time range, optionally filtered by environment, project, or release; `start` and `end` times must be provided together. **`[WARNING]`**: This API is experimental (Alpha) and subject to change!

Retrieves the total count of session replays for a specified Sentry organization, filterable by time range, environment, project, and query.

Retrieves detailed information for a specific replay session by ID within a Sentry organization, optionally filtering time-series data using `statsPeriod` or `start`/`end`, and further refining by projects, environments, or specific fields.

Retrieves replay selectors (CSS/DOM selectors from session replays) for a Sentry organization. Selectors include elements with dead clicks or rage clicks, useful for identifying UI issues. Returns selector details with click counts and associated project IDs. Use `statsPeriod` for time filtering (preferred over start/end).

Retrieves detailed information for a specific environment within a Sentry project.

Retrieves the ownership configuration, like CODEOWNERS rules or Issue Owner settings, for a specified Sentry project.

Retrieves artifact files (e.g., source maps, debug information files) for a specific release version in a Sentry project; requires existing organization, project, and release version with associated files.

Fetches a list of user click interactions for a specific Sentry session replay, including the clicked DOM element ID and timestamp.

Retrieves a specific recording segment for a Sentry replay, requiring valid organization, project, replay, and segment identifiers.

Retrieves a list of distinct values for a specified tag key associated with an existing Sentry issue, useful for understanding tag manifestations like browser versions or affected users.

DEPRECATED: Retrieves all activations for a specific metric alert rule. ⚠️ WARNING: This endpoint has been removed from Sentry as of January 2025. The AlertRuleActivations feature was never fully released and has been completely removed from the Sentry codebase (database tables dropped in migration 0814). This action is retained for backwards compatibility but will fail with 404 errors. Sources: - https://github.com/getsentry/sentry/issues/81970 - https://github.com/getsentry/sentry/pull/83280 - https://github.com/getsentry/sentry/pull/83255

Tool to retrieve all combined alert rules and monitors for a Sentry organization. Use when you need to get a unified view of both alert rules and cron monitors. This endpoint combines results from multiple sources into a single response.

Retrieves details for a specific integration, identified by `integration_id`, installed within an existing Sentry organization, identified by `organization_id_or_slug`.

Retrieves a Sentry organization by its ID or slug; use the `detailed` parameter to optionally exclude project and team details for a more concise response.

Retrieves Sentry organizations accessible via the current authentication, with scope varying between user (all in region) and API key (linked org only) credentials.

Lists deployment environments for a Sentry organization, optionally filtered by visibility status. Environments represent deployment contexts like 'production', 'staging', or 'development' where events are tracked. By default, only visible environments are returned. Use the visibility parameter to include hidden environments or view only hidden ones.

Retrieves detailed information for a specific issue within a Sentry organization. Accepts both numeric issue IDs (e.g., '7159174717') and short IDs displayed in the Sentry UI (e.g., 'PROJECT-123', 'SENTRY-4V'). Short IDs are automatically resolved to numeric IDs before fetching issue details.

Retrieves detailed information, including optional health data and statistics, for a specific release version within a Sentry organization.

Retrieves time series data for an organization's Sentry project release health sessions; note session duration data (e.g., using `avg(session.duration)`) may be incomplete after Jan 12, 2023, results are capped at 10,000 data points, `statsPeriod` overrides `start`/`end` timestamps, and the `interval` parameter (default/min '1h', max '1d', format like `statsPeriod`) dictates time series resolution and must cleanly divide one day.

Retrieves summarized event statistics for a Sentry organization, aggregated by project, allowing queries for event counts or unique occurrences over a specified time period and resolution, with filtering by project, category, and outcome.

Retrieves time-series event statistics for a Sentry project. Returns an array of [timestamp, count] data points showing event volumes over time. Use this to analyze event trends, monitor error rates, or generate custom dashboards. The endpoint supports different event types (received, rejected, blacklisted, generated) and time resolutions (10s, 1h, 1d). **Important**: This endpoint may change in the future without notice. Monitor Sentry's API changelog for updates. **Common use cases**: - Monitor error rates over time - Analyze event rejection patterns - Generate custom analytics dashboards - Track event volume trends

Retrieves a list of error events for a specified project within a Sentry organization, with options for pagination and detail level.

Retrieves detailed information for an existing service hook within a Sentry project. Service hooks (webhooks) are HTTP callbacks that notify external systems when specific events occur in Sentry, such as when alerts are triggered ('event.alert') or new events are processed ('event.created'). This action requires: - Authentication with 'project:read' scope - The hook_id (GUID) of an existing service hook, typically obtained from creating a hook or listing project hooks Common use cases: - Verifying hook configuration and status - Retrieving the webhook URL and secret for external system setup - Checking which events the hook is subscribed to - Auditing hook creation timestamps Note: The 'servicehooks' feature must be enabled on your Sentry plan to create or manage hooks, though reading existing hook details may be possible depending on your API permissions.

Lists all Sentry projects the authenticated token has membership access to across all organizations. IMPORTANT: This endpoint returns projects where the token's user is a member. An empty result does NOT mean no projects exist - it means the token lacks project membership. This commonly happens when: - The auth token has organization-level access but not explicit project membership - Projects exist in organizations you can access, but you're not a project member If you receive an empty list but know projects exist, use SENTRY_RETRIEVE_ORGANIZATION_PROJECTS instead, which lists all projects within a specific organization (requires organization_id_or_slug parameter).

Retrieves detailed information for a specific Sentry cron monitor, provided the organization, project, and monitor exist.

Retrieves detailed information for a specific issue alert rule within a Sentry project.

Retrieves SCIM group information for a specific Sentry team. Returns the team's SCIM representation including ID, display name, and member list (limited to 10,000 members). Requires SCIM to be enabled for the organization (Business Plan with SAML2). Use this to query team details via the SCIM protocol for identity provider integrations.

Retrieves a list of Sentry App installations for a given organization, which must exist.

Retrieves all active members of a Sentry team with detailed user information, roles, and permissions. This endpoint returns members who have accepted their team invitation. Users with pending invitations are excluded from the results. Each member object includes comprehensive details such as user profile information, organization and team roles, authentication status, and membership flags.

Retrieves users who viewed a specific, existing session replay within a Sentry project and organization.

Ingests a single custom event into a Sentry project using its DSN via the Envelope ingestion endpoint. This may create or update an issue group depending on Sentry's grouping algorithm. Note: Sentry does not provide a direct API to 'create an issue group'; issues are created from ingested events. This tool allows controlled generation of events for testing or workflows requiring synthetic events.

Retrieves a list of client keys (DSNs), used by Sentry SDKs to send events, for a specified project within an organization.

Retrieves a list of legacy user feedback items within a Sentry project. Use when you need to see user-reported feedback on errors. Note: This returns legacy User Reports, not submissions from the User Feedback Widget.

Returns a list of values associated with this key for an issue. Use when you need to analyze tag values, their frequency, or timeline for specific issue tags.

Lists all client keys (DSNs) across all projects in an organization. Use when you need to audit keys organization-wide or filter keys by team or status.

Returns a list of issues (error groups) for an organization. Use when you need to retrieve and analyze error patterns, track unresolved issues, or monitor issue trends. Default query applies 'is:unresolved issue.priority:[high,medium]'.

Retrieves a list of custom dashboards for a Sentry organization, with pagination support.

Lists all members, including those with pending invitations, for a Sentry organization.

Retrieves a list of releases for an existing Sentry organization, optionally filtering by a query string that matches the start of the release version.

Retrieves a list of version control repositories for a specific Sentry organization, which must exist and is identified by its ID or slug.

Retrieves users who have interacted with or are recognized within a specific Sentry project, optionally filtered by a query.

Retrieves a paginated list of SCIM (System for Cross-domain Identity Management) users for a Sentry organization, allowing for filtering, pagination, and attribute exclusion.

Retrieves the list of AI models currently used in production in Seer. Use when you need to discover which LLM models Seer is actively using.

Lists teams for an existing Sentry organization, optionally including project details and supporting pagination via a cursor.

Retrieves a list of all teams that the authenticated user has access to within the specified Sentry organization.

Modifies an organization's notification action, specifically for `spike-protection` triggers.

Updates settings for a Sentry organization, such as name, slug, member roles, privacy, and integrations; if `avatarType` is 'upload', `avatar` (base64 image) is required.

Updates attributes (e.g., name, distribution) of a specific file within an existing release, identified by organization, version, and file ID.

Bulk enable or disable alerts for an organization. Use when you need to activate or deactivate multiple alerts at once. This endpoint is in beta and may change in the future.

Bulk enable or disable monitors for an organization. This endpoint is in beta and may change. Use when you need to enable or disable multiple monitors at once based on filters.

Performs SCIM PATCH operations (RFC 7644) to update attributes of a SCIM-enabled Sentry team, provided SCIM integration is active for the organization.

Retrieves explore data for a given organization as a timeseries. Use this to query timeseries data for 1 or many axis, with results optionally grouped by top events depending on parameters.

Retrieves detailed information about a custom integration (Sentry App) by its slug. Use this action when you need to: - Get configuration details of a custom integration including scopes, webhooks, and OAuth settings - Check the status and permissions of an integration - Retrieve integration metadata such as name, description, and avatar - Verify which events an integration subscribes to Note: Provide the integration's slug (case-sensitive), not its UUID.

Retrieves detailed information for a specific monitor within an organization. Use when you need to check monitor configuration, status, schedule, environments, or alert settings.

Retrieves aggregated test result metrics for a repository, owner, and organization. Use when you need to analyze test performance and reliability metrics for a specific repository.

Retrieves detailed information for a specific metric alert rule within a Sentry organization. Note: This endpoint is specifically for metric alert rules (organization-level alerts based on metrics like error count, latency, failure rate, etc.). For issue alert rules (project-level alerts triggered by events), use the project rules endpoint instead. The API may return 404 if: - The alert rule ID does not exist - The organization does not have metric alerts enabled - The organization does not exist or you don't have access

Retrieves a list of commits for a given repository within a Sentry organization.

Retrieves files changed in commits for a specified Sentry release; the release must exist and have linked commits.

Retrieves all external issue links for a Sentry issue. Returns connections between the Sentry issue and external tracking systems (e.g., Jira, GitHub Issues, Linear, GitLab, Asana) created through custom integrations or Sentry Apps. Use this to see what external tickets or issues are linked to a Sentry error.

Returns a list of data forwarders for an organization. Use when you need to retrieve all data forwarders configured for a specific organization.

Retrieve a list of debug information files (dSYM files) for a specified Sentry project, used for symbolication to display human-readable stack traces.

Resolves a Sentry event ID to its project and issue details within an accessible Sentry organization.

Retrieves artifact files for a specific release version in a Sentry organization; the organization and release must exist, and the response `data` field will contain the file information as a dictionary.

Retrieves events for a specified Sentry `issue_id`, which must be an existing issue.

Retrieves a list of grouping checksums (hashes) generated by Sentry for a specific issue within an organization, used for understanding event aggregation.

Retrieves detailed information (e.g., top values, counts) for a specific tag key on an existing Sentry issue; results are paginated (max 1000 values per page).

Retrieves the history of check-ins for a Sentry monitor, providing insights into the health and performance of associated scheduled tasks.

Retrieves check-ins (pings/heartbeats of a monitored cron job or task) for a specific monitor within a Sentry organization.

Retrieves details for a specific Spike Protection Notification Action, which defines alerts for triggered spike protection rules, within a Sentry organization.

Retrieves configuration for all integrations, or a specific integration if `providerKey` is given, for an existing Sentry organization.

Fetches detailed information about a specific custom dashboard within a Sentry organization.

Retrieves Discover event data for a Sentry organization; the `sort` field must be in the `field` list (not an equation), and `field` has a 20-item limit.

Retrieves a list of available integrations for an existing Sentry organization.

Retrieves details for a Sentry organization member or pending invitee, including role, teams, and status, using their member ID and the organization's ID or slug.

Retrieves cron monitors for a Sentry organization, including details of nested monitor environments.

Retrieves a list of Sentry projects for a specified organization (which must be accessible), supporting pagination via cursor. Note: The {region} placeholder in the base URL is handled by the OpenAPIAction framework, which overrides it with the base_url from auth metadata (typically 'https://sentry.io'). This ensures correct URL construction regardless of the region placeholder in the template.

Retrieves a list of trusted Sentry Relays configured for an organization. Sentry Relay is a service that proxies events between your application and Sentry. This endpoint returns the configuration of trusted relays registered for an organization. Each trusted relay entry includes details such as the relay name, public key for authentication, and a description of its purpose. Note: This feature is typically available for organizations on Business and Enterprise plans that have Relay infrastructure enabled. Organizations without any configured relays will return an empty list. Use this to: - View all trusted relays configured for your organization - Verify relay configurations and public keys - Audit relay infrastructure setup

Retrieves a list of commits for a given release version in an existing Sentry organization, if the release exists.

Fetches session replays for a Sentry organization; use `statsPeriod` for relative time, or `start` and `end` (used together) for absolute time ranges.

Retrieves a paginated list of SCIM groups (teams) for a Sentry organization; the `members` field in the response for each group will contain at most 10,000 members.

Retrieves Sentry organization event statistics; specify time range with `statsPeriod` OR both `start`/`end`; note that grouping by `project` returns a sum not a time-series, and `interval` (if used) must be 1h-1d and cleanly divide 24 hours.

Retrieves a paginated list of repository tokens for a given owner. Use when you need to access repository tokens with pagination support.

Retrieves a list of environments for an existing project within a Sentry organization.

Retrieves detailed information for a specific Sentry event using its ID, organization identifier, and project identifier.

Retrieves a Sentry project's current data filtering settings, used to ignore events from sources like localhost, web crawlers, or legacy browsers.

Return a list of service hooks (webhooks) bound to a Sentry project, used to send notifications to external services upon event occurrences.

Retrieves a list of issues for a Sentry project, defaulting to unresolved issues unless an empty `query` string is provided or specific `hashes` are used.

Retrieves details of a specific client key (DSN) for a Sentry project, which is used by Sentry SDKs to send event data.

Retrieves active organization members belonging to any team assigned to the specified Sentry project.

Retrieves metadata (default) or raw content (if `download` is true) for a specific file within a Sentry project's release version.

Retrieves a list of active issue alert rules associated with a specific project within an organization. Returns all active issue alert rules configured for the specified project, including their conditions, filters, actions, and metadata. This endpoint is useful for auditing alert configurations, managing alert rules programmatically, or understanding what alerts are active in a project.

Retrieves custom symbol sources for a Sentry project, either listing all or fetching a specific one if its ID is provided.

Retrieves up to 1000 unique values for a specified tag key that has been recorded for events within a Sentry project. Returns an empty list if the tag key doesn't exist or has no values recorded yet.

Retrieves a list of teams with explicit access to a specific project within a Sentry organization.

Retrieves a list of commits associated with a specific release version within a Sentry project.

Retrieves a list of all deployment records for a specific release version in an organization, detailing each deployment's environment and timestamps.

Retrieves a specific file's content or its metadata from a Sentry release, using the `download` parameter to choose between raw content or JSON metadata.

Retrieves a paginated list of recording segments for a specific Sentry replay, used for reconstructing or analyzing the replay.

Retrieves a paginated list of saved Discover queries for a Sentry organization. Returns saved query definitions that can be used to reproduce specific event searches and analyses. Supports filtering by name and sorting by various criteria (name, date, popularity, etc.). **Important**: This endpoint may return 404 if the Discover saved queries feature has been deprecated for the organization (organizations with 'discover-saved-queries-deprecation' feature flag). In such cases, the action gracefully returns an empty list with an explanatory message instead of failing. Organizations migrating to newer query systems may have this feature disabled.

Retrieves a specific saved Discover query (a predefined set of filters and conditions for exploring event data) for a Sentry organization.

Retrieves the current detailed state of an AI-assisted autofix process for a Sentry issue. Use when you need to check the progress, status, root cause analysis, proposed solutions, or code modifications for an autofix operation.

Resolves a Sentry short ID (e.g., 'PROJECT-1A') to its complete issue details including organization slug, project slug, group ID, and full issue metadata. Use this to look up issue information when you have a short ID reference.

Retrieves detailed debug information for diagnosing source map processing issues for a specific Sentry event, stack trace frame, and exception index. Note: The event must contain an exception with stack trace frames for this endpoint to return useful data.

Retrieves detailed information for an existing Sentry team within its organization, optionally expanding related data (e.g., projects) or collapsing sections (e.g., organization details).

Retrieves a list of Sentry projects for a specific team within an organization, supporting pagination via a cursor.

Retrieves custom integrations (Sentry Apps) created by an organization. Use when you need to list all custom integrations that the organization has developed.

Retrieves a list of email addresses for an existing Sentry user, identified by their `user_id`.

Retrieves an individual Sentry organization member's details using the SCIM v2 API. Returns a SCIM-formatted user resource containing the member's ID, username (email), email addresses, name (givenName and familyName), active status, and Sentry organization role. **Requirements**: This endpoint requires SCIM to be enabled for the organization, which requires a Business Plan subscription and SAML2 authentication enabled. A SCIM bearer token (not a regular API token) must be used for authentication. **Note**: Sentry's SCIM API does not support syncing passwords or setting user attributes other than 'active'.

Saves a new Discover query with a unique name for a Sentry organization, allowing reuse of search criteria for analyzing event data (errors, transactions) across specified projects and environments.

Trigger a Seer Issue Fix run for a specific issue. Use when you want to start an AI-assisted autofix process that operates asynchronously to identify root causes, propose solutions, generate code changes, and optionally create pull requests with fixes.

Creates a Sentry notification action for 'spike-protection' triggers, requiring `integration_id` if `service_type` is 'slack', 'pagerduty', or 'opsgenie', and `target_identifier`/`target_display` if `service_type` is 'slack' or 'opsgenie'.

Submits user feedback tied to a specific Sentry event. Use when you need to associate user-reported issues with specific error events. DEPRECATED: This endpoint is maintained for legacy SDKs; new implementations should use the User Feedback Widget. Feedback must be submitted within 30 minutes of event creation and can only be modified within 5 minutes of submission.

Changes a member's role within a Sentry team, ensuring the member is already part of the team and that any organization-level role restrictions are respected.

Updates the status or configuration of a specific inbound data filter for a Sentry project; use `active` for most filters, or `subfilters` if `filter_id` is `legacy-browsers`.

Updates a monitor's configuration and settings. Use when you need to modify monitor name, schedule, check-in margin, max runtime, timezone, or alert thresholds.

Updates an existing Sentry monitor (detector) for metric-based issue detection. Use when you need to modify monitor configuration, thresholds, data sources, or enable/disable the monitor. Note: This endpoint is in beta and may change.

Updates an existing Discover saved query for a Sentry organization.

Updates an existing custom symbol source (HTTP, GCS, or S3) in a project for fetching debug symbols. Use when you need to modify the configuration of a symbol source identified by its ID.

Tool to update an existing Sentry alert (workflow) by ID. Use when you need to modify alert settings like name, filters, triggers, or configuration. Note: This endpoint is in beta and supported by New Monitors and Alerts.

Updates an existing custom integration (Sentry App) with new configuration. Use this action to modify integration settings such as name, scopes, webhook URL, or other configuration. You must provide the integration's slug or ID and the required fields (name and scopes).

Updates the visibility of a specific environment within a Sentry project.

Updates an existing external team integration's display name, provider, Sentry integration ID, or external ID; the `integration_id` must match a valid, configured Sentry integration for the organization and the specified `provider`.

Updates attributes of an existing external user linkage (identified by `external_user_id`) within a Sentry organization (specified by `organization_id_or_slug`).

Updates specified attributes of an existing Sentry issue within a Sentry organization, leaving other attributes unchanged.

Updates a monitor for a project. Use when you need to modify monitor name, schedule, check-in margin, max runtime, timezone, status, owner, or alert thresholds for a project-level monitor.

Replaces an existing Sentry metric alert rule's configuration; fields not provided in the request are removed or reset. This action updates an existing metric alert rule. Note that this is a full replacement - any fields not provided will be removed or reset to defaults. Prerequisites: - The organization must have metric alerts feature enabled - The alert_rule_id must be a valid existing metric alert rule - Use SENTRY_FETCH_ORGANIZATION_ALERT_RULES to get existing alert rule IDs

Updates an existing custom dashboard, allowing modifications to its title, widgets, and data filters; providing `widgets`, `projects`, `environment`, `period`, `start`, `end`, or `filters` will overwrite existing settings for those fields.

Updates a Sentry organization member's organization-level role (`orgRole`) and/or their team roles (`teamRoles`), ensuring the initiator has permissions equivalent to both the member's current and intended new `orgRole` if `orgRole` is being modified.

Updates a Sentry project's settings (e.g., name, slug, platform, bookmark status); `isBookmarked` can be updated with `project:read` permission, other fields typically require `project:write` or `project:admin` permissions.

Bulk update attributes of issues in a Sentry project, targeting issues by a list of IDs or by a query status (which implies updating all matching issues if IDs are omitted).

Updates configuration settings (e.g., name, status, rate limits, SDK options) for an existing Sentry client key (DSN), identified by `key_id`, within a specified `project_id_or_slug` and `organization_id_or_slug`.

Updates the ownership configuration settings (raw rules, fallthrough, auto-assignment, CODEOWNERS sync) for a Sentry project; omitted attributes retain their current values.

Updates the name (path) or distribution identifier of a specific file within an existing project release in Sentry.

Updates an existing Sentry project issue alert rule by `rule_id`, completely overwriting it; all rule fields must be provided in the request, as omitted fields may be cleared or reset to defaults.

Updates an existing Sentry release's details for an organization, including its reference, URL, release date, associated commits, or repository references.

Updates the slug for an existing team within a Sentry organization.

Updates the primary email address for a Sentry user. The new email must already be added as a secondary email and be verified. **AUTHENTICATION REQUIREMENTS:** - Requires `user:write` scope - Typically requires a PERSONAL auth token (created from User Settings > Personal Tokens) - Internal integration tokens (organization-scoped) may not have permission for user-level operations **PREREQUISITES:** - The new email must already be added to the user's account as a secondary email - The email must be verified before it can be set as primary **COMMON ERRORS:** - 403 Forbidden: Token lacks user:write scope or is not a personal auth token - 400 Bad Request: Email is not already added to the account or is not verified

Updates an existing Sentry service hook's target URL and subscribed event types for a given project and organization. Service hooks (webhooks) are HTTP callbacks that notify external systems when specific events occur in Sentry. This action allows you to modify the webhook's URL and change which events trigger notifications. Valid event types are: - 'event.alert': Triggered when alerts fire - 'event.created': Triggered when new events are processed Requirements: - Authentication with 'project:write' scope - The 'servicehooks' feature must be enabled for your Sentry plan - The hook_id must be a valid GUID from an existing service hook Common use cases: - Updating webhook URL when your endpoint changes - Modifying event subscriptions to receive different notification types - Reconfiguring webhooks for testing or production environments

Uploads a dSYM (debug symbols) zip archive, containing an Apple .dSYM folder, to the specified Sentry project for symbolicating crash reports from Apple platforms.

Uploads a file to a Sentry project release, for an existing organization, project, and version; uses `multipart/form-data` and the region-specific Sentry domain.

Uploads a new file, such as a source map or debug information, to an existing release version in a Sentry organization.

Retrieves Spike Protection notification actions for a Sentry organization, filterable by project IDs or slugs (slugs take precedence); if `triggerType` is used, it must be 'spike-protection'.