# Sentry on boxd

> Integrate Sentry to manage your error tracking and monitoring.

- Page: https://boxd.sh/integrations/sentry/
- CLI: `run sentry` (211 commands, 33 marked common)
- SDK: `import { sentry } from "@boxd/run"`; every parameter and response type is at `@boxd/run/sentry`
- Triggers: none
- Connect: `run auth sentry` (Sign in with Sentry), or https://app.boxd.sh/integrations/detail/sentry
- All integrations: https://boxd.sh/integrations/ (Markdown: https://boxd.sh/integrations/index.md)

## From the shell

```sh
run auth sentry      # once: prints a link to connect your account
run sentry           # list its commands
run sentry list-organizations
```

Parameters are flags (`--flag value`); object and array parameters take a JSON string. Output is YAML, or JSON with `--json`. Calls use your own connection; `--scope <name>` uses a connection shared with your team.

## From a script

```ts
import { every, sentry } from "@boxd/run";

every("1 hour", async () => {
  const result = await sentry.listOrganizations({});
  console.log(result);
});
```

Run it with `run sentry.run.ts`. Sentry has no triggers; `every()` polls on a schedule, keeps the script running as a job, and wakes the machine when it is due.

## Commands

Required flags are listed; `run sentry <command> --help` lists the optional ones. "common" marks what `run sentry` shows without `--all`.

