- Category: developer tools
- Auth: OAUTH2
- Composio-managed OAuth available? Yes
- Tools: 211
- Triggers: 0
- Slug:
SENTRY - Version: 20261101_00
Tools
Access project information
Access project information
Add a symbol source to a project
Add a symbol source to a project
SENTRY_ADD_A_SYMBOL_SOURCE_TO_A_PROJECTTool to add a custom symbol source to a Sentry project. Use when configuring symbol sources for crash symbolication.Input Parameters
Output
Add organization member via email
Add organization member via email
SENTRY_ADD_ORGANIZATION_MEMBER_VIA_EMAILInvites a new member (or re-invites an existing non-accepted member) to a Sentry organization via email, allowing specification of organization and team roles.Input Parameters
billing: Manages payment/compliance. member: Views events/data. manager: Manages teams, projects, membership. owner: Unrestricted access. admin: Edits global integrations, manages projects/teams. Note: The admin role may have plan-specific restrictions; consider manager or teamRoles.contributor (views/acts on issues, may add members per org settings) and admin (full team/project management).True, an invitation email is sent to the user. Set to False to add the member without an email notification.Output
Add or remove user email by id
Add or remove user email by id
SENTRY_ADD_REMOVE_USER_EMAIL_BY_IDAdds or removes a secondary email for an existing Sentry user, determined by whether the email already exists for that user.Input Parameters
Output
Add team member in organization
Add team member in organization
SENTRY_ADD_TEAM_MEMBER_IN_ORGANIZATIONAdds an existing organization member to one of its teams, or may generate an access request when permission to join is needed. An already-existing membership is reported as an error.Input Parameters
Output
Add team to project
Add team to project
SENTRY_ADD_TEAM_TO_PROJECTGrants a Sentry team access to a Sentry project within the specified Sentry organization.Input Parameters
Output
Bulk mutate an organization's issues
Bulk mutate an organization's issues
SENTRY_BULK_MUTATE_AN_ORGANIZATIONS_ISSUESBulk 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.Input Parameters
Output
Bulk remove an organization's issues
Bulk remove an organization's issues
SENTRY_BULK_REMOVE_AN_ORGANIZATIONS_ISSUESPermanently removes issues from an organization. If IDs are provided, queries and filtering are ignored. Maximum of 1000 issues can be removed at once.Input Parameters
Output
Create an alert for an organization
Create an alert for an organization
SENTRY_CREATE_AN_ALERT_FOR_AN_ORGANIZATIONCreates 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.Input Parameters
Output
Create dashboard with widgets
Create dashboard with widgets
SENTRY_CREATE_DASHBOARD_WITH_WIDGETSCreates 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.Input Parameters
Output
Create external user for organization
Create external user for organization
SENTRY_CREATE_EXTERNAL_USER_FOR_ORGANIZATIONLinks 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.Input Parameters
github, github_enterprise, slack, gitlab, msteams, custom_scm.provider.Output
Create organization alert rule
Create organization alert rule
SENTRY_CREATE_ORGANIZATION_ALERT_RULECreates a Sentry metric alert rule for an organization, mandating a ‘critical’ trigger, typically for a single project, where actions may require Sentry integrations.Input Parameters
http.status_code:400. Use an empty string for no filter.events, transactions, metrics, sessions, and generic-metrics. Defaults to events if not specified. Refer to Sentry’s [Metric Alert Rule Types] documentation for valid configurations.label (‘critical’ or ‘warning’; ‘critical’ is mandatory), alertThreshold (numeric value to trigger), and actions. Each action specifies type (e.g., ‘email’, ‘slack’, ‘msteams’, ‘pagerduty’, ‘sentry_app’, ‘sentry_notification’, ‘opsgenie’), targetType (must be lowercase, valid values: ‘user’, ‘team’, ‘specific’, ‘sentry_app’), targetIdentifier (ID/name, format varies by type e.g., email string, PagerDuty integer). Optional action fields include inputChannelId (Slack-specific), integrationId (usually required, except for ‘email’/‘sentry_app’), sentryAppId (if action type is ‘sentry_app’), and priority (e.g., PagerDuty ‘critical’, Opsgenie ‘P1’).count, count_unique, percentage, avg, apdex, failure_rate, p50, p75, p95, p99, p100, and percentile. Refer to Sentry’s [Metric Alert Rule Types] documentation for valid configurations based on dataset and query type.queryType defaults based on the specified dataset. Supported values: 0 (Error events: event.type:error), 1 (Transaction events: event.type:transaction), 2 (None: for datasets like metrics that don’t use this). See Sentry’s [Metric Alert Rule Types] for valid configurations.default (for events captured via Capture Message), error, and transaction.1 (1 minute), 5 (5 minutes), 10 (10 minutes), 15 (15 minutes), 30 (30 minutes), 60 (1 hour), 120 (2 hours), 240 (4 hours), 1440 (24 hours).0 for ‘Above’ and 1 for ‘Below’. The resolved threshold uses the opposite operator. For percentage change thresholds, 0 means ‘Higher than’ and 1 means ‘Lower than’.comparisonDelta minutes ago’). Cannot be used for Crash Free Session Rate or Crash Free User Rate alerts.alertThreshold and thresholdType. For example, if an alert triggers ‘Above’ 50, it might resolve ‘Below’ 50. If thresholdType is 0 (Above), resolveThreshold must typically be less than or equal to the critical threshold; if thresholdType is 1 (Below), it must be greater than or equal.monitorType indicates conditional monitoring. Consult Sentry documentation for specific values.Output
Create organization monitor
Create organization monitor
SENTRY_CREATE_ORGANIZATION_MONITORCreates 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.Input Parameters
^[a-z][a-z0-9_\-]*$. Changing this slug after creation requires updating any instrumented check-in calls.Output
Create organization team
Create organization team
SENTRY_CREATE_ORGANIZATION_TEAMCreates a new team in a Sentry organization, requiring either a ‘slug’ or ‘name’ to define the team.Input Parameters
slug (if slug is provided). At least one of name or slug is required to create a team.name (if name is provided). Must adhere to the pattern: ^[a-z][a-z0-9_\-]*$.Output
Create project key with optional rate limiting
Create project key with optional rate limiting
SENTRY_CREATE_PROJECT_KEY_WITH_OPTIONAL_RATE_LIMITINGCreates a new client key (DSN) for an existing Sentry project, with optional custom rate limit configuration.Input Parameters
rateLimit_window. If omitted, no custom rate limit will be applied to this key.rateLimit_count. For example, if rateLimit_count is 1000 and rateLimit_window is 3600, the key will accept up to 1000 events per hour. If omitted, no custom rate limit will be applied to this key.Output
Create project rule for alerts
Create project rule for alerts
SENTRY_CREATE_PROJECT_RULE_FOR_ALERTSCreates 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.Input Parameters
fallthroughType - Who the notification should be sent to if there are no suggested assignees. Valid values are ActiveMembers, AllMembers, and NoOne. json { “id”: “sentry.mail.actions.NotifyEmailAction”, “targetType”: “IssueOwners”, “fallthroughType”: “ActiveMembers” } Send a notification to a Member or a Team - targetType - One of Member or Team. - fallthroughType - Who the notification should be sent to if it cannot be sent to the original target. Valid values are ActiveMembers, AllMembers, and NoOne. - targetIdentifier - The ID of the Member or Team the notification should be sent to. json { “id”: “sentry.mail.actions.NotifyEmailAction”, “targetType”: “Team”, “fallthroughType”: “AllMembers”, “targetIdentifier”: 4524986223 } Send a Slack notification - workspace - The integration ID associated with the Slack workspace. - channel - The name of the channel to send the notification to (e.g., #critical, Jane Schmidt). - channel_id (optional) - The ID of the channel to send the notification to. - tags (optional) - A string of tags to show in the notification, separated by commas (e.g., “environment, user, my_tag”). - notes (optional) - Text to show alongside the notification. To @ a user, include their user id like @<USER_ID>. To include a clickable link, format the link and title like <http://example.com|Click Here>. json { “id”: “sentry.integrations.slack.notify_action.SlackNotifyServiceAction”, “workspace”: 293854098, “channel”: “#warning”, “tags”: “environment,level”, “notes”: “Please <http://example.com|click here> for triage information” } Send a Microsoft Teams notification - team - The integration ID associated with the Microsoft Teams team. - channel - The name of the channel to send the notification to. json { “id”: “sentry.integrations.msteams.notify_action.MsTeamsNotifyServiceAction”, “team”: 23465424, “channel”: “General” } Send a Discord notification - server - The integration ID associated with the Discord server. - channel_id - The ID of the channel to send the notification to. - tags (optional) - A string of tags to show in the notification, separated by commas (e.g., “environment, user, my_tag”). json { “id”: “sentry.integrations.discord.notify_action.DiscordNotifyServiceAction”, “server”: 63408298, “channel_id”: 94732897, “tags”: “browser,user” } Create a Jira Ticket - integration - The integration ID associated with Jira. - project - The ID of the Jira project. - issuetype - The ID of the type of issue that the ticket should be created as. - dynamic_form_fields (optional) - A list of any custom fields you want to include in the ticket as objects. json { “id”: “sentry.integrations.jira.notify_action.JiraCreateTicketAction”, “integration”: 321424, “project”: “349719”, “issueType”: “1” } Create a Jira Server Ticket - integration - The integration ID associated with Jira Server. - project - The ID of the Jira Server project. - issuetype - The ID of the type of issue that the ticket should be created as. - dynamic_form_fields (optional) - A list of any custom fields you want to include in the ticket as objects. json { “id”: “sentry.integrations.jira_server.notify_action.JiraServerCreateTicketAction”, “integration”: 321424, “project”: “349719”, “issueType”: “1” } Create a GitHub Issue - integration - The integration ID associated with GitHub. - repo - The name of the repository to create the issue in. - title - The title of the issue. - body (optional) - The contents of the issue. - assignee (optional) - The GitHub user to assign the issue to. - labels (optional) - A list of labels to assign to the issue. json { “id”: “sentry.integrations.github.notify_action.GitHubCreateTicketAction”, “integration”: 93749, “repo”: “default”, “title”: “My Test Issue”, “assignee”: “Baxter the Hacker”, “labels”: [“bug”, “p1”] } Create a GitHub Enterprise Issue - integration - The integration ID associated with GitHub Enterprise. - repo - The name of the repository to create the issue in. - title - The title of the issue. - body (optional) - The contents of the issue. - assignee (optional) - The GitHub user to assign the issue to. - labels (optional) - A list of labels to assign to the issue. json { “id”: “sentry.integrations.github_enterprise.notify_action.GitHubEnterpriseCreateTicketAction”, “integration”: 93749, “repo”: “default”, “title”: “My Test Issue”, “assignee”: “Baxter the Hacker”, “labels”: [“bug”, “p1”] } } Create an Azure DevOps work item - integration - The integration ID. - project - The ID of the Azure DevOps project. - work_item_type - The type of work item to create. - dynamic_form_fields (optional) - A list of any custom fields you want to include in the work item as objects. json { “id”: “sentry.integrations.vsts.notify_action.AzureDevopsCreateTicketAction”, “integration”: 294838, “project”: “0389485”, “work_item_type”: “Microsoft.VSTS.WorkItemTypes.Task” } Send a PagerDuty notification - account - The integration ID associated with the PagerDuty account. - service - The ID of the service to send the notification to. - severity - The severity of the Pagerduty alert. This is optional, the default is critical for fatal issues, error for error issues, warning for warning issues, and info for info and debug issues. json { “id”: “sentry.integrations.pagerduty.notify_action.PagerDutyNotifyServiceAction”, “account”: 92385907, “service”: 9823924, “severity”: “critical” } Send an Opsgenie notification - account - The integration ID associated with the Opsgenie account. - team - The ID of the Opsgenie team to send the notification to. - priority - The priority of the Opsgenie alert. This is optional, the default is P3. json { “id”: “sentry.integrations.opsgenie.notify_action.OpsgenieNotifyTeamAction”, “account”: 8723897589, “team”: “9438930258-fairy”, “priority”: “P1” } Send a notification to a Sentry app with a custom webhook payload - settings - A list of objects denoting the settings each action will be created with. All required fields must be included. - sentryAppInstallationUuid - The ID for the Sentry app json { “id”: “sentry.rules.actions.notify_event_sentry_app.NotifyEventSentryAppAction”, “settings”: [ {“name”: “title”, “value”: “Team Rocket”}, {“name”: “summary”, “value”: “We’re blasting off again.”} ], “sentryAppInstallationUuid”: “643522”, “hasSchemaFormConfig”: true } Send a notification (for all legacy integrations) json { “id”: “sentry.rules.actions.notify_event.NotifyEventAction” }comparison_type than value time - comparison_type - One of older or newer - value - An integer - time - The unit of time. Valid values are minute, hour, day, and week. json { “id”: “sentry.rules.filters.age_comparison.AgeComparisonFilter”, “comparison_type”: “older”, “value”: 3, “time”: “week” } The issue has happened at least value times - value - An integer json { “id”: “sentry.rules.filters.issue_occurrences.IssueOccurrencesFilter”, “value”: 120 } The issue is assigned to No One json { “id”: “sentry.rules.filters.assigned_to.AssignedToFilter”, “targetType”: “Unassigned” } The issue is assigned to targetType - targetType - One of Team or Member - targetIdentifier - The target”s ID json { “id”: “sentry.rules.filters.assigned_to.AssignedToFilter”, “targetType”: “Member”, “targetIdentifier”: 895329789 } The event is from the latest release json { “id”: “sentry.rules.filters.latest_release.LatestReleaseFilter” } The issue”s category is equal to value - value - An integer correlated with a category. Valid values are 1 (Error), 2 (Performance), 3 (Profile), 4 (Cron), and 5 (Replay). json { “id”: “sentry.rules.filters.issue_category.IssueCategoryFilter”, “value”: 2 } The event”s tags match key match value - key - The tag - match - The comparison operator. Valid values are eq (equals), ne (does not equal), sw (starts with), ew (ends with), co (contains), nc (does not contain), is (is set), and ns (is not set). - value - A string. Not required when match is is or ns. json { “id”: “sentry.rules.filters.tagged_event.TaggedEventFilter”, “key”: “level”, “match”: “eq”, “value”: “error” } The event”s level is match level - match - Valid values are eq, gte, and lte. - level - Valid values are 50 (fatal), 40 (error), 30 (warning), 20 (info), 10 (debug), 0 (sample). json { “id”: “sentry.rules.filters.level.LevelFilter”, “match”: “gte”, “level”: “50” }value times in interval - value - An integer - interval - Valid values are 1m, 5m, 15m, 1h, 1d, 1w and 30d (m for minutes, h for hours, d for days, and w for weeks). json { “id”: “sentry.rules.conditions.event_frequency.EventFrequencyCondition”, “value”: 500, “interval”: “1h” } The issue is seen by more than value users in interval - value - An integer - interval - Valid values are 1m, 5m, 15m, 1h, 1d, 1w and 30d (m for minutes, h for hours, d for days, and w for weeks). json { “id”: “sentry.rules.conditions.event_frequency.EventUniqueUserFrequencyCondition”, “value”: 1000, “interval”: “15m” } The issue affects more than value percent of sessions in interval - value - A float - interval - Valid values are 5m, 10m, 30m, and 1h (m for minutes, h for hours). json { “id”: “sentry.rules.conditions.event_frequency.EventFrequencyPercentCondition”, “value”: 50.0, “interval”: “10m” }Output
Create project webhook subscription
Create project webhook subscription
SENTRY_CREATE_PROJECT_WEBHOOK_SUBSCRIPTIONRegisters 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.Input Parameters
Output
Create release deploy for org
Create release deploy for org
SENTRY_CREATE_RELEASE_DEPLOY_FOR_ORGCreates a new deploy record in Sentry to track the introduction of a release version into a specific environment.Input Parameters
Output
Create release for organization
Create release for organization
SENTRY_CREATE_RELEASE_FOR_ORGANIZATIONCreates a new Sentry release for an existing organization, associating it with specified projects that must belong to that organization.Input Parameters
version is ‘v1.0.0’ and ref is ‘refs/tags/v1.0.0’).repository and commit (the HEAD SHA). They can optionally include previousCommit (the SHA of the HEAD of the previous release), which should be specified if this is the first time you’ve sent commit data. commit may also contain a range in the form of previousCommit..commit.id parameter (the SHA of the commit). Optionally, include repository, message, patch_set, author_name, author_email, and timestamp for richer integration and better suspect commit tracking.Output
Create scim group for organization
Create scim group for organization
SENTRY_CREATE_SCIM_GROUP_FOR_ORGANIZATIONCreates 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.Input Parameters
Output
Create sentry external issue link
Create sentry external issue link
SENTRY_CREATE_SENTRY_EXTERNAL_ISSUE_LINKLinks an existing Sentry issue to an issue in an external service, or updates an existing link, requiring a configured Sentry App installation uuid.Input Parameters
Output
Create team project for organization
Create team project for organization
SENTRY_CREATE_TEAM_PROJECT_FOR_ORGANIZATIONCreates a new Sentry project for an existing organization and team, allowing configuration of its name, slug, platform, and default alert rules.Input Parameters
^[a-z][a-z0-9_\-]*$.Output
Create user for SAML integration
Create user for SAML integration
SENTRY_CREATE_USER_FOR_SAML_INTEGRATIONCreates a new Sentry organization member via a SCIM request for SAML integration; this action does not support setting secondary emails.Input Parameters
admin role cannot be assigned in Business/Enterprise plans; use TeamRoles instead.Output
Delete a custom integration
Delete a custom integration
SENTRY_DELETE_A_CUSTOM_INTEGRATIONDeletes 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.Input Parameters
Output
Delete an alert
Delete an alert
Delete bulk alerts
Delete bulk alerts
SENTRY_DELETE_BULK_ALERTSBulk 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.Input Parameters
Output
Delete dsyms for project
Delete dsyms for project
SENTRY_DELETE_DSYMS_FOR_PROJECTPermanently removes a specific Debug Information File (DIF), used for symbolicating crash reports, from the specified Sentry project and organization.Input Parameters
Output
Delete external issue by uuid
Delete external issue by uuid
Delete an external team by id
Delete an external team by id
Delete external user from organization
Delete external user from organization
SENTRY_DELETE_EXTERNAL_USER_FROM_ORGANIZATIONDeletes 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.Input Parameters
Output
Delete member from team
Delete member from team
SENTRY_DELETE_MEMBER_FROM_TEAMRemoves an organization member from a Sentry team, revoking their team-specific permissions, provided the member is currently part of that team.Input Parameters
Output
Delete organization alert rule
Delete organization alert rule
SENTRY_DELETE_ORGANIZATION_ALERT_RULEDeletes a specified Sentry organization metric alert rule. An HTTP 202 response yields an empty result, indicating that the deletion request was accepted for processing.Input Parameters
Output
Delete organization dashboard
Delete organization dashboard
Delete organization discover query
Delete organization discover query
SENTRY_DELETE_ORGANIZATION_DISCOVER_QUERYPermanently 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.Input Parameters
Output
Delete organization integration
Delete organization integration
SENTRY_DELETE_ORGANIZATION_INTEGRATIONPermanently 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.Input Parameters
Output
Delete organization issue
Delete organization issue
Delete organization member
Delete organization member
SENTRY_DELETE_ORGANIZATION_MEMBERPermanently removes a member from a Sentry organization, revoking their access to that organization and all its associated projects.Input Parameters
Output
Delete organization monitor
Delete organization monitor
Delete organization release
Delete organization release
SENTRY_DELETE_ORGANIZATION_RELEASEPermanently and irreversibly removes a Sentry release, including all its associated files, identified by its version from the specified organization.Input Parameters
Output
Delete organization release file
Delete organization release file
Delete org notification action
Delete org notification action
Delete project by id
Delete project by id
SENTRY_DELETE_PROJECT_BY_IDSchedules a Sentry project for asynchronous deletion within a specified organization, hiding it from most public views once the process begins.Input Parameters
Output
Delete project hook
Delete project hook
SENTRY_DELETE_PROJECT_HOOKDeletes a specific service hook from a Sentry project using its organization, project, and hook identifiers.Input Parameters
Output
Delete project issues
Delete project issues
SENTRY_DELETE_PROJECT_ISSUESPermanently removes specified issues from a Sentry project; if no issue IDs are provided, it removes the oldest 1000 issues.Input Parameters
Output
Delete project key
Delete project key
Delete project monitor
Delete project monitor
SENTRY_DELETE_PROJECT_MONITORDeletes a Sentry monitor, or optionally only its specified environments, for a given project.Input Parameters
Output
Delete project replay
Delete project replay
SENTRY_DELETE_PROJECT_REPLAYPermanently 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.Input Parameters
Output
Delete project rule
Delete project rule
SENTRY_DELETE_PROJECT_RULEPermanently deletes a specific issue alert rule from an existing project within an existing Sentry organization.Input Parameters
Output
Delete project team association
Delete project team association
Delete release file by id
Delete release file by id
SENTRY_DELETE_RELEASE_FILE_BY_IDPermanently deletes a specific build artifact (e.g., source map, application bundle) associated with a project release.Input Parameters
Output
Delete a symbol source from a project
Delete a symbol source from a project
Delete team by organization and team slug
Delete team by organization and team slug
SENTRY_DELETE_TEAM_BY_ORGANIZATION_OR_TEAM_SLUGSchedules a Sentry team for asynchronous deletion, which releases the team’s slug for reuse upon successful scheduling.Input Parameters
Output
Delete a team from an organization (SCIM v2)
Delete a team from an organization (SCIM v2)
SENTRY_DELETE_TEAM_FROM_ORG_SCIM_V2Permanently and irreversibly deletes a specific team from a Sentry organization via a SCIM v2 request, provided SCIM integration is enabled for the organization.Input Parameters
Output
Delete user emails by id
Delete user emails by id
Delete user from org
Delete user from org
Disable spike protection
Disable spike protection
SENTRY_DISABLE_SPIKE_PROTECTIONDisables 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.Input Parameters
['$all'] to disable for all projects in the organization.Output
Fetch alerts
Fetch alerts
SENTRY_FETCH_ALERTSRetrieves 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.Input Parameters
name, id, dateCreated, dateUpdated, connectedDetectors, actions, priorityDetector. Prefix with - to sort in descending order (e.g., -dateCreated).[-1] to include all available projects. For example: [1234, 56789] or [-1].Output
Fetch a monitor
Fetch a monitor
Fetch an alert
Fetch an alert
Fetch an organization's monitors
Fetch an organization's monitors
SENTRY_FETCH_AN_ORGANIZATIONS_MONITORSRetrieves 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.Input Parameters
- to sort in descending order.-1 to include all available projects. Can specify multiple project IDs.Output
Fetch issue event by id
Fetch issue event by id
SENTRY_FETCH_ISSUE_EVENT_BY_IDRetrieves the ‘latest’, ‘oldest’, or ‘recommended’ event for a Sentry issue within an organization, optionally filtered by environment(s).Input Parameters
Output
Fetch organization alert rules
Fetch organization alert rules
SENTRY_FETCH_ORGANIZATION_ALERT_RULESRetrieves metric alert rules for a Sentry organization by ID or slug. A 404 with the detail “The requested resource does not exist” is returned as an empty list, which does not by itself establish that the organization has no rules.Input Parameters
Output
Fetch organization release threshold statuses
Fetch organization release threshold statuses
SENTRY_FETCH_ORGANIZATION_RELEASE_THRESHOLD_STATUSESRetrieves 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!Input Parameters
Output
Fetch organization replay count
Fetch organization replay count
SENTRY_FETCH_ORGANIZATION_REPLAY_COUNTRetrieves the total count of session replays for a specified Sentry organization, filterable by time range, environment, project, and query.Input Parameters
(transaction:foo AND release:abc) OR (transaction:[bar,baz] AND release:def). Refer to Sentry documentation for detailed query syntax.2001-12-14T12:34:56.7890Z).[-1] to include all available projects within the organization.start and end if provided. Format is a number followed by d (days), h (hours), m (minutes), s (seconds), or w (weeks). For example, 24h queries data from the last 24 hours.Output
Fetch organization replay details
Fetch organization replay details
SENTRY_FETCH_ORGANIZATION_REPLAY_DETAILSRetrieves 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.Input Parameters
start; alternative to statsPeriod.FieldEnm for valid fields.user.email:test@example.com, has:error).end; alternative to statsPeriod.1d, 2h). Use if not providing start and end.Output
Fetch organization replay selectors
Fetch organization replay selectors
SENTRY_FETCH_ORGANIZATION_REPLAY_SELECTORSRetrieves 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).Input Parameters
start; not with statsPeriod. Note: This endpoint may not support start/end parameters - prefer using statsPeriod instead.end; not with statsPeriod. Note: This endpoint may not support start/end parameters - prefer using statsPeriod instead.Output
Fetch project environment details
Fetch project environment details
Fetch project ownership details
Fetch project ownership details
SENTRY_FETCH_PROJECT_OWNERSHIP_DETAILSRetrieves the ownership configuration, like CODEOWNERS rules or Issue Owner settings, for a specified Sentry project.Input Parameters
Output
Fetch project release files
Fetch project release files
Fetch project replay clicks
Fetch project replay clicks
SENTRY_FETCH_PROJECT_REPLAY_CLICKSFetches a list of user click interactions for a specific Sentry session replay, including the clicked DOM element ID and timestamp.Input Parameters
(transaction:foo AND release:abc) OR (transaction:[bar,baz] AND release:def)).Output
Fetch replay recording segment
Fetch replay recording segment
SENTRY_FETCH_REPLAY_RECORDING_SEGMENTRetrieves a specific recording segment for a Sentry replay, requiring valid organization, project, replay, and segment identifiers.Input Parameters
Output
Fetch Tag Values for Issue
Fetch Tag Values for Issue
SENTRY_FETCH_TAG_VALUES_FOR_ISSUERetrieves 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.Input Parameters
Output
Get activation of alert rule for organization
Get activation of alert rule for organization
SENTRY_GET_ACTIVATION_OF_ALERT_RULE_FOR_ORGANIZATIONThis legacy operation retrieved activations for a specific metric alert rule in a Sentry organization, allowing users to review the rule’s activations. DEPRECATED: Activation data is unavailable through this action.Input Parameters
Output
Get alerts and monitors
Get alerts and monitors
SENTRY_GET_ALERTSTool 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.Input Parameters
Output
Get integration details by org
Get integration details by org
SENTRY_GET_INTEGRATION_DETAILS_BY_ORGRetrieves details for a specific integration, identified by integration_id, installed within an existing Sentry organization, identified by organization_id_or_slug.Input Parameters
Output
Get oldest event
Get oldest event
SENTRY_GET_OLDEST_EVENTRetrieves the oldest (first) event associated with a Sentry issue within an organization. Use this action when you need to investigate the original occurrence of an issue to understand its root cause or initial context. This is particularly useful for debugging issues from their first appearance, analyzing initial error conditions, or determining when a problem first started occurring.Input Parameters
Output
Get organization by id or slug
Get organization by id or slug
SENTRY_GET_ORGANIZATION_BY_ID_OR_SLUGRetrieves a Sentry organization by its ID or slug; use the detailed parameter to optionally exclude project and team details for a more concise response.Input Parameters
Output
Get organization details
Get organization details
SENTRY_GET_ORGANIZATION_DETAILSRetrieves Sentry organizations accessible via the current authentication, with scope varying between user (all in region) and API key (linked org only) credentials.Input Parameters
id (organization ID), slug (organization slug), status (current status like ‘active’, ‘pending_deletion’), email or member_id (member’s email or ID), platform (project platform like ‘python’), and query (substring match on organization name, slug, member details).Output
Get organization environments
Get organization environments
SENTRY_GET_ORGANIZATION_ENVIRONMENTSLists 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.Input Parameters
Output
Get organization issue details
Get organization issue details
SENTRY_GET_ORGANIZATION_ISSUE_DETAILSRetrieves 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.Input Parameters
Output
Get organization release version
Get organization release version
SENTRY_GET_ORGANIZATION_RELEASE_VERSIONRetrieves detailed information, including optional health data and statistics, for a specific release version within a Sentry organization.Input Parameters
'''(transaction:foo AND release:abc) OR (transaction:[bar,baz] AND release:def)'''Output
Get organization sessions
Get organization sessions
SENTRY_GET_ORGANIZATION_SESSIONSRetrieves 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.Input Parameters
sum(session), count_unique(user), p99(session.duration), crash_free_rate(user)). Session duration aggregations may be incomplete for data after Jan 12, 2023.(transaction:foo AND release:abc)). See Sentry docs for syntax.field parameter to order results by. Prefix with ’-’ for descending (e.g., -sum(session)).statsPeriod). Minimum ‘1h’, maximum ‘1d’. Must cleanly divide one day.start and end. Uses ‘d’ (days), ‘h’ (hours), ‘m’ (minutes), ‘s’ (seconds), or ‘w’ (weeks).Output
Get organization stats summary
Get organization stats summary
SENTRY_GET_ORGANIZATION_STATS_SUMMARYRetrieves 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.Input Parameters
start instead of statsPeriod.sum(quantity): For attachments, total size in bytes. For sessions, total events within sessions. For others, event count. sum(times_seen): Sum of unique occurrences. For sessions, count of unique sessions. For attachments, total attachments.end instead of statsPeriod.default and security are also included.1h). Default is 1h. Minimum 1h. Intervals must cleanly divide one day and cannot exceed 1d.1d, 2h). Units: m, h, d, w. Use instead of start and end. Defaults to 24h if no time range is specified.Output
Get project events
Get project events
SENTRY_GET_PROJECT_EVENTSRetrieves a list of error events for a specified project within a Sentry organization, with options for pagination and detail level.Input Parameters
True, retrieves full event details including stacktraces; otherwise, a summary is returned.Output
Get project event stats
Get project event stats
SENTRY_GET_PROJECT_EVENT_STATSRetrieves 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 trendsInput Parameters
Output
Get project hook
Get project hook
SENTRY_GET_PROJECT_HOOKRetrieves 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.Input Parameters
Output
Get project list
Get project list
SENTRY_GET_PROJECT_LISTLists 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).Input Parameters
Output
Get project monitor by id
Get project monitor by id
Get project rule details
Get project rule details
Get SCIM group by team ID
Get SCIM group by team ID
SENTRY_GET_SCIM_GROUP_BY_TEAM_IDRetrieves 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.Input Parameters
Output
Get sentry app installations for organization
Get sentry app installations for organization
Get team members by id or slug
Get team members by id or slug
SENTRY_GET_TEAM_MEMBERS_BY_ID_OR_SLUGRetrieves a page of Sentry team members with user information, organization and team roles, authentication status, and membership flags. Supports pagination with a cursor.Input Parameters
Output
Get who viewed replay by project
Get who viewed replay by project
SENTRY_GET_WHO_VIEWED_REPLAY_BY_PROJECTRetrieves users who viewed a session replay in a Sentry project and organization. An empty list can also indicate a 404 response or a successful response without a usable nested viewer list, rather than proving that nobody viewed the replay.Input Parameters
Output
Ingest event via DSN
Ingest event via DSN
SENTRY_INGEST_EVENT_VIA_DSNIngests 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.Input Parameters
Output
List an organization's client keys
List an organization's client keys
SENTRY_LIST_AN_ORGANIZATION_S_CLIENT_KEYSLists 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.Input Parameters
Output
List an organization's issues
List an organization's issues
SENTRY_LIST_AN_ORGANIZATIONS_ISSUESReturns 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]’.Input Parameters
Output
List a project's user feedback
List a project's user feedback
List organization dashboards
List organization dashboards
SENTRY_LIST_ORGANIZATION_DASHBOARDSRetrieves a list of custom dashboards for a Sentry organization, with pagination support.Input Parameters
Output
List organization members
List organization members
List organization releases
List organization releases
SENTRY_LIST_ORGANIZATION_RELEASESRetrieves a list of releases for an existing Sentry organization, optionally filtering by a query string that matches the start of the release version.Input Parameters
Output
List organization repositories
List organization repositories
SENTRY_LIST_ORGANIZATION_REPOSITORIESRetrieves a list of version control repositories for a specific Sentry organization, which must exist and is identified by its ID or slug.Input Parameters
Output
List organizations
List organizations
SENTRY_LIST_ORGANIZATIONSRetrieves a list of organizations available to the authenticated session. Use this action when you need to discover which organizations the user has access to before performing operations on a specific organization. This is essential for organization-bound operations that require an organization_id_or_slug parameter. Note that API key requests only return the associated organization.Input Parameters
Output
List User's Teams in Organization
List User's Teams in Organization
SENTRY_LIST_ORGANIZATION_USER_TEAMSRetrieves a list of all teams that the authenticated user has access to within the specified Sentry organization.Input Parameters
Output
List project users
List project users
SENTRY_LIST_PROJECT_USERSRetrieves users who have interacted with or are recognized within a specific Sentry project, optionally filtered by a query.Input Parameters
id:, email:, username:, or ip: to target specific fields. For example, email:foo@example.com or username:john.doe.Output
List SCIM v2 organization users
List SCIM v2 organization users
SENTRY_LIST_SCIM_V2_ORGANIZATION_USERSRetrieves a paginated list of SCIM (System for Cross-domain Identity Management) users for a Sentry organization, allowing for filtering, pagination, and attribute exclusion.Input Parameters
userName eq "user@example.com"). Only eq operator is supported.members is currently supported for exclusion.Output
List Seer AI models
List Seer AI models
List teams in organization
List teams in organization
Create an external team
Create an external team
SENTRY_MANAGE_TEAM_EXTERNAL_INTEGRATIONSLinks 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.Input Parameters
Output
Modify organization notification action
Modify organization notification action
SENTRY_MODIFY_ORGANIZATION_NOTIFICATION_ACTIONModifies an organization’s notification action, specifically for spike-protection triggers.Input Parameters
sentry_notification for built-in Sentry notifications. Other supported services include slack, pagerduty, and opsgenie (these require additional configuration via integration_id, target_identifier, and target_display parameters).spike-protection.service_type is slack, pagerduty, or opsgenie. Not needed for sentry_notification service type.service_type is slack or opsgenie.service_type is slack or opsgenie.Output
Modify organization settings
Modify organization settings
SENTRY_MODIFY_ORGANIZATION_SETTINGSUpdates settings for a Sentry organization, such as name, slug, member roles, privacy, and integrations; if avatarType is ‘upload’, avatar (base64 image) is required.Input Parameters
name, publicKey, description. Business/Enterprise plans. Warning: Overwrites existing configurations.Output
Modify release file attributes
Modify release file attributes
SENTRY_MODIFY_RELEASE_FILE_ATTRIBUTESUpdates attributes (e.g., name, distribution) of a specific file within an existing release, identified by organization, version, and file ID.Input Parameters
Output
Mutate an organization's alerts
Mutate an organization's alerts
SENTRY_MUTATE_AN_ORGANIZATION_S_ALERTSBulk 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.Input Parameters
Output
Mutate an organization's monitors
Mutate an organization's monitors
SENTRY_MUTATE_AN_ORGANIZATIONS_MONITORSBulk 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.Input Parameters
-1 means all available projects. For example: /?project=1234&project=56789 or /?project=-1Output
Patch SCIM group operations
Patch SCIM group operations
SENTRY_PATCH_SCIM_GROUP_OPERATIONSPerforms SCIM PATCH operations (RFC 7644) to update attributes of a SCIM-enabled Sentry team, provided SCIM integration is active for the organization.Input Parameters
Output
Deactivate an organization member
Deactivate an organization member
SENTRY_PATCH_USER_ACTIVE_STATUS_IN_ORGANIZATIONDeactivates and permanently deletes a Sentry organization member by using a SCIM PATCH operation to set their ‘active’ attribute to ‘false’.Input Parameters
Output
Enable spike protection for an organization
Enable spike protection for an organization
SENTRY_POST_SPIKE_PROTECTION_FOR_ORGANIZATIONEnables or updates Spike Protection for specified projects (or all projects using ['$all']) within an existing Sentry organization, to which the projects must belong.Input Parameters
['$all'] for all projects in the organization.Output
Query explore events in timeseries format
Query explore events in timeseries format
SENTRY_QUERY_EXPLORE_EVENTS_IN_TIMESERIES_FORMATRetrieves explore data for an organization as a timeseries for a selected dataset and aggregate axis, optionally grouped by top events.Input Parameters
2001-12-14T12:34:56.7890. This parameter is ignored if statsPeriod is provided.field list, excluding equations.(transaction:foo AND release:abc) OR (transaction:[bar,baz] AND release:def).2001-12-14T12:34:56.7890. This parameter is ignored if statsPeriod is provided.-1 means all available projects. For example, the following are valid parameters: [1234, 56789] or [-1].24h means query data starting from 24 hours ago to now.Output
Retrieve a custom integration by id or slug
Retrieve a custom integration by id or slug
SENTRY_RETRIEVE_A_CUSTOM_INTEGRATION_BY_ID_OR_SLUGRetrieves 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.Input Parameters
Output
Retrieve aggregated test result metrics
Retrieve aggregated test result metrics
SENTRY_RETRIEVE_AGGREGATED_TEST_RESULT_METRICSRetrieves 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.Input Parameters
Output
Retrieve alert rule details
Retrieve alert rule details
SENTRY_RETRIEVE_ALERT_RULE_DETAILSRetrieves 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 accessInput Parameters
Output
Retrieve a monitor
Retrieve a monitor
SENTRY_RETRIEVE_A_MONITORRetrieves detailed information for a specific monitor within an organization. Use when you need to check monitor configuration, status, schedule, environments, or alert settings.Input Parameters
Output
Retrieve commit files for release
Retrieve commit files for release
SENTRY_RETRIEVE_COMMIT_FILES_FOR_RELEASERetrieves files changed in commits for a specified Sentry release; the release must exist and have linked commits.Input Parameters
my-org-slug) or numerical ID (e.g., 1234567) of the Sentry organization to which the release belongs.Output
Retrieve an organization's repository commits
Retrieve an organization's repository commits
Retrieve custom integration issue links
Retrieve custom integration issue links
SENTRY_RETRIEVE_CUSTOM_INTEG_ISSUE_LINKS_GIVEN_SENTRY_ISSUERetrieves 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.Input Parameters
Output
Retrieve data forwarders for an organization
Retrieve data forwarders for an organization
Retrieve dsym files for project
Retrieve dsym files for project
Retrieve event id for organization
Retrieve event id for organization
SENTRY_RETRIEVE_EVENT_ID_FOR_ORGANIZATIONResolves a Sentry event ID to its project and issue details within an accessible Sentry organization.Input Parameters
Output
Retrieve files for release
Retrieve files for release
SENTRY_RETRIEVE_FILES_FOR_RELEASERetrieves a list of artifact files for a specific release version in a Sentry organization.Input Parameters
Output
Retrieve issue events by id
Retrieve issue events by id
SENTRY_RETRIEVE_ISSUE_EVENTS_BY_IDRetrieves events for a specified Sentry issue_id, which must be an existing issue.Input Parameters
2001-12-14T12:34:56.7890Z). If provided, start must also be specified. This parameter is overridden by statsPeriod if both are used.true, the full event body, including stacktraces, is included in the response for each event. If false or not provided (default), summarized event data is returned.2001-12-14T12:34:56.7890Z). If provided, end must also be specified. This parameter is overridden by statsPeriod if both are used.true, events are returned in a pseudo-random yet deterministic order. An identical query will consistently produce the same event sequence. Useful for obtaining a representative sample from a large number of events.start and end if specified. Format is a number followed by ‘d’ (days), ‘h’ (hours), ‘m’ (minutes), ‘s’ (seconds), or ‘w’ (weeks).Output
Retrieve issue hashes for organization
Retrieve issue hashes for organization
SENTRY_RETRIEVE_ISSUE_HASHES_FOR_ORGANIZATIONRetrieves a list of grouping checksums (hashes) generated by Sentry for a specific issue within an organization, used for understanding event aggregation.Input Parameters
True, includes comprehensive details for each hash; if False, returns a minimal representation.Output
Retrieve issue tag details
Retrieve issue tag details
SENTRY_RETRIEVE_ISSUE_TAG_DETAILSRetrieves 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).Input Parameters
Output
Retrieve monitor checkins
Retrieve monitor checkins
SENTRY_RETRIEVE_MONITOR_CHECKINSRetrieves the history of check-ins for a Sentry monitor, providing insights into the health and performance of associated scheduled tasks.Input Parameters
Output
Retrieve monitor checkins by org
Retrieve monitor checkins by org
Retrieve notification action by org id
Retrieve notification action by org id
SENTRY_RETRIEVE_NOTIFICATION_ACTION_BY_ORG_IDRetrieves details for a specific Spike Protection Notification Action, which defines alerts for triggered spike protection rules, within a Sentry organization.Input Parameters
Output
Retrieve organization dashboard
Retrieve organization dashboard
Retrieve organization events
Retrieve organization events
SENTRY_RETRIEVE_ORGANIZATION_EVENTSRetrieves Discover event data for a Sentry organization. When a nonempty field list and sort are supplied, the tool adds the sort field to the list if missing; equation fields cannot be used for sorting, and the field list has a 20-item limit.Input Parameters
2024-01-15T12:30:00Z). This parameter is ignored if statsPeriod is provided.- for descending order (e.g., -timestamp). Important: The sort field must be included in the field parameter list and cannot be an equation field.id, title, timestamp, project, user.email, level, transaction, platform). - A tag, using tag[tagName] format (e.g., tag[browser.name]). - A function in function_name(parameters,...) format (e.g., count(), count_unique(user), avg(transaction.duration)). When a function is included, results are grouped by any non-aggregate fields. - An equation, prefixed with equation| (e.g., equation|count_if(transaction.duration,greater,300) / count() * 100). Note: The API automatically includes id and project.name fields in responses. If a sort parameter is provided, the base sort field will be automatically added to this list if not already present.(transaction:foo AND release:abc) OR (transaction:[bar,baz] AND release:def). Refer to Sentry documentation for detailed search syntax.2024-01-01T10:00:00Z). This parameter is ignored if statsPeriod is provided.[-1] to include all accessible projects. For example: [123, 456] or [-1].24h, 7d, 30m). This overrides start and end if provided. Valid suffixes: d (days), h (hours), m (minutes), s (seconds), w (weeks).Output
Retrieve organization integrations list
Retrieve organization integrations list
SENTRY_RETRIEVE_ORGANIZATION_INTEGRATIONS_LISTRetrieves a list of available integrations for an existing Sentry organization.Input Parameters
alert-rule, chat-unfurl, codeowners, commits, data-forwarding, deployment, enterprise-alert-rule, enterprise-incident-management, incident-management, issue-basic, issue-sync, mobile, serverless, session-replay, stacktrace-link, ticket-rules.True, fetches detailed third-party configurations for each integration; this may significantly increase response time.Output
Retrieve organization member
Retrieve organization member
SENTRY_RETRIEVE_ORGANIZATION_MEMBERRetrieves 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.Input Parameters
Output
Retrieve organization monitors
Retrieve organization monitors
Retrieve organization projects
Retrieve organization projects
SENTRY_RETRIEVE_ORGANIZATION_PROJECTSRetrieves 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 ApiAction 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.Input Parameters
Output
Retrieve organization relay usage
Retrieve organization relay usage
SENTRY_RETRIEVE_ORGANIZATION_RELAY_USAGERetrieves 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 setupInput Parameters
Output
Retrieve organization release commits
Retrieve organization release commits
SENTRY_RETRIEVE_ORGANIZATION_RELEASE_COMMITSRetrieves a list of commits for a given release version in an existing Sentry organization, if the release exists.Input Parameters
Output
Retrieve organization replays
Retrieve organization replays
SENTRY_RETRIEVE_ORGANIZATION_REPLAYSFetches session replays for a Sentry organization; use statsPeriod for relative time, or start and end (used together) for absolute time ranges.Input Parameters
start. Conflicts with statsPeriod.end. Conflicts with statsPeriod.1d for one day). Units: m (minutes), h (hours), d (days), w (weeks).Output
Retrieve organization SCIM groups
Retrieve organization SCIM groups
SENTRY_RETRIEVE_ORGANIZATION_SCIM_GROUPSRetrieves 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.Input Parameters
eq (equals) operator is supported, e.g., displayName eq "Engineering Team".members.Output
Retrieve organization stats v2
Retrieve organization stats v2
SENTRY_RETRIEVE_ORGANIZATION_STATS_V2Retrieves 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.Input Parameters
start; alternative to statsPeriod.sum(quantity) for event counts (or bytes if category is attachment, milliseconds if profile_duration). sum(times_seen) for unique event occurrences (or sessions/attachments).end; alternative to statsPeriod.filters:release_version, spike_protection). Often used with outcomes like filtered or rate_limited.category either in groupBy OR as a filter parameter. Grouping by project returns a sum over the entire period, not a time series; for many projects, consider filtering by projects individually or querying them one by one to avoid missing rows.accepted, filtered, rate_limited), indicating how Sentry processed the event.["-1"] to include all accessible projects for the organization.error, transaction). IMPORTANT: Either this parameter OR category in groupBy is required for the query to succeed. attachment and profile_duration categories affect interpretation of sum(quantity) in field (bytes and milliseconds respectively).1h, 1d). Must be between 1h and 1d (inclusive) and cleanly divide 24 hours (e.g., 1h, 2h, 6h, 12h, 24h).1d for 1 day, 2w for 2 weeks). Use m (minutes), h (hours), d (days), w (weeks). Provide this or both start and end.Output
Retrieve org integration config
Retrieve org integration config
SENTRY_RETRIEVE_ORG_INTEGRATION_CONFIGRetrieves configuration for all integrations, or a specific integration if providerKey is given, for an existing Sentry organization.Input Parameters
Output
Retrieve paginated repository tokens
Retrieve paginated repository tokens
SENTRY_RETRIEVE_PAGINATED_REPOSITORY_TOKENSRetrieves a paginated list of repository tokens for a given owner. Use when you need to access repository tokens with pagination support.Input Parameters
Output
Retrieve project environments
Retrieve project environments
Retrieve project event by id
Retrieve project event by id
Retrieve project filter data
Retrieve project filter data
Retrieve project hooks
Retrieve project hooks
Retrieve project issues list
Retrieve project issues list
SENTRY_RETRIEVE_PROJECT_ISSUES_LISTRetrieves a list of issues for a Sentry project, defaulting to unresolved issues unless an empty query string is provided or specific hashes are used.Input Parameters
"" retrieves all issues regardless of status. IMPORTANT: Boolean operators “OR” and “AND” are NOT supported in Issue search - they will cause an error. To search multiple values for the same key, use list syntax: key:[value1, value2] instead of key:value1 OR key:value2. Use negation with ! prefix (e.g., !is:resolved) to exclude results.Link header to fetch the next/previous set of issues.query. Max 100 hashes processed.True, enables issue lookup by short IDs; may return issues from a different project. API default is typically False.Output
Retrieve project key details
Retrieve project key details
List a project's client keys
List a project's client keys
SENTRY_RETRIEVE_PROJECT_KEYS_BY_ORG_AND_PROJECTRetrieves a list of client keys (DSNs), used by Sentry SDKs to send events, for a specified project within an organization.Input Parameters
Output
Retrieve project members list
Retrieve project members list
SENTRY_RETRIEVE_PROJECT_MEMBERS_LISTRetrieves active organization members belonging to any team assigned to the specified Sentry project.Input Parameters
Output
Retrieve project release file details
Retrieve project release file details
SENTRY_RETRIEVE_PROJECT_RELEASE_FILE_DETAILSRetrieves metadata (default) or raw content (if download is true) for a specific file within a Sentry project’s release version.Input Parameters
Output
Retrieve project rules by org and project id
Retrieve project rules by org and project id
SENTRY_RETRIEVE_PROJECT_RULES_BY_ORG_AND_PROJECT_IDRetrieves 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.Input Parameters
Output
Retrieve project symbol sources
Retrieve project symbol sources
Retrieve project tag values
Retrieve project tag values
SENTRY_RETRIEVE_PROJECT_TAG_VALUESRetrieves values for a specified tag key recorded in a Sentry project. An empty list can also result from a 404 response or a non-list response.Input Parameters
Output
Retrieve project teams
Retrieve project teams
Retrieve release commits
Retrieve release commits
SENTRY_RETRIEVE_RELEASE_COMMITSRetrieves a list of commits associated with a specific release version within a Sentry project.Input Parameters
Output
Retrieve release deployments
Retrieve release deployments
SENTRY_RETRIEVE_RELEASE_DEPLOYMENTSRetrieves a list of all deployment records for a specific release version in an organization, detailing each deployment’s environment and timestamps.Input Parameters
Output
Retrieve release file by id
Retrieve release file by id
SENTRY_RETRIEVE_RELEASE_FILE_BY_IDRetrieves a specific file’s content or its metadata from a Sentry release, using the download parameter to choose between raw content or JSON metadata.Input Parameters
true to receive raw file content. If false or omitted, results in a JSON object with file metadata being returned.Output
Retrieve replay recording segments
Retrieve replay recording segments
SENTRY_RETRIEVE_REPLAY_RECORDING_SEGMENTSRetrieves a paginated list of recording segments for a specific Sentry replay, for reconstructing or analyzing the replay. The replay is identified within its organization and project.Input Parameters
Output
Retrieve saved discover queries
Retrieve saved discover queries
SENTRY_RETRIEVE_SAVED_DISCOVER_QUERIESRetrieves a paginated list of saved Discover query definitions for a Sentry organization, with name filtering and sorting. HTTP 404 responses are returned as an empty list without an explanatory message, so an empty result may also indicate an unavailable endpoint.Input Parameters
name (alphabetical), dateCreated (creation date), dateUpdated (last modified date), mostPopular (by usage frequency), recentlyViewed (by last view date), myqueries (queries created by the authenticated user).Output
Retrieve saved discover query for organization
Retrieve saved discover query for organization
Retrieve Seer issue fix state
Retrieve Seer issue fix state
Retrieve short id for organization
Retrieve short id for organization
Retrieve source map debug event
Retrieve source map debug event
SENTRY_RETRIEVE_SOURCE_MAP_DEBUG_EVENTRetrieves source map debug errors for a Sentry event, stack trace frame, and exception index. Responses for HTTP 400, 404, and 500 return an error detail and status rather than raising an error.Input Parameters
Output
Retrieve team info
Retrieve team info
SENTRY_RETRIEVE_TEAM_INFO_VIA_ORGANIZATION_ID_OR_SLUGRetrieves detailed information for an existing Sentry team within its organization, optionally expanding related data (e.g., projects) or collapsing sections (e.g., organization details).Input Parameters
projects (to include details of projects associated with the team) and externalTeams (to include mappings to external teams). For example, ‘projects,externalTeams’.organization (to exclude detailed organization information from the team details).Output
Retrieve team projects
Retrieve team projects
Retrieve the custom integrations created by an organization
Retrieve the custom integrations created by an organization
Retrieve user email information
Retrieve user email information
Retrieve user via SCIM API
Retrieve user via SCIM API
SENTRY_RETRIEVE_USER_VIA_SCIM_APIRetrieves 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’.Input Parameters
Output
Save organization discover query
Save organization discover query
SENTRY_SAVE_ORGANIZATION_DISCOVER_QUERYSaves 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.Input Parameters
transaction, tag[tagName]), functions (e.g., count_if(...)), or equations (prefixed with equation|) to include (max 20). See Sentry documentation for details.fields list to order results by (prefix with - for descending). Cannot be an equation.discover (event properties/tags), error-events (error data), or transaction-like (transaction/performance data).Output
Start Seer issue fix
Start Seer issue fix
SENTRY_START_SEER_ISSUE_FIXTrigger 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.Input Parameters
Output
Submit notification action API data
Submit notification action API data
SENTRY_SUBMIT_NOTIFICATION_ACTION_API_DATACreates 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’.Input Parameters
service_type is ‘slack’, ‘pagerduty’, or ‘opsgenie’.service_type is ‘slack’ or ‘opsgenie’.service_type is ‘slack’ or ‘opsgenie’.Output
Submit user feedback
Submit user feedback
SENTRY_SUBMIT_USER_FEEDBACKSubmits 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.Input Parameters
Output
Switch team role for member
Switch team role for member
SENTRY_SWITCH_TEAM_ROLE_FOR_MEMBERChanges 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.Input Parameters
contributor allows viewing/acting on events and most team project data; admin grants team administration privileges like managing projects and memberships.Output
Toggle project filter status
Toggle project filter status
SENTRY_TOGGLE_PROJECT_FILTER_STATUSUpdates 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.Input Parameters
true) or disable (false) the filter. Required if filter_id is not legacy-browsers; not used if filter_id is legacy-browsers (use subfilters then).filter_id has a specific behavior: - browser-extensions: Filters errors known to be caused by browser extensions. - localhost: Filters events originating from localhost (IPv4: 127.0.0.1, IPv6: ::1). - filtered-transaction: Filters transactions for health check and ping endpoints. - web-crawlers: Filters known web crawlers, as they may cause errors unlikely for normal users. - legacy-browsers: Filters known errors from legacy browsers (often providing less accurate context). Use subfilters to configure specific browsers for this filter.filter_id is legacy-browsers. Available options: - ie: Internet Explorer (v11 and older) - edge: Edge (v18 and older, non-Chromium) - safari: Safari (v11 and older) - firefox: Firefox (v66 and older) - chrome: Chrome (v62 and older) - opera: Opera (v50 and older) - android: Android Browser (v3 and older) - opera_mini: Opera Mini (v34 and older) Deprecated options (still functional but may be removed in the future): - ie_pre_9: Internet Explorer (v8 and older) - ie9: Internet Explorer v9 - ie10: Internet Explorer v10 - ie11: Internet Explorer v11 - safari_pre_6: Safari (v5 and older) - opera_pre_15: Opera (v14 and older) - opera_mini_pre_8: Opera Mini (v8 and older) - android_pre_4: Android Browser (v3 and older) - edge_pre_79: Edge (v18 and older, non-Chromium based)Output
Update a monitor
Update a monitor
SENTRY_UPDATE_A_MONITORUpdates a monitor’s configuration and settings. Use when you need to modify monitor name, schedule, check-in margin, max runtime, timezone, or alert thresholds.Input Parameters
Output
Update a monitor by ID
Update a monitor by ID
SENTRY_UPDATE_A_MONITOR_BY_IDUpdates 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.Input Parameters
Output
Update an alert by ID
Update an alert by ID
SENTRY_UPDATE_AN_ALERT_BY_IDUpdates a Sentry alert workflow by ID, including its name, filters, triggers, or configuration; the enabled setting defaults to true unless set otherwise or explicitly set to null. This endpoint is in beta and supported by New Monitors and Alerts.Input Parameters
Output
Update an existing custom integration
Update an existing custom integration
SENTRY_UPDATE_AN_EXISTING_CUSTOM_INTEGRATIONUpdates 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).Input Parameters
Output
Update a symbol source in a project
Update a symbol source in a project
SENTRY_UPDATE_A_PROJECTS_SYMBOL_SOURCEUpdates 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.Input Parameters
Output
Update environment visibility
Update environment visibility
Update external team integration
Update external team integration
SENTRY_UPDATE_EXTERNAL_TEAM_INTEGRATIONUpdates 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.Input Parameters
Output
Update external user for organization
Update external user for organization
SENTRY_UPDATE_EXTERNAL_USER_FOR_ORGANIZATIONUpdates attributes of an existing external user linkage (identified by external_user_id) within a Sentry organization (specified by organization_id_or_slug).Input Parameters
external_user_id path parameter.github, github_enterprise, jira_server, slack, perforce, gitlab, msteams, custom_scm.Output
Update issue attributes in organization
Update issue attributes in organization
SENTRY_UPDATE_ISSUE_ATTRIBUTES_IN_ORGANIZATIONUpdates specified attributes of an existing Sentry issue within a Sentry organization, leaving other attributes unchanged.Input Parameters
Output
Update monitor for project
Update monitor for project
SENTRY_UPDATE_MONITOR_FOR_PROJECTUpdates 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.Input Parameters
Output
Update organization alert rules
Update organization alert rules
SENTRY_UPDATE_ORGANIZATION_ALERT_RULESReplaces 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 IDsInput Parameters
team:123, user:456) owning the rule, determining management permissions.events, transactions, metrics, sessions, generic-metrics). Affects available fields/aggregations; see Sentry’s ‘Metric Alert Rule Types’ docs.critical label is mandatory. See Sentry API docs for full action schema.count, p95). See Sentry’s ‘Metric Alert Rule Types’ documentation for configurations based on dataset and query type.dataset: 0 (error events), 1 (transaction events), 2 (none). See Sentry’s ‘Metric Alert Rule Types’ for valid combinations.aggregate computation (1, 5, 10, 15, 30, 60, 120, 240, 1440).activationCondition).0 for ‘Above’ (metric > threshold) or ‘Higher than’ (percentage change), 1 for ‘Below’ (metric < threshold) or ‘Lower than’.thresholdType implies percentage change; not for ‘Crash Free…’ alerts.thresholdType is 0 (‘Above’), resolveThreshold must be < critical threshold to resolve when metric drops below this value; if 1 (‘Below’), it must be > critical threshold to resolve when metric rises above this value.Output
Update organization dashboard
Update organization dashboard
SENTRY_UPDATE_ORGANIZATION_DASHBOARDUpdates 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.Input Parameters
period is ignored. Replaces the existing end time.True for UTC, False for the user’s local time.period is ignored. Replaces the existing start time.Output
Update organization member role
Update organization member role
SENTRY_UPDATE_ORGANIZATION_MEMBER_ROLEUpdates a Sentry organization member’s organization-level role and team roles. The request sends an empty team roles list by default when team roles are omitted.Input Parameters
teamRoles for granular admin tasks.teamSlug and role). This list completely replaces existing team roles. An empty list (default) removes the member from all teams. Team roles: contributor (views/acts on issues), admin (full team/project management).Output
Update project details
Update project details
SENTRY_UPDATE_PROJECT_DETAILSUpdates 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.Input Parameters
python, javascript, java). This helps Sentry categorize and process errors.0 to disable auto-resolution.["release", "environment", "server_name"].$title, $shortID, $projectID, $orgID, and ${tag:key} (e.g., ${tag:environment}, ${tag:release}).{"user": ["id", "email"], "device": ["model"]}.Output
Update project issue status and details
Update project issue status and details
SENTRY_UPDATE_PROJECT_ISSUE_STATUS_AND_DETAILSBulk updates attributes of issues in a Sentry project, selecting issues by ID or status. If IDs are omitted when a status filter is used, the update targets all issues matching that status.Input Parameters
"resolved", "resolvedInNextRelease", "unresolved", and "ignored".user:123 or team:456) or username for assignment. Use an empty string or null to unassign.Output
Update project key configuration
Update project key configuration
SENTRY_UPDATE_PROJECT_KEY_CONFIGURATIONUpdates 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.Input Parameters
true to activate, false to deactivate). Status remains unchanged if omitted.rateLimit_window. Uses existing settings or project defaults if omitted.rateLimit_count (e.g., 3600 for 1 hour). Uses existing settings or project defaults if omitted.true) or disable (false) Debugging features for the dynamic SDK loader. Current setting remains unchanged if omitted.true) or disable (false) Session Replay for the dynamic SDK loader. Current setting remains unchanged if omitted.true) or disable (false) Performance Monitoring for the dynamic SDK loader. Current setting remains unchanged if omitted.Output
Update project ownership settings
Update project ownership settings
SENTRY_UPDATE_PROJECT_OWNERSHIP_SETTINGSUpdates a Sentry project’s ownership settings, including raw rules, fallthrough, auto-assignment and CODEOWNERS sync. CODEOWNERS sync defaults to enabled when omitted.Input Parameters
True, assigns issues to all project members if no ownership rule matches; if False, no owners are set by default in such cases.True (default), automatically synchronizes Sentry issue ownership with the repository’s CODEOWNERS file during a release.Output
Update project release file details
Update project release file details
SENTRY_UPDATE_PROJECT_RELEASE_FILE_DETAILSUpdates the name (path) or distribution identifier of a specific file within an existing project release in Sentry.Input Parameters
Output
Update Project Rule By Id
Update Project Rule By Id
SENTRY_UPDATE_PROJECT_RULE_BY_IDUpdates an existing Sentry project issue alert rule by ID. Omitted fields may be cleared or reset to defaults.Input Parameters
team:TEAM_ID or user:USER_ID or the user’s email, or a team name prefixed with ’#’. For example, ‘user@example.com’ or ‘#platform-team’.5 to 43200 (30 days).Output
Update release details for organization
Update release details for organization
SENTRY_UPDATE_RELEASE_DETAILS_FOR_ORGANIZATIONUpdates an existing Sentry release’s details for an organization, including its reference, URL, release date, associated commits, or repository references.Input Parameters
repository and commit (HEAD SHA), and can optionally include previousCommit (SHA of previous release’s HEAD) for initial data sends or corrections.Output
Update a saved query for an organization
Update a saved query for an organization
SENTRY_UPDATE_SAVED_QUERY_FOR_ORGANIZATIONUpdates an existing Discover saved query for a Sentry organization. If omitted, projects is sent as an empty list and the query dataset as error-events.Input Parameters
Output
Update team information by organization id
Update team information by organization id
SENTRY_UPDATE_TEAM_INFORMATION_BY_ORGANIZATION_IDUpdates the slug for an existing team within a Sentry organization.Input Parameters
Output
Update user email
Update user email
SENTRY_UPDATE_USER_EMAILUpdates 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 verifiedInput Parameters
Output
Update webhook configuration
Update webhook configuration
SENTRY_UPDATE_WEBHOOK_CONFIGURATION_XPUpdates 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 environmentsInput Parameters
Output
Upload dsyms file to project
Upload dsyms file to project
SENTRY_UPLOAD_DSYMS_FILE_TO_PROJECTUploads a dSYM (debug symbols) zip archive, containing an Apple .dSYM folder, to the specified Sentry project for symbolicating crash reports from Apple platforms.Input Parameters
Output
Upload file to project release
Upload file to project release
SENTRY_UPLOAD_FILE_TO_PROJECT_RELEASEUploads a file to a Sentry project release, for an existing organization, project, and version; uses multipart/form-data and the region-specific Sentry domain.Input Parameters
Output
Upload release file to organization
Upload release file to organization
SENTRY_UPLOAD_RELEASE_FILE_TO_ORGANIZATIONUploads a new file, such as a source map or debug information, to an existing release version in a Sentry organization.Input Parameters
Output
Validate credential
Validate credential
View organization notification actions
View organization notification actions
SENTRY_VIEW_ORGANIZATION_NOTIFICATION_ACTIONSRetrieves 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’.Input Parameters
[-1] for all projects. project_id_or_slug takes precedence if also provided.["$all"] for all projects. Takes precedence over project if also specified.