| Command | SDK method | Required flags | Optional | Description |
|---|---|---|---|---|
| `access-project-information` ·common | `sentry.accessProjectInformation()` | `--organization-id-or-slug` `--project-id-or-slug` | 0 | Retrieves detailed information for a Sentry project, given its existing organization and project ID or slug |
| `add-organization-member-via-email` ·common | `sentry.addOrganizationMemberViaEmail()` | `--email` `--organization-id-or-slug` | 4 | 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 |
| `add-remove-user-email-by-id` | `sentry.addRemoveUserEmailById()` | `--email` `--user-id` | 0 | Adds or removes a secondary email for an existing Sentry user, determined by whether the email already exists for that user |
| `add-symbol-source-to-project` | `sentry.addSymbolSourceToProject()` | `--layout--casing` `--layout--type` `--name` `--organization-id-or-slug` `--project-id-or-slug` `--type` | 14 | Add a custom symbol source to a Sentry project |
| `add-team-member-in-organization` | `sentry.addTeamMemberInOrganization()` | `--member-id` `--organization-id-or-slug` `--team-id-or-slug` | 0 | 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 |
| `add-team-to-project` | `sentry.addTeamToProject()` | `--organization-id-or-slug` `--project-id-or-slug` `--team-id-or-slug` | 0 | Grants a Sentry team access to a Sentry project within the specified Sentry organization |
| `bulk-mutate-organizations-issues` ·common | `sentry.bulkMutateOrganizationsIssues()` | `--organization-id-or-slug` | 19 | Bulk mutate various attributes on issues within an organization |
| `bulk-remove-organizations-issues` ·common | `sentry.bulkRemoveOrganizationsIssues()` | `--organization-id-or-slug` | 7 | Permanently removes issues from an organization |
| `create-alert-for-organization` ·common | `sentry.createAlertForOrganization()` | `--actionFilters` `--config` `--name` `--organization-id-or-slug` `--triggers` | 2 | Creates a workflow alert for a Sentry organization using the New Monitors and Alerts system |
| `create-dashboard-with-widgets` | `sentry.createDashboardWithWidgets()` | `--organization-id-or-slug` `--title` | 9 | 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… |
| `create-external-issue-link` | `sentry.createExternalIssueLink()` | `--identifier` `--issueId` `--project` `--uuid` `--webUrl` | 0 | Links an existing Sentry issue to an issue in an external service, or updates an existing link, requiring a configured Sentry App installation `uuid` |
| `create-external-user-for-organization` | `sentry.createExternalUserForOrganization()` | `--external-name` `--id` `--integration-id` `--organization-id-or-slug` `--provider` `--user-id` | 1 | 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… |
| `create-organization-alert-rule` | `sentry.createOrganizationAlertRule()` | `--aggregate` `--name` `--organization-id-or-slug` `--projects` `--query` `--thresholdType` `--timeWindow` `--triggers` | 9 | Creates a Sentry metric alert rule for an organization, mandating a 'critical' trigger, typically for a single project, where actions may require Sentry integrations |
| `create-organization-monitor` | `sentry.createOrganizationMonitor()` | `--config` `--name` `--organization-id-or-slug` `--project` | 4 | 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… |
| `create-organization-team` | `sentry.createOrganizationTeam()` | `--organization-id-or-slug` | 2 | Creates a new team in a Sentry organization, requiring either a 'slug' or 'name' to define the team |
| `create-project-key-with-optional-rate-limiting` | `sentry.createProjectKeyWithOptionalRateLimiting()` | `--organization-id-or-slug` `--project-id-or-slug` | 3 | Creates a new client key (DSN) for an existing Sentry project, with optional custom rate limit configuration |
| `create-project-rule-for-alerts` | `sentry.createProjectRuleForAlerts()` | `--actionMatch` `--actions` `--conditions` `--frequency` `--name` `--organization-id-or-slug` `--project-id-or-slug` | 4 | 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… |
| `create-project-webhook-subscription` | `sentry.createProjectWebhookSubscription()` | `--events` `--organization-id-or-slug` `--project-id-or-slug` `--url` | 0 | 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 |
| `create-release-deploy-for-org` | `sentry.createReleaseDeployForOrg()` | `--environment` `--organization-id-or-slug` `--version` | 5 | Creates a new deploy record in Sentry to track the introduction of a release version into a specific environment |
| `create-release-for-organization` ·common | `sentry.createReleaseForOrganization()` | `--organization-id-or-slug` `--projects` `--version` | 5 | Creates a new Sentry release for an existing organization, associating it with specified projects that must belong to that organization |
| `create-scim-group-for-organization` | `sentry.createScimGroupForOrganization()` | `--displayName` `--organization-id-or-slug` | 0 | Creates a new Sentry team (SCIM group) within an organization via the SCIM API |
| `create-team-project-for-organization` | `sentry.createTeamProjectForOrganization()` | `--name` `--organization-id-or-slug` `--team-id-or-slug` | 3 | Creates a new Sentry project for an existing organization and team, allowing configuration of its name, slug, platform, and default alert rules |
| `create-user-for-saml-integration` | `sentry.createUserForSamlIntegration()` | `--organization-id-or-slug` `--userName` | 1 | Creates a new Sentry organization member via a SCIM request for SAML integration; this action does not support setting secondary emails |
| `delete-alert` | `sentry.deleteAlert()` | `--organization-id-or-slug` `--workflow-id` | 0 | ⚠️ This endpoint is currently in beta and may be subject to change |
| `delete-bulk-alerts` | `sentry.deleteBulkAlerts()` | `--organization-id-or-slug` | 3 | Bulk delete alerts for a given organization |
| `delete-custom-integration` | `sentry.deleteCustomIntegration()` | `--sentry-app-id-or-slug` | 0 | Deletes a custom integration (Sentry App) by its ID or slug |
| `delete-dsyms-for-project` | `sentry.deleteDsymsForProject()` | `--id` `--organization-id-or-slug` `--project-id-or-slug` | 0 | Permanently removes a specific Debug Information File (DIF), used for symbolicating crash reports, from the specified Sentry project and organization |
| `delete-external-issue-by-uuid` | `sentry.deleteExternalIssueByUuid()` | `--external-issue-id` `--uuid` | 0 | Unlinks an external issue (e.g., from Jira/GitHub), identified by `external_issue_id`, from the Sentry app installation specified by `uuid` |
| `delete-external-team-by-id` | `sentry.deleteExternalTeamById()` | `--external-team-id` `--organization-id-or-slug` `--team-id-or-slug` | 0 | Unlinks a previously established external team from a Sentry team; this action does not delete either the Sentry team or the external team |
| `delete-external-user-from-organization` | `sentry.deleteExternalUserFromOrganization()` | `--external-user-id` `--organization-id-or-slug` | 0 | 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 |
| `delete-member-from-team` | `sentry.deleteMemberFromTeam()` | `--member-id` `--organization-id-or-slug` `--team-id-or-slug` | 0 | Removes an organization member from a Sentry team, revoking their team-specific permissions, provided the member is currently part of that team |
| `delete-org-notification-action` | `sentry.deleteOrgNotificationAction()` | `--action-id` `--organization-id-or-slug` | 0 | 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` |
| `delete-organization-alert-rule` | `sentry.deleteOrganizationAlertRule()` | `--alert-rule-id` `--organization-id-or-slug` | 0 | Permanently deletes a metric alert rule from a Sentry organization |
| `delete-organization-dashboard` | `sentry.deleteOrganizationDashboard()` | `--dashboard-id` `--organization-id-or-slug` | 0 | Deletes a custom dashboard or tombstones (marks as deleted) a pre-built dashboard within a Sentry organization |
| `delete-organization-discover-query` | `sentry.deleteOrganizationDiscoverQuery()` | `--organization-id-or-slug` `--query-id` | 0 | Permanently removes a specific saved Discover query (a configuration for exploring event data) from a Sentry organization |
| `delete-organization-integration` | `sentry.deleteOrganizationIntegration()` | `--integration-id` `--organization-id-or-slug` | 0 | Permanently removes an integration installation from a Sentry organization |
| `delete-organization-issue` | `sentry.deleteOrganizationIssue()` | `--issue-id` `--organization-id-or-slug` | 0 | Permanently deletes a specific Sentry issue, identified by its ID, from an organization; this operation is irreversible and idempotent |
| `delete-organization-member` ·common | `sentry.deleteOrganizationMember()` | `--member-id` `--organization-id-or-slug` | 0 | Permanently removes a member from a Sentry organization, revoking their access to that organization and all its associated projects |
| `delete-organization-monitor` | `sentry.deleteOrganizationMonitor()` | `--monitor-id-or-slug` `--organization-id-or-slug` | 1 | Deletes a Sentry cron monitor or, if `environment` is specified, only specific environments within that monitor |
| `delete-organization-release` | `sentry.deleteOrganizationRelease()` | `--organization-id-or-slug` `--version` | 0 | Permanently and irreversibly removes a Sentry release, including all its associated files, identified by its version from the specified organization |
| `delete-organization-release-file` | `sentry.deleteOrganizationReleaseFile()` | `--file-id` `--organization-id-or-slug` `--version` | 0 | Delete a file from an organization release |
| `delete-project-by-id` | `sentry.deleteProjectById()` | `--organization-id-or-slug` `--project-id-or-slug` | 0 | Schedules a Sentry project for asynchronous deletion within a specified organization, hiding it from most public views once the process begins |
| `delete-project-hook` | `sentry.deleteProjectHook()` | `--hook-id` `--organization-id-or-slug` `--project-id-or-slug` | 0 | Deletes a specific service hook from a Sentry project using its organization, project, and hook identifiers |
| `delete-project-issues` | `sentry.deleteProjectIssues()` | `--organization-id-or-slug` `--project-id-or-slug` | 1 | Permanently removes specified issues from a Sentry project; if no issue IDs are provided, it removes the oldest 1000 issues |
| `delete-project-key` | `sentry.deleteProjectKey()` | `--key-id` `--organization-id-or-slug` `--project-id-or-slug` | 0 | Permanently deletes a specific client key (DSN) for a project, preventing it from being used to send events to Sentry |
| `delete-project-monitor` | `sentry.deleteProjectMonitor()` | `--monitor-id-or-slug` `--organization-id-or-slug` `--project-id-or-slug` | 1 | Deletes a Sentry monitor, or optionally only its specified environments, for a given project |
| `delete-project-replay` | `sentry.deleteProjectReplay()` | `--organization-id-or-slug` `--project-id-or-slug` `--replay-id` | 0 | 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 |
| `delete-project-rule` | `sentry.deleteProjectRule()` | `--organization-id-or-slug` `--project-id-or-slug` `--rule-id` | 0 | Permanently deletes a specific issue alert rule from an existing project within an existing Sentry organization |
| `delete-project-team-association` | `sentry.deleteProjectTeamAssociation()` | `--organization-id-or-slug` `--project-id-or-slug` `--team-id-or-slug` | 0 | Revokes a team's access to a Sentry project; this operation is idempotent |
| `delete-release-file-by-id` | `sentry.deleteReleaseFileById()` | `--file-id` `--organization-id-or-slug` `--project-id-or-slug` `--version` | 0 | Permanently deletes a specific build artifact (e.g., source map, application bundle) associated with a project release |
| `delete-symbol-source-from-project` | `sentry.deleteSymbolSourceFromProject()` | `--id` `--organization-id-or-slug` `--project-id-or-slug` | 0 | Deletes a custom symbol source from a Sentry project |
| `delete-team-by-organization-or-team-slug` | `sentry.deleteTeamByOrganizationOrTeamSlug()` | `--organization-id-or-slug` `--team-id-or-slug` | 0 | Schedules a Sentry team for asynchronous deletion, which releases the team's slug for reuse upon successful scheduling |
| `delete-team-from-org-scim-v2` | `sentry.deleteTeamFromOrgScimV2()` | `--organization-id-or-slug` `--team-id` | 0 | Permanently and irreversibly deletes a specific team from a Sentry organization via a SCIM v2 request, provided SCIM integration is enabled for the organization |
| `delete-user-emails-by-id` | `sentry.deleteUserEmailsById()` | `--email` `--user-id` | 0 | 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 |
| `delete-user-from-org` | `sentry.deleteUserFromOrg()` | `--member-id` `--organization-id-or-slug` | 0 | Removes a SCIM-managed member from a Sentry organization that has SCIM enabled, permanently revoking their access |
| `disable-spike-protection` | `sentry.disableSpikeProtection()` | `--organization-id-or-slug` `--projects` | 0 | Disables Spike Protection feature for specified projects within a Sentry organization |
| `fetch-alert` ·common | `sentry.fetchAlert()` | `--organization-id-or-slug` `--workflow-id` | 0 | Retrieves detailed information for a specific alert workflow |
| `fetch-alerts` ·common | `sentry.fetchAlerts()` | `--organization-id-or-slug` | 4 | Retrieves a list of alerts (workflows) for a Sentry organization |
| `fetch-issue-event-by-id` | `sentry.fetchIssueEventById()` | `--event-id` `--issue-id` `--organization-id-or-slug` | 1 | Retrieves the 'latest', 'oldest', or 'recommended' event for a Sentry issue within an organization, optionally filtered by environment(s) |
| `fetch-monitor` ·common | `sentry.fetchMonitor()` | `--detector-id` `--organization-id-or-slug` | 0 | Fetches detailed information for a specific monitor (detector) within an organization |
| `fetch-organization-alert-rules` | `sentry.fetchOrganizationAlertRules()` | `--organization-id-or-slug` | 0 | Retrieves a list of active metric alert rules for an existing Sentry organization, identified by its ID or slug |
| `fetch-organization-release-threshold-statuses` | `sentry.fetchOrganizationReleaseThresholdStatuses()` | `--end` `--organization-id-or-slug` `--start` | 3 | 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… |
| `fetch-organization-replay-count` | `sentry.fetchOrganizationReplayCount()` | `--organization-id-or-slug` | 6 | Retrieves the total count of session replays for a specified Sentry organization, filterable by time range, environment, project, and query |
| `fetch-organization-replay-details` | `sentry.fetchOrganizationReplayDetails()` | `--organization-id-or-slug` `--replay-id` | 10 | 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… |
| `fetch-organization-replay-selectors` | `sentry.fetchOrganizationReplaySelectors()` | `--organization-id-or-slug` | 9 | Retrieves replay selectors (CSS/DOM selectors from session replays) for a Sentry organization |
| `fetch-organizations-monitors` ·common | `sentry.fetchOrganizationsMonitors()` | `--organization-id-or-slug` | 4 | Retrieves monitors (detectors) for a Sentry organization |
| `fetch-project-environment-details` | `sentry.fetchProjectEnvironmentDetails()` | `--environment` `--organization-id-or-slug` `--project-id-or-slug` | 0 | Retrieves detailed information for a specific environment within a Sentry project |
| `fetch-project-ownership-details` | `sentry.fetchProjectOwnershipDetails()` | `--organization-id-or-slug` `--project-id-or-slug` | 0 | Retrieves the ownership configuration, like CODEOWNERS rules or Issue Owner settings, for a specified Sentry project |
| `fetch-project-release-files` | `sentry.fetchProjectReleaseFiles()` | `--organization-id-or-slug` `--project-id-or-slug` `--version` | 0 | 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… |
| `fetch-project-replay-clicks` | `sentry.fetchProjectReplayClicks()` | `--organization-id-or-slug` `--project-id-or-slug` `--replay-id` | 4 | Fetches a list of user click interactions for a specific Sentry session replay, including the clicked DOM element ID and timestamp |
| `fetch-replay-recording-segment` | `sentry.fetchReplayRecordingSegment()` | `--organization-id-or-slug` `--project-id-or-slug` `--replay-id` `--segment-id` | 0 | Retrieves a specific recording segment for a Sentry replay, requiring valid organization, project, replay, and segment identifiers |
| `fetch-tag-values-for-issue` | `sentry.fetchTagValuesForIssue()` | `--issue-id` `--key` `--organization-id-or-slug` | 2 | 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 |
| `get-activation-of-alert-rule-for-organization` ·deprecated | `sentry.getActivationOfAlertRuleForOrganization()` | `--alert-rule-id` `--organization-id-or-slug` | 0 | Retrieves all activations for a specific metric alert rule. ⚠️ WARNING: This endpoint has been removed from Sentry as of January 2025 |
| `get-alerts` ·common | `sentry.getAlerts()` | `--organization` | 3 | Retrieve all combined alert rules and monitors for a Sentry organization |
| `get-app-installations-for-organization` | `sentry.getAppInstallationsForOrganization()` | `--organization-id-or-slug` | 0 | Retrieves a list of Sentry App installations for a given organization, which must exist |
| `get-integration-details-by-org` | `sentry.getIntegrationDetailsByOrg()` | `--integration-id` `--organization-id-or-slug` | 0 | Retrieves details for a specific integration, identified by `integration_id`, installed within an existing Sentry organization, identified by `organization_id_or_slug` |
| `get-oldest-event` ·common | `sentry.getOldestEvent()` | `--issue-id` `--organization-id-or-slug` | 1 | Retrieves the oldest (first) event associated with a Sentry issue within an organization |
| `get-organization-by-id-or-slug` ·common | `sentry.getOrganizationByIdOrSlug()` | `--organization-id-or-slug` | 1 | 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 |
| `get-organization-details` ·common | `sentry.getOrganizationDetails()` | — | 4 | Retrieves Sentry organizations accessible via the current authentication, with scope varying between user (all in region) and API key (linked org only) credentials |
| `get-organization-environments` | `sentry.getOrganizationEnvironments()` | `--organization-id-or-slug` | 1 | Lists deployment environments for a Sentry organization, optionally filtered by visibility status |
| `get-organization-issue-details` | `sentry.getOrganizationIssueDetails()` | `--issue-id` `--organization-id-or-slug` | 0 | Retrieves detailed information for a specific issue within a Sentry organization |
| `get-organization-release-version` ·common | `sentry.getOrganizationReleaseVersion()` | `--organization-id-or-slug` `--version` | 8 | Retrieves detailed information, including optional health data and statistics, for a specific release version within a Sentry organization |
| `get-organization-sessions` | `sentry.getOrganizationSessions()` | `--field` `--organization-id-or-slug` | 12 | 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… |
| `get-organization-stats-summary` | `sentry.getOrganizationStatsSummary()` | `--field` `--organization-id-or-slug` | 9 | 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… |
| `get-project-event-stats` | `sentry.getProjectEventStats()` | `--organization-id-or-slug` `--project-id-or-slug` | 4 | Retrieves time-series event statistics for a Sentry project |
| `get-project-events` | `sentry.getProjectEvents()` | `--organization-id-or-slug` `--project-id-or-slug` | 6 | Retrieves a list of error events for a specified project within a Sentry organization, with options for pagination and detail level |
| `get-project-hook` | `sentry.getProjectHook()` | `--hook-id` `--organization-id-or-slug` `--project-id-or-slug` | 0 | Retrieves detailed information for an existing service hook within a Sentry project |
| `get-project-list` | `sentry.getProjectList()` | — | 1 | Lists all Sentry projects the authenticated token has membership access to across all organizations |
| `get-project-monitor-by-id` | `sentry.getProjectMonitorById()` | `--monitor-id-or-slug` `--organization-id-or-slug` `--project-id-or-slug` | 0 | Retrieves detailed information for a specific Sentry cron monitor, provided the organization, project, and monitor exist |
| `get-project-rule-details` | `sentry.getProjectRuleDetails()` | `--organization-id-or-slug` `--project-id-or-slug` `--rule-id` | 0 | Retrieves detailed information for a specific issue alert rule within a Sentry project |
| `get-scim-group-by-team-id` | `sentry.getScimGroupByTeamId()` | `--organization-id-or-slug` `--team-id` | 0 | Retrieves SCIM group information for a specific Sentry team |
| `get-team-members-by-id-or-slug` | `sentry.getTeamMembersByIdOrSlug()` | `--organization-id-or-slug` `--team-id-or-slug` | 1 | Retrieves all active members of a Sentry team with detailed user information, roles, and permissions |
| `get-who-viewed-replay-by-project` | `sentry.getWhoViewedReplayByProject()` | `--organization-id-or-slug` `--project-id-or-slug` `--replay-id` | 0 | Retrieves users who viewed a specific, existing session replay within a Sentry project and organization |
| `ingest-event-via-dsn` ·common | `sentry.ingestEventViaDsn()` | `--dsn` | 16 | Ingests a single custom event into a Sentry project using its DSN via the Envelope ingestion endpoint |
| `list-organization-dashboards` | `sentry.listOrganizationDashboards()` | `--organization-id-or-slug` | 2 | Retrieves a list of custom dashboards for a Sentry organization, with pagination support |
| `list-organization-members` | `sentry.listOrganizationMembers()` | `--organization-id-or-slug` | 0 | Lists all members, including those with pending invitations, for a Sentry organization |
| `list-organization-releases` | `sentry.listOrganizationReleases()` | `--organization-id-or-slug` | 1 | Retrieves a list of releases for an existing Sentry organization, optionally filtering by a query string that matches the start of the release version |
| `list-organization-repositories` | `sentry.listOrganizationRepositories()` | `--organization-id-or-slug` | 0 | Retrieves a list of version control repositories for a specific Sentry organization, which must exist and is identified by its ID or slug |
| `list-organization-s-client-keys` ·common | `sentry.listOrganizationSClientKeys()` | `--organization-id-or-slug` | 3 | Lists all client keys (DSNs) across all projects in an organization |
| `list-organization-user-teams` | `sentry.listOrganizationUserTeams()` | `--organization-id-or-slug` | 0 | Retrieves a list of all teams that the authenticated user has access to within the specified Sentry organization |
| `list-organizations` ·common | `sentry.listOrganizations()` | — | 4 | Retrieves a list of organizations available to the authenticated session |
| `list-organizations-issues` ·common | `sentry.listOrganizationsIssues()` | `--organization-id-or-slug` | 14 | Returns a list of issues (error groups) for an organization |
| `list-project-tags` | `sentry.listProjectTags()` | `--organization-id-or-slug` `--project-id-or-slug` | 0 | Retrieves all tags that have been recorded for events within a Sentry project, along with statistical information for each tag |
| `list-project-users` | `sentry.listProjectUsers()` | `--organization-id-or-slug` `--project-id-or-slug` | 1 | Retrieves users who have interacted with or are recognized within a specific Sentry project, optionally filtered by a query |
| `list-projects-user-feedback` | `sentry.listProjectsUserFeedback()` | `--organization-id-or-slug` `--project-id-or-slug` | 2 | Retrieves a list of legacy user feedback items within a Sentry project |
| `list-scim-v2-organization-users` | `sentry.listScimV2OrganizationUsers()` | `--organization-id-or-slug` | 4 | Retrieves a paginated list of SCIM (System for Cross-domain Identity Management) users for a Sentry organization, allowing for filtering, pagination, and attribute exclusion |
| `list-seer-ai-models` | `sentry.listSeerAiModels()` | — | 0 | Retrieves the list of AI models currently used in production in Seer |
| `list-tags-values-for-issue` | `sentry.listTagsValuesForIssue()` | `--issue-id` `--key` `--organization-id-or-slug` | 1 | Returns a list of values associated with this key for an issue |
| `list-teams-in-organization` | `sentry.listTeamsInOrganization()` | `--organization-id-or-slug` | 2 | Lists teams for an existing Sentry organization, optionally including project details and supporting pagination via a cursor |
| `manage-team-external-integrations` | `sentry.manageTeamExternalIntegrations()` | `--external-name` `--integration-id` `--organization-id-or-slug` `--provider` `--team-id-or-slug` | 1 | 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 |
| `modify-organization-notification-action` | `sentry.modifyOrganizationNotificationAction()` | `--action-id` `--organization-id-or-slug` `--projects` `--service-type` `--trigger-type` | 3 | Modifies an organization's notification action, specifically for `spike-protection` triggers |
| `modify-organization-settings` | `sentry.modifyOrganizationSettings()` | `--organization-id-or-slug` | 32 | Updates settings for a Sentry organization, such as name, slug, member roles, privacy, and integrations; if `avatarType` is 'upload', `avatar` (base64 image) is required |
| `modify-release-file-attributes` | `sentry.modifyReleaseFileAttributes()` | `--file-id` `--organization-id-or-slug` `--version` | 2 | Updates attributes (e.g., name, distribution) of a specific file within an existing release, identified by organization, version, and file ID |
| `mutate-organization-s-alerts` ·common | `sentry.mutateOrganizationSAlerts()` | `--enabled` `--organization-id-or-slug` | 3 | Bulk enable or disable alerts for an organization |
| `mutate-organizations-monitors` | `sentry.mutateOrganizationsMonitors()` | `--enabled` `--organization-id-or-slug` | 3 | Bulk enable or disable monitors for an organization |
| `patch-scim-group-operations` | `sentry.patchScimGroupOperations()` | `--Operations` `--organization-id-or-slug` `--team-id` | 0 | Performs SCIM PATCH operations (RFC 7644) to update attributes of a SCIM-enabled Sentry team, provided SCIM integration is active for the organization |
| `patch-user-active-status-in-organization` | `sentry.patchUserActiveStatusInOrganization()` | `--Operations` `--member-id` `--organization-id-or-slug` | 0 | Deactivates and permanently deletes a Sentry organization member by using a SCIM PATCH operation to set their 'active' attribute to 'false' |
| `post-spike-protection-for-organization` | `sentry.postSpikeProtectionForOrganization()` | `--organization-id-or-slug` `--projects` | 0 | Enables or updates Spike Protection for specified projects (or all projects using `['$all']`) within an existing Sentry organization, to which the projects must belong |
| `query-explore-events-in-timeseries-format` | `sentry.queryExploreEventsInTimeseriesFormat()` | `--dataset` `--organization-id-or-slug` | 15 | Retrieves explore data for a given organization as a timeseries |
| `retrieve-aggregated-test-result-metrics` | `sentry.retrieveAggregatedTestResultMetrics()` | `--organization-id-or-slug` `--owner` `--repository` | 2 | Retrieves aggregated test result metrics for a repository, owner, and organization |
| `retrieve-alert-rule-details` | `sentry.retrieveAlertRuleDetails()` | `--alert-rule-id` `--organization-id-or-slug` | 0 | Retrieves detailed information for a specific metric alert rule within a Sentry organization |
| `retrieve-commit-files-for-release` | `sentry.retrieveCommitFilesForRelease()` | `--organization-id-or-slug` `--version` | 0 | Retrieves files changed in commits for a specified Sentry release; the release must exist and have linked commits |
| `retrieve-commits-for-organization-repo` | `sentry.retrieveCommitsForOrganizationRepo()` | `--organization-id-or-slug` `--repo-id` | 0 | Retrieves a list of commits for a given repository within a Sentry organization |
| `retrieve-custom-integ-issue-links-given-issue` | `sentry.retrieveCustomIntegIssueLinksGivenIssue()` | `--issue-id` `--organization-id-or-slug` | 0 | Retrieves all external issue links for a Sentry issue |
| `retrieve-custom-integration-by-id-or-slug` | `sentry.retrieveCustomIntegrationByIdOrSlug()` | `--sentry-app-id-or-slug` | 0 | Retrieves detailed information about a custom integration (Sentry App) by its slug |
| `retrieve-custom-integs-created-by-org` | `sentry.retrieveCustomIntegsCreatedByOrg()` | `--organization-id-or-slug` | 0 | Retrieves custom integrations (Sentry Apps) created by an organization |
| `retrieve-data-forwarders-for-organization` | `sentry.retrieveDataForwardersForOrganization()` | `--organization-id-or-slug` | 0 | Returns a list of data forwarders for an organization |
| `retrieve-dsym-files-for-project` | `sentry.retrieveDsymFilesForProject()` | `--organization-id-or-slug` `--project-id-or-slug` | 0 | Retrieve a list of debug information files (dSYM files) for a specified Sentry project, used for symbolication to display human-readable stack traces |
| `retrieve-event-id-for-organization` | `sentry.retrieveEventIdForOrganization()` | `--event-id` `--organization-id-or-slug` | 0 | Resolves a Sentry event ID to its project and issue details within an accessible Sentry organization |
| `retrieve-files-for-release` | `sentry.retrieveFilesForRelease()` | `--organization-id-or-slug` `--version` | 0 | 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… |
| `retrieve-issue-events-by-id` | `sentry.retrieveIssueEventsById()` | `--issue-id` `--organization-id-or-slug` | 7 | Retrieves events for a specified Sentry `issue_id`, which must be an existing issue |
| `retrieve-issue-hashes-for-organization` | `sentry.retrieveIssueHashesForOrganization()` | `--issue-id` `--organization-id-or-slug` | 2 | Retrieves a list of grouping checksums (hashes) generated by Sentry for a specific issue within an organization, used for understanding event aggregation |
| `retrieve-issue-tag-details` | `sentry.retrieveIssueTagDetails()` | `--issue-id` `--key` | 1 | 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) |
| `retrieve-monitor` ·common | `sentry.retrieveMonitor()` | `--monitor-id-or-slug` `--organization-id-or-slug` | 1 | Retrieves detailed information for a specific monitor within an organization |
| `retrieve-monitor-checkins` | `sentry.retrieveMonitorCheckins()` | `--monitor-id-or-slug` `--organization-id-or-slug` `--project-id-or-slug` | 0 | Retrieves the history of check-ins for a Sentry monitor, providing insights into the health and performance of associated scheduled tasks |
| `retrieve-monitor-checkins-by-org` | `sentry.retrieveMonitorCheckinsByOrg()` | `--monitor-id-or-slug` `--organization-id-or-slug` | 0 | Retrieves check-ins (pings/heartbeats of a monitored cron job or task) for a specific monitor within a Sentry organization |
| `retrieve-notification-action-by-org-id` | `sentry.retrieveNotificationActionByOrgId()` | `--action-id` `--organization-id-or-slug` | 0 | Retrieves details for a specific Spike Protection Notification Action, which defines alerts for triggered spike protection rules, within a Sentry organization |
| `retrieve-org-integration-config` | `sentry.retrieveOrgIntegrationConfig()` | `--organization-id-or-slug` | 1 | Retrieves configuration for all integrations, or a specific integration if `providerKey` is given, for an existing Sentry organization |
| `retrieve-organization-dashboard` | `sentry.retrieveOrganizationDashboard()` | `--dashboard-id` `--organization-id-or-slug` | 0 | Fetches detailed information about a specific custom dashboard within a Sentry organization |
| `retrieve-organization-events` | `sentry.retrieveOrganizationEvents()` | `--field` `--organization-id-or-slug` | 8 | 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 |
| `retrieve-organization-integrations-list` | `sentry.retrieveOrganizationIntegrationsList()` | `--organization-id-or-slug` | 3 | Retrieves a list of available integrations for an existing Sentry organization |
| `retrieve-organization-member` | `sentry.retrieveOrganizationMember()` | `--member-id` `--organization-id-or-slug` | 0 | 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 |
| `retrieve-organization-monitors` | `sentry.retrieveOrganizationMonitors()` | `--organization-id-or-slug` | 3 | Retrieves cron monitors for a Sentry organization, including details of nested monitor environments |
| `retrieve-organization-projects` | `sentry.retrieveOrganizationProjects()` | `--organization-id-or-slug` | 1 | Retrieves a list of Sentry projects for a specified organization (which must be accessible), supporting pagination via cursor |
| `retrieve-organization-relay-usage` | `sentry.retrieveOrganizationRelayUsage()` | `--organization-id-or-slug` | 0 | Retrieves a list of trusted Sentry Relays configured for an organization |
| `retrieve-organization-release-commits` | `sentry.retrieveOrganizationReleaseCommits()` | `--organization-id-or-slug` `--version` | 0 | Retrieves a list of commits for a given release version in an existing Sentry organization, if the release exists |
| `retrieve-organization-replays` | `sentry.retrieveOrganizationReplays()` | `--organization-id-or-slug` | 10 | Fetches session replays for a Sentry organization; use `statsPeriod` for relative time, or `start` and `end` (used together) for absolute time ranges |
| `retrieve-organization-scim-groups` | `sentry.retrieveOrganizationScimGroups()` | `--organization-id-or-slug` | 4 | 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 |
| `retrieve-organization-stats-v2` | `sentry.retrieveOrganizationStatsV2()` | `--field` `--groupBy` `--organization-id-or-slug` | 8 | 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)… |
| `retrieve-paginated-repository-tokens` | `sentry.retrievePaginatedRepositoryTokens()` | `--organization-id-or-slug` `--owner` | 4 | Retrieves a paginated list of repository tokens for a given owner |
| `retrieve-project-environments` | `sentry.retrieveProjectEnvironments()` | `--organization-id-or-slug` `--project-id-or-slug` | 1 | Retrieves a list of environments for an existing project within a Sentry organization |
| `retrieve-project-event-by-id` | `sentry.retrieveProjectEventById()` | `--event-id` `--organization-id-or-slug` `--project-id-or-slug` | 0 | Retrieves detailed information for a specific Sentry event using its ID, organization identifier, and project identifier |
| `retrieve-project-filter-data` | `sentry.retrieveProjectFilterData()` | `--organization-id-or-slug` `--project-id-or-slug` | 0 | Retrieves a Sentry project's current data filtering settings, used to ignore events from sources like localhost, web crawlers, or legacy browsers |
| `retrieve-project-hooks` | `sentry.retrieveProjectHooks()` | `--organization-id-or-slug` `--project-id-or-slug` | 1 | Return a list of service hooks (webhooks) bound to a Sentry project, used to send notifications to external services upon event occurrences |
| `retrieve-project-issues-list` ·common | `sentry.retrieveProjectIssuesList()` | `--organization-id-or-slug` `--project-id-or-slug` | 5 | 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 |
| `retrieve-project-key-details` | `sentry.retrieveProjectKeyDetails()` | `--key-id` `--organization-id-or-slug` `--project-id-or-slug` | 0 | Retrieves details of a specific client key (DSN) for a Sentry project, which is used by Sentry SDKs to send event data |
| `retrieve-project-keys-by-org-and-project` | `sentry.retrieveProjectKeysByOrgAndProject()` | `--organization-id-or-slug` `--project-id-or-slug` | 2 | Retrieves a list of client keys (DSNs), used by Sentry SDKs to send events, for a specified project within an organization |
| `retrieve-project-members-list` | `sentry.retrieveProjectMembersList()` | `--organization-id-or-slug` `--project-id-or-slug` | 0 | Retrieves active organization members belonging to any team assigned to the specified Sentry project |
| `retrieve-project-release-file-details` | `sentry.retrieveProjectReleaseFileDetails()` | `--file-id` `--organization-id-or-slug` `--project-id-or-slug` `--version` | 1 | Retrieves metadata (default) or raw content (if `download` is true) for a specific file within a Sentry project's release version |
| `retrieve-project-rules-by-org-and-project-id` | `sentry.retrieveProjectRulesByOrgAndProjectId()` | `--organization-id-or-slug` `--project-id-or-slug` | 0 | Retrieves a list of active issue alert rules associated with a specific project within an organization |
| `retrieve-project-symbol-sources` | `sentry.retrieveProjectSymbolSources()` | `--organization-id-or-slug` `--project-id-or-slug` | 1 | Retrieves custom symbol sources for a Sentry project, either listing all or fetching a specific one if its ID is provided |
| `retrieve-project-tag-values` | `sentry.retrieveProjectTagValues()` | `--key` `--organization-id-or-slug` `--project-id-or-slug` | 0 | Retrieves up to 1000 unique values for a specified tag key that has been recorded for events within a Sentry project |
| `retrieve-project-teams` | `sentry.retrieveProjectTeams()` | `--organization-id-or-slug` `--project-id-or-slug` | 0 | Retrieves a list of teams with explicit access to a specific project within a Sentry organization |
| `retrieve-release-commits` | `sentry.retrieveReleaseCommits()` | `--organization-id-or-slug` `--project-id-or-slug` `--version` | 0 | Retrieves a list of commits associated with a specific release version within a Sentry project |
| `retrieve-release-deployments` | `sentry.retrieveReleaseDeployments()` | `--organization-id-or-slug` `--version` | 0 | Retrieves a list of all deployment records for a specific release version in an organization, detailing each deployment's environment and timestamps |
| `retrieve-release-file-by-id` | `sentry.retrieveReleaseFileById()` | `--file-id` `--organization-id-or-slug` `--version` | 1 | 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 |
| `retrieve-replay-recording-segments` | `sentry.retrieveReplayRecordingSegments()` | `--organization-id-or-slug` `--project-id-or-slug` `--replay-id` | 2 | Retrieves a paginated list of recording segments for a specific Sentry replay, used for reconstructing or analyzing the replay |
| `retrieve-saved-discover-queries` | `sentry.retrieveSavedDiscoverQueries()` | `--organization-id-or-slug` | 4 | Retrieves a paginated list of saved Discover queries for a Sentry organization |
| `retrieve-saved-discover-query-for-organization` | `sentry.retrieveSavedDiscoverQueryForOrganization()` | `--organization-id-or-slug` `--query-id` | 0 | Retrieves a specific saved Discover query (a predefined set of filters and conditions for exploring event data) for a Sentry organization |
| `retrieve-seer-issue-fix-state` ·common | `sentry.retrieveSeerIssueFixState()` | `--issue-id` `--organization-id-or-slug` | 0 | Retrieves the current detailed state of an AI-assisted autofix process for a Sentry issue |
| `retrieve-short-id-for-organization` | `sentry.retrieveShortIdForOrganization()` | `--organization-id-or-slug` `--short-id` | 0 | 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 |
| `retrieve-source-map-debug-event` | `sentry.retrieveSourceMapDebugEvent()` | `--event-id` `--exception-idx` `--frame-idx` `--organization-id-or-slug` `--project-id-or-slug` | 0 | Retrieves detailed debug information for diagnosing source map processing issues for a specific Sentry event, stack trace frame, and exception index |
| `retrieve-team-info-via-organization-id-or-slug` ·common | `sentry.retrieveTeamInfoViaOrganizationIdOrSlug()` | `--organization-id-or-slug` `--team-id-or-slug` | 2 | 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) |
| `retrieve-team-projects` | `sentry.retrieveTeamProjects()` | `--organization-id-or-slug` `--team-id-or-slug` | 1 | Retrieves a list of Sentry projects for a specific team within an organization, supporting pagination via a cursor |
| `retrieve-user-email-information` | `sentry.retrieveUserEmailInformation()` | `--user-id` | 0 | Retrieves a list of email addresses for an existing Sentry user, identified by their `user_id` |
| `retrieve-user-via-scim-api` | `sentry.retrieveUserViaScimApi()` | `--member-id` `--organization-id-or-slug` | 0 | Retrieves an individual Sentry organization member's details using the SCIM v2 API |
| `save-organization-discover-query` | `sentry.saveOrganizationDiscoverQuery()` | `--name` `--organization-id-or-slug` | 13 | 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 |
| `start-seer-issue-fix` ·common | `sentry.startSeerIssueFix()` | `--issue-id` `--organization-id-or-slug` | 4 | Trigger a Seer Issue Fix run for a specific issue |
| `submit-notification-action-api-data` | `sentry.submitNotificationActionApiData()` | `--organization-id-or-slug` `--service-type` `--trigger-type` | 4 | 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… |
| `submit-user-feedback` | `sentry.submitUserFeedback()` | `--comments` `--email` `--event-id` `--name` `--organization-id-or-slug` `--project-id-or-slug` | 0 | Submits user feedback tied to a specific Sentry event |
| `switch-team-role-for-member` | `sentry.switchTeamRoleForMember()` | `--member-id` `--organization-id-or-slug` `--team-id-or-slug` | 1 | 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 |
| `toggle-project-filter-status` | `sentry.toggleProjectFilterStatus()` | `--filter-id` `--organization-id-or-slug` `--project-id-or-slug` | 2 | 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` |
| `update-alert-by-id` ·common | `sentry.updateAlertById()` | `--name` `--organization-id-or-slug` `--workflow-id` | 6 | Update an existing Sentry alert (workflow) by ID |
| `update-environment-visibility` | `sentry.updateEnvironmentVisibility()` | `--environment` `--isHidden` `--organization-id-or-slug` `--project-id-or-slug` | 0 | Updates the visibility of a specific environment within a Sentry project |
| `update-existing-custom-integration` ·common | `sentry.updateExistingCustomIntegration()` | `--name` `--scopes` `--sentry-app-id-or-slug` | 10 | Updates an existing custom integration (Sentry App) with new configuration |
| `update-external-team-integration` | `sentry.updateExternalTeamIntegration()` | `--external-name` `--external-team-id` `--integration-id` `--organization-id-or-slug` `--provider` `--team-id-or-slug` | 1 | 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… |
| `update-external-user-for-organization` | `sentry.updateExternalUserForOrganization()` | `--external-name` `--external-user-id` `--id` `--integration-id` `--organization-id-or-slug` `--provider` `--user-id` | 1 | Updates attributes of an existing external user linkage (identified by `external_user_id`) within a Sentry organization (specified by `organization_id_or_slug`) |
| `update-issue-attributes-in-organization` | `sentry.updateIssueAttributesInOrganization()` | `--issue-id` `--organization-id-or-slug` | 9 | Updates specified attributes of an existing Sentry issue within a Sentry organization, leaving other attributes unchanged |
| `update-monitor` ·common | `sentry.updateMonitor()` | `--config` `--monitor-id-or-slug` `--name` `--organization-id-or-slug` `--project` | 4 | Updates a monitor's configuration and settings |
| `update-monitor-by-id` | `sentry.updateMonitorById()` | `--detectorId` `--name` `--organizationIdOrSlug` `--type` | 6 | Updates an existing Sentry monitor (detector) for metric-based issue detection |
| `update-monitor-for-project` ·common | `sentry.updateMonitorForProject()` | `--config` `--monitor-id-or-slug` `--name` `--organization-id-or-slug` `--project` `--project-id-or-slug` | 4 | Updates a monitor for a project |
| `update-organization-alert-rules` | `sentry.updateOrganizationAlertRules()` | `--aggregate` `--alert-rule-id` `--name` `--organization-id-or-slug` `--projects` `--query` `--thresholdType` `--timeWindow` `--triggers` | 9 | Replaces an existing Sentry metric alert rule's configuration; fields not provided in the request are removed or reset |
| `update-organization-dashboard` | `sentry.updateOrganizationDashboard()` | `--dashboard-id` `--organization-id-or-slug` | 10 | Updates an existing custom dashboard, allowing modifications to its title, widgets, and data filters; providing `widgets`, `projects`, `environment`, `period`, `start`, `end`, or `filters` will… |
| `update-organization-member-role` | `sentry.updateOrganizationMemberRole()` | `--member-id` `--organization-id-or-slug` | 2 | 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… |
| `update-project-details` ·common | `sentry.updateProjectDetails()` | `--organization-id-or-slug` `--project-id-or-slug` | 9 | 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… |
| `update-project-issue-status-and-details` ·common | `sentry.updateProjectIssueStatusAndDetails()` | `--organization-id-or-slug` `--project-id-or-slug` | 16 | 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) |
| `update-project-key-configuration` | `sentry.updateProjectKeyConfiguration()` | `--key-id` `--organization-id-or-slug` `--project-id-or-slug` | 8 | 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… |
| `update-project-ownership-settings` | `sentry.updateProjectOwnershipSettings()` | `--organization-id-or-slug` `--project-id-or-slug` | 4 | Updates the ownership configuration settings (raw rules, fallthrough, auto-assignment, CODEOWNERS sync) for a Sentry project; omitted attributes retain their current values |
| `update-project-release-file-details` | `sentry.updateProjectReleaseFileDetails()` | `--file-id` `--organization-id-or-slug` `--project-id-or-slug` `--version` | 2 | Updates the name (path) or distribution identifier of a specific file within an existing project release in Sentry |
| `update-project-rule-by-id` | `sentry.updateProjectRuleById()` | `--actionMatch` `--actions` `--conditions` `--frequency` `--name` `--organization-id-or-slug` `--project-id-or-slug` `--rule-id` | 4 | 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 |
| `update-projects-symbol-source` | `sentry.updateProjectsSymbolSource()` | `--id` `--name` `--organization-id-or-slug` `--project-id-or-slug` `--type` | 16 | Updates an existing custom symbol source (HTTP, GCS, or S3) in a project for fetching debug symbols |
| `update-release-details-for-organization` | `sentry.updateReleaseDetailsForOrganization()` | `--organization-id-or-slug` `--version` | 5 | Updates an existing Sentry release's details for an organization, including its reference, URL, release date, associated commits, or repository references |
| `update-saved-query-for-organization` | `sentry.updateSavedQueryForOrganization()` | `--name` `--organization-id-or-slug` `--query-id` | 13 | Updates an existing Discover saved query for a Sentry organization |
| `update-team-information-by-organization-id` | `sentry.updateTeamInformationByOrganizationId()` | `--organization-id-or-slug` `--slug` `--team-id-or-slug` | 0 | Updates the slug for an existing team within a Sentry organization |
| `update-user-email` | `sentry.updateUserEmail()` | `--email` `--user-id` | 0 | Updates the primary email address for a Sentry user |
| `update-webhook-configuration-xp` | `sentry.updateWebhookConfigurationXp()` | `--events` `--hook-id` `--organization-id-or-slug` `--project-id-or-slug` `--url` | 0 | Updates an existing Sentry service hook's target URL and subscribed event types for a given project and organization |
| `upload-dsyms-file-to-project` | `sentry.uploadDsymsFileToProject()` | `--organization-id-or-slug` `--project-id-or-slug` | 1 | Uploads a dSYM (debug symbols) zip archive, containing an Apple .dSYM folder, to the specified Sentry project for symbolicating crash reports from Apple platforms |
| `upload-file-to-project-release` | `sentry.uploadFileToProjectRelease()` | `--organization-id-or-slug` `--project-id-or-slug` `--version` | 4 | 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 |
| `upload-release-file-to-organization` | `sentry.uploadReleaseFileToOrganization()` | `--organization-id-or-slug` `--version` | 4 | Uploads a new file, such as a source map or debug information, to an existing release version in a Sentry organization |
| `validate-credential` ·common | `sentry.validateCredential()` | — | 0 | Validates Sentry API credentials by retrieving the authenticated user's information |
| `view-organization-notification-actions` | `sentry.viewOrganizationNotificationActions()` | `--organization-id-or-slug` | 3 | 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' |

## Docs

- [run CLI](https://docs.boxd.sh/cli/run): Call connected integrations from the shell, connect new ones, and run automations.
- [Quickstart](https://docs.boxd.sh/guides/integrations/quickstart): Connect an integration, call it from the shell, and turn a script into an automation.
- [Connections](https://docs.boxd.sh/guides/integrations/connections): Connect an account once, for yourself or for your whole organization.
- [Scripts](https://docs.boxd.sh/guides/automations/scripts): Typed integrations, triggers, schedules and state in a .run.ts file.
- [Jobs](https://docs.boxd.sh/guides/automations/jobs): How a script becomes a background job: states, retries, sleep and wake.
- [Beyond the catalog](https://docs.boxd.sh/guides/automations/beyond-the-catalog): Reach your own APIs, databases and cloud accounts from a script.