Sentry

ID or slug of the Sentry project.

ID or slug of the Sentry organization to which the project belongs.

Dictionary with project details, including ID, name, slug, platform, creation date, and other settings.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The email address of the user to invite or add to the organization.

Primary organization-level role. `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`.

If `True`, resends an invitation to a user previously invited but who has not yet accepted.

List of team-specific role assignments. Common roles: `contributor` (views/acts on issues, may add members per org settings) and `admin` (full team/project management).

If `True`, an invitation email is sent to the user. Set to `False` to add the member without an email notification.

The unique identifier (ID or slug) of the Sentry organization to which the member will be added.

A dictionary containing details of the organization member who was added or invited, such as their ID, email, role, and status.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The email address to be added to or removed from the user's Sentry account. Ensure this is a valid email format.

The unique identifier of the Sentry user (e.g., numeric ID or 'self') for whom the email address is being managed.

A dictionary containing Sentry's response. This typically reflects the updated state of the user's email addresses or the status of the operation. For instance, it might contain a list of all current emails for the user (possibly nested under a key like 'emails') or details of the specific email that was managed.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

ID of the existing organization member to be added to the team.

The ID or slug of the team to which the member will be added. Slugs are typically lowercase and use hyphens.

The ID or slug of the organization. Slugs are typically lowercase and use hyphens.

Contains data on the operation's outcome, which varies if the member was newly added, an access request was generated, or the member was already on the team.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The unique identifier (ID) or human-readable slug for the Sentry team that will be granted access to the project.

The unique identifier (ID) or human-readable slug for the Sentry project. Access will be granted to this project.

The unique identifier (ID) or human-readable slug for the Sentry organization. This organization contains both the project and the team.

A dictionary containing the details of the Sentry project, reflecting the addition of the team.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

Optional client-specified unique dashboard identifier; Sentry generates one if omitted.

Absolute end datetime (ISO 8601) for time range; 'start' must also be set for custom absolute range.

If true, time range is UTC; otherwise, defaults to user's local time or organization settings.

Absolute start datetime (ISO 8601) for time range; 'end' must also be set for custom absolute range.

Title for the new dashboard.

Default relative time range (e.g., '24h', '7d', 'auto'); 'auto' is often 14 days. Overridden if 'start' and 'end' are provided.

Additional key-value filters (Sentry search syntax for keys) for the dashboard.

List of widget configurations defining appearance, data queries, and layout.

Project IDs to scope dashboard data; if empty/null, may apply to all accessible projects based on org settings.

Environment names (e.g., 'production') to filter data; if empty/null, all environments included.

ID or slug of the Sentry organization where the dashboard will be created.

Representation of the created dashboard, including its ID, title, widget configurations, and properties.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The unique numeric identifier for the external actor linkage being created. Its specific use may depend on the integration or Sentry's internal handling.

The numeric ID of the Sentry user to be linked with the external identity.

The external identity provider. Allowed values: `github`, `github_enterprise`, `slack`, `gitlab`, `msteams`, `custom_scm`.

The user's unique identifier on the external provider's platform (e.g., GitHub user ID, Slack member ID). This ID is specific to the selected `provider`.

The display name of the user as known on the external provider's platform (e.g., GitHub username, Slack display name).

The numeric ID of the Sentry integration that corresponds to the specified provider and is configured for the organization.

The unique identifier (ID or slug) of the Sentry organization where the external user linkage will be created.

A dictionary containing the representation of the created external user linkage. The structure may include details such as the Sentry user ID, external user ID, provider, and integration ID.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The name for the alert rule. Maximum length of 256 characters.

The ID of the Sentry team or user that owns this alert rule. Can be a numeric ID or a string in the format 'team:<team_id>' or 'user:<user_id>'.

An event search query to filter events for the alert. For example, to include only transactions with status code 400, use `http.status_code:400`. Use an empty string for no filter.

The Sentry dataset this query will execute on. Valid values include `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.

A list of project slugs to filter by. For metric alerts, this list is typically limited to containing a single project slug.

List of trigger configurations. Each trigger must specify `label` ('critical' or 'warning'; 'critical' is mandatory), `alertThreshold` (numeric value to trigger), and `actions`. Each action specifies `type` (e.g., 'email', 'slack'), `targetType` (e.g., 'specific', 'user'), `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').

The aggregate function used in this alert rule. Valid functions include `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.

The type of query. If no value is provided, `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.

A list of event types this alert will relate to. Valid values are `default` (for events captured via Capture Message), `error`, and `transaction`.

The time period in minutes to aggregate over. Supported values: `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).

The name of the environment to filter by. If None or omitted, the alert rule applies to all environments.

Integer representing the monitor type. This determines if the alert rule is actively monitored or monitored based on a specific activation condition. Consult Sentry documentation for specific values and their meanings.

The comparison operator for the critical and warning thresholds. `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'.

Optional. The time delta in minutes for the comparison period. Required when using a percentage change threshold (e.g., 'X% higher/lower compared to `comparisonDelta` minutes ago'). Cannot be used for Crash Free Session Rate or Crash Free User Rate alerts.

Optional. The numeric value the metric must reach to resolve an active alert. If not provided, it's automatically set based on the lowest severity trigger's `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.

Optional integer. Represents a trigger condition for when to start monitoring the alert rule, typically used when `monitorType` indicates conditional monitoring. Consult Sentry documentation for specific values.

The ID or slug of the organization to which this alert rule belongs.

A dictionary containing the details of the newly created organization alert rule.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The human-readable name for the monitor. This name is used in notifications and the Sentry UI.

A unique identifier for the monitor within the organization. If not provided, Sentry will generate one. It must match the pattern `^[a-z][a-z0-9_\-]*$`. Changing this slug after creation requires updating any instrumented check-in calls.

The type of the monitor. Must be 'cron_job', indicating a monitor for a scheduled task or cron job.

The Sentry actor ID (team or user) to be designated as the owner of this monitor. Format: 'user:{user_id}' or 'team:{team_id}'. If not provided, the monitor will be unassigned.

The initial status of the monitor. 'active' monitors accept check-ins and contribute to quotas, while 'disabled' monitors do not. Allowed values: 'active', 'disabled'.

A boolean flag to control incident creation for this monitor. If true, monitor incidents (alerts) will be suppressed. Defaults to false if not provided.

The identifier (ID or slug) of the Sentry organization to which this monitor will belong.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

Optional. **`[DEPRECATED]`** The display name for the new team. If not supplied, it's auto-generated from the `slug` (if `slug` is provided). At least one of `name` or `slug` is required to create a team.

Optional. A unique, URL-friendly identifier for the new team. If not supplied, it's auto-generated from the `name` (if `name` is provided). Must adhere to the pattern: `^[a-z][a-z0-9_\-]*$`.

The unique identifier (ID) or human-readable slug of the Sentry organization where the new team will be created. This organization must already exist.

A dictionary containing the attributes and details of the newly created Sentry team.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

An optional descriptive name for the client key. If not provided, Sentry will generate a default name.

The maximum number of events that can be accepted for this key within the specified `rateLimit_window`. If omitted, Sentry's default rate limits will apply.

The time window in seconds for the `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, Sentry's default rate limits will apply.

The unique identifier (ID) or human-readable slug for the Sentry project for which the client key will be created.

The unique identifier (ID) or human-readable slug for the Sentry organization to which the project belongs.

A dictionary containing the details of the newly created project key, typically including its DSN, public key, secret key, name, and rate limit configuration if specified.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

Descriptive name for the alert rule.

Owner ID (e.g., 'team:ID', 'user:ID').

List of action objects executed when conditions (and filters) are met. Each object must specify an ID (action type) and parameters. See examples for required JSON structures: **Send a notification to Suggested Assignees** - `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 service** - `service` - The plugin slug. json { "id": "sentry.rules.actions.notify_event_service.NotifyEventServiceAction", "service": "mail" } **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" }

Optional list of filter objects for additional criteria after conditions are met. Each object must specify an ID (filter type) and parameters. See examples for required JSON structures: **The issue is `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 `attribute` value `match` `value`** - `attribute` - Valid values are `message`, `platform`, `environment`, `type`, `error.handled`, `error.unhandled`, `error.main_thread`, `exception.type`, `exception.value`, `user.id`, `user.email`, `user.username`, `user.ip_address`, `http.method`, `http.url`, `http.status_code`, `sdk.name`, `stacktrace.code`, `stacktrace.module`, `stacktrace.filename`, `stacktrace.abs_path`, `stacktrace.package`, `unreal.crashtype`, and `app.in_foreground`. - `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.conditions.event_attribute.EventAttributeCondition", "attribute": "http.url", "match": "nc", "value": "localhost" } **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" }

Action performance interval in minutes (5-43200) once conditions are met.

List of condition objects defining rule triggers. Each object must specify an ID (condition type) and parameters. See examples for required JSON structures: **A new issue is created** json { "id": "sentry.rules.conditions.first_seen_event.FirstSeenEventCondition" } **The issue changes state from resolved to unresolved** json { "id": "sentry.rules.conditions.regression_event.RegressionEventCondition" } **The issue is seen more than `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" }

Logic for condition evaluation ('all', 'any', 'none') before proceeding to filters.

Sentry environment name for event filtering (e.g., 'production'). If omitted, applies to all environments.

Logic for filter evaluation ('all', 'any', 'none') for action execution. Required if 'filters' are specified.

Unique identifier (ID or slug) of the Sentry project for the rule.

Unique identifier (ID or slug) of the Sentry organization.

Full details of the successfully created alert rule.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The fully qualified URL to which Sentry will send webhook POST requests for the subscribed events.

A list of event types to subscribe to for this webhook. When any of these events occur in the project, Sentry will send a notification to the specified URL.

The unique identifier (ID) or human-readable slug of the Sentry project for which to create the webhook.

The unique identifier (ID) or human-readable slug of the Sentry organization to which the project belongs.

A dictionary containing the details of the newly created webhook subscription.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

An optional URL that provides a link to the deployment, such as a commit or a CI build page.

An optional human-readable name for the deploy.

The version identifier of the release to be deployed. This version must already exist in Sentry.

An optional list of project slugs to associate this deploy with. If not provided, the deploy applies to all projects associated with the release.

An optional ISO 8601 formatted date-time string (UTC is recommended) indicating when the deployment process started.

The name of the environment to which this release is being deployed (e.g., 'production', 'staging'). This environment must be known to Sentry.

An optional ISO 8601 formatted date-time string (UTC is recommended) indicating when the deployment process finished. If not provided, Sentry uses the time the deploy API call is received.

The unique identifier (ID) or human-readable slug of the Sentry organization.

A dictionary representing the newly created deploy object. This includes details such as the deploy ID, environment, version, associated projects, start and finish dates, and any other relevant attributes recorded by Sentry.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

An optional commit reference, such as a branch name or a tag. This is useful if a tagged version has been provided (e.g., `version` is 'v1.0.0' and `ref` is 'refs/tags/v1.0.0').

An optional URL that points to the release. This can be a link to a GitHub release, a CI build page, or an internal changelog.

An optional way to indicate the start and end commits for each repository included in a release. Head commits must include `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`.

An optional list of commit data to be associated with the release. Commits must include the `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.

A unique identifier for this release. Can be a semantic version number, a commit hash, or any other string that uniquely identifies this release.

A list of project slugs that are part of this release. These projects must belong to the specified organization.

An optional ISO 8601 timestamp indicating when the release went live. If not provided, the current time is assumed by Sentry.

The ID or slug of the Sentry organization.

A dictionary containing the details of the newly created Sentry release.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

Human-readable name for the new team.

The unique identifier (ID) or slug of the Sentry organization where the new team will be created.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

UUID of the Sentry App installation, used to associate the external issue with the correct Sentry instance.

URL of the external issue in the third-party service; should be a direct link.

ID of the Sentry issue to link to the external issue.

Identifier for the project in the external service (not the Sentry project ID), e.g., JIRA project key, GitHub repository name.

Unique identifier for the external issue within the third-party service (e.g., JIRA issue key, GitHub issue number).

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

Display name for the new Sentry project.

Optional unique identifier for the project (e.g., for URLs), auto-generated from the name if omitted. Pattern: `^[a-z][a-z0-9_\-]*$`.

Primary platform or language (e.g., python, javascript, java) for SDK setup instructions and issue processing.

Specifies whether to create default alert rules. If true (API default when parameter is omitted), an alert is triggered for every new issue. If false, no default alerts are created.

ID or slug of the Sentry team to associate with the project.

ID or slug of the Sentry organization where the project will be created.

Full details of the newly created Sentry project.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

User's email address, used as the SAML identifier for the new member.

Organization role for the new member; defaults to the organization's default role. The `admin` role cannot be assigned in Business/Enterprise plans; use `TeamRoles` instead.

The ID or slug of the Sentry organization.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The unique identifier of the Debug Information File (DIF) to be deleted. This ID is assigned by Sentry when the file is uploaded.

The unique identifier (ID or slug) of the Sentry project from which the Debug Information File (DIF) will be deleted.

The unique identifier (ID or slug) of the Sentry organization to which the project belongs. Slugs are short, URL-friendly names.

A dictionary containing the API response. If the deletion is successful, this dictionary might be empty or contain a success message. In case of an error, it will typically include details about the error.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

Unique identifier (UUID) of the Sentry app installation.

Platform-specific identifier of the external issue to be unlinked.

Response data from the delete operation. Typically an empty dictionary for successful deletions that return a 204 No Content status.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

Unique identifier (ID or slug) of the Sentry team.

Numeric ID of the external team integration, typically obtained when the link was established.

Unique identifier (ID or slug) of the Sentry organization.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

Unique numerical identifier of the external user, typically obtained when the association was initially established with Sentry.

ID or human-readable slug of the Sentry organization.

Deletion operation result; may be an empty object or minimal API confirmation for success.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

Identifier (ID) of the organization member to remove from the team (e.g., '234567'). Typically a numerical ID.

Identifier (ID) or slug of the Sentry team from which the member will be removed (e.g., 'frontend-developers', '98765'). Team slugs are typically lowercase and hyphenated.

Identifier (ID) or slug of the Sentry organization (e.g., 'our-company', '123456'). Slugs are typically lowercase and hyphenated.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The unique numerical identifier (ID) of the metric alert rule to be deleted.

The unique identifier (ID) or human-readable slug of the Sentry organization to which the alert rule belongs. This specifies the scope of the deletion operation.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

Numerical ID of the dashboard to delete.

Identifier (ID) or human-readable slug of the Sentry organization.

API response data; typically empty for a successful deletion (HTTP 204 No Content).

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The unique integer identifier of the saved Discover query that you intend to delete.

The unique identifier (ID) or human-readable slug of the Sentry organization to which the Discover query belongs.

An empty dictionary is usually returned on successful deletion. May contain error details if the operation fails.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The unique identifier (ID) of the integration that is installed on the organization and is to be deleted.

The unique identifier (ID) or human-readable slug of the Sentry organization from which the integration will be deleted.

Data concerning the deletion's outcome; typically empty for successful operations (which often return HTTP 204 No Content).

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The unique identifier (ID) of the Sentry issue to be permanently deleted.

The unique identifier (ID) or human-readable slug of the Sentry organization to which the issue belongs.

A dictionary containing the response from the Sentry API. Upon successful deletion, this is typically an empty object or contains minimal confirmation data, as the HTTP status code indicates success (e.g., 202 Accepted or 204 No Content).

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The unique identifier (ID) of the member to be removed from the organization.

The unique identifier (ID) or the human-readable slug of the Sentry organization from which the member will be removed.

Typically empty upon successful deletion (204 No Content); may contain data in non-standard responses or with additional API wrapper context.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

Optional list of environment names to delete; if omitted, the entire monitor (including all its environments) is deleted.

The ID or slug of the Sentry cron monitor to be deleted.

The ID or slug of the Sentry organization to which the monitor belongs.

A dictionary that is typically empty on a successful synchronous deletion (e.g., HTTP 204 No Content). For asynchronous deletions (e.g., HTTP 202 Accepted), it might contain details about the deletion task.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The version identifier of the release to be deleted. This could be a semantic version (e.g., '1.0.0', 'my-app@2.3.1') or a unique commit hash.

The unique identifier (ID) or human-readable slug of the Sentry organization to which the release belongs.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The unique numerical identifier (ID) of the notification action to be deleted.

The unique identifier (ID) or human-readable slug of the Sentry organization.

A dictionary that is typically empty upon successful deletion (HTTP 204 No Content). It may contain additional information in other response scenarios.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The unique identifier (ID) or URL-friendly slug of the Sentry project to be deleted.

The unique identifier (ID) or URL-friendly slug of the Sentry organization to which the project belongs.

Dictionary for operation details or error messages. For successful asynchronous 204 No Content deletions, this is typically empty as no body is returned.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The unique identifier (GUID) of the service hook to be deleted from the specified project.

The unique identifier (ID) or human-readable slug of the Sentry project from which the service hook will be removed.

The unique identifier (ID) or human-readable slug of the Sentry organization to which the project and service hook belong.

A dictionary that may contain additional information regarding the deletion. For successful deletions (e.g., HTTP 204 No Content), this is often an empty dictionary.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

A list of specific issue IDs to be permanently removed. If not provided, the action removes the oldest 1000 issues in the project.

The unique identifier (ID or slug) of the Sentry project from which issues will be removed.

The unique identifier (ID or slug) of the Sentry organization to which the project and its issues belong.

A dictionary containing the API response. This is typically empty (e.g., following an HTTP 204 No Content status) on successful removal, or may contain error details if the operation fails.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The ID of the client key (public DSN key) to delete.

The ID or slug of the project to which the client key belongs.

The ID or slug of the organization to which the project belongs.

Response data from Sentry. Typically an empty dictionary for successful deletion.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

Optional. A list of environment names. If provided, only the monitor configurations for these specific environments will be deleted. If this parameter is omitted or an empty list is passed, the entire monitor and all its environment configurations will be deleted.

The unique identifier (ID or slug) of the Sentry monitor to be deleted.

The unique identifier (ID or slug) of the Sentry project to which the monitor belongs.

The unique identifier (ID or slug) of the Sentry organization to which the project and monitor belong.

A dictionary that may contain additional details about the deletion. Usually empty for successful monitor deletions.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The unique identifier (ID) of the session replay to be deleted.

The unique identifier (ID) or human-readable slug for the Sentry project from which the replay will be deleted.

The unique identifier (ID) or human-readable slug for the Sentry organization to which the project and replay belong.

Usually empty upon successful deletion; may contain confirmation details or error information.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The numerical ID of the specific issue alert rule that needs to be deleted from the project.

The unique identifier (ID or slug) of the Sentry project from which the alert rule will be deleted. Slugs are typically lowercase and hyphenated (e.g., 'my-web-project').

The unique identifier (ID or slug) of the Sentry organization that contains the project and the alert rule to be deleted. Slugs are typically lowercase and hyphenated (e.g., 'my-sentry-org').

A dictionary that is typically empty upon successful deletion. It might contain additional details or a success confirmation in some cases.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The unique identifier of the symbol source to be deleted. This is usually a UUID. Example: 'a1b2c3d4-e5f6-7890-1234-567890abcdef'.

The ID or slug of the project from which the symbol source will be deleted. Examples: 'my-project', '67890'.

The ID or slug of the organization to which the project belongs. Examples: 'my-org', '12345'.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The unique identifier (ID) or human-readable slug of the Sentry team to be disassociated from the project.

The unique identifier (ID) or human-readable slug of the Sentry project.

The unique identifier (ID) or human-readable slug of the Sentry organization.

The response payload. For a successful deletion, this is typically an empty dictionary. In case of an error, it may contain details about the failure.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

Identifier of the file to be deleted.

Version identifier of the release.

Identifier (ID or slug) of the release's project.

Identifier (ID or slug) of the release's organization.

An empty dictionary is expected upon successful deletion of the release file, as the API typically returns a 204 No Content status.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The unique identifier of the specific file to be deleted from the release. This often corresponds to the file's name or path as Sentry knows it.

The version identifier of the release from which the file will be deleted. This can be a semantic version, a commit hash, or any unique string identifying the release.

The unique identifier (ID or slug) of the Sentry organization to which the release belongs.

A dictionary that may contain data related to the deletion operation. For a successful synchronous deletion (HTTP 204 No Content), this is usually an empty dictionary.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The unique identifier (ID) or URL-friendly slug of the Sentry team targeted for deletion. For example, 'frontend-devs' or '67890'.

The unique identifier (ID) or URL-friendly slug of the Sentry organization to which the team belongs. For example, 'acme-corp' or '12345'.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The unique numerical ID of the team to be deleted.

The ID or URL-friendly slug of the Sentry organization from which the team will be deleted.

A dictionary containing data from the SCIM API response. For successful deletion, this may be empty or contain a minimal confirmation.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

Unique identifier of the Sentry user.

API response data; often an empty dictionary or minimal confirmation upon successful deletion.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The unique identifier of the organization member to remove.

The identifier or slug of the Sentry organization.

Data from the Sentry API response; usually empty for successful SCIM DELETE operations.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

Specifies the event to retrieve: 'latest', 'oldest', or 'recommended'.

The unique numerical ID of the Sentry issue for which to fetch an event.

Filter by environment names; if omitted, events from all environments are considered.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The unique identifier (ID) or human-readable slug of the Sentry organization for which alert rules are to be fetched. Slugs are typically the organization's name in lowercase, using hyphens for spaces (e.g., 'acme-corp').

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The inclusive end of the time series range for querying release threshold statuses. Accepts UTC ISO8601 format (e.g., '2023-01-01T23:59:59Z') or epoch seconds (e.g., '1672617599').

The start of the time series range for querying release threshold statuses. Accepts UTC ISO8601 format (e.g., '2023-01-01T00:00:00Z') or epoch seconds (e.g., '1672531200').

A list of release versions (e.g., '1.0.0', 'my-app@2.1.3') to filter the release threshold statuses by. If not provided, statuses for all releases within the time range are considered.

A list of environment names (e.g., 'production', 'staging') to filter the release threshold statuses by. If not provided, statuses for all environments are considered.

A list of project slugs (e.g., 'frontend', 'backend-api') to filter the release threshold statuses by. If not provided, statuses for all projects in the organization are considered.

The ID or slug of the Sentry organization for which to fetch release threshold statuses.

A dictionary where keys are in the format `{release_version}-{project_slug}`. Each value contains a list of enriched release thresholds, including their derived health statuses and the full serialized `release_threshold` instance.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The end timestamp for the query period, in ISO-8601 format (e.g., `2001-12-14T12:34:56.7890Z`).

A Sentry search query string to further filter replays. Example: `(transaction:foo AND release:abc) OR (transaction:[bar,baz] AND release:def)`. Refer to Sentry documentation for detailed query syntax.

The start timestamp for the query period, in ISO-8601 format (e.g., `2001-12-14T12:34:56.7890Z`).

A list of project IDs to filter results by. Use `[-1]` to include all available projects within the organization.

A list of environment names to filter results by (e.g., production, staging).

A relative time period for the query, which overrides `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.

The unique identifier (ID or slug) of the Sentry organization.

A dictionary containing the replay count data based on the provided query filters.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

Inclusive end of the time series range (UTC ISO8601 or epoch seconds). Use with `start`; alternative to `statsPeriod`.

Field to sort replay details by (prefix with '-' for descending, e.g., '-started_at').

Specific fields to include in the response (e.g., 'activity', 'browser'). See `FieldEnm` for valid fields.

Structured query string to filter replay details (e.g., `user.email:test@example.com`, `has:error`).

Start of the time series range (UTC ISO8601 or epoch seconds). Use with `end`; alternative to `statsPeriod`.

Pagination cursor for fetching the next or previous set of results.

List of project IDs to filter replay details by.

Maximum number of items to return per page for pagination.

ID of the specific replay session to retrieve.

Environment (e.g., 'production', 'staging') to filter replay details by.

Time range for series data, relative to now (e.g., `1d`, `2h`). Use if not providing `start` and `end`.

ID or slug of the Sentry organization for the replay.

Detailed information of the fetched replay, structured by requested fields.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

End of time range (UTC ISO8601 or epoch seconds). Use with `start`; not with `statsPeriod`.

Field to sort replay selectors by. Refer to Sentry API docs for available fields.

Sentry search query syntax for filtering. See Sentry docs for syntax/fields.

Start of time range (UTC ISO8601 or epoch seconds). Use with `end`; not with `statsPeriod`.

Pagination cursor for fetching next/previous page.

Filter by project IDs.

Maximum items per page (API defaults to 100 if not specified, max 100).

Filter by environment names.

Time range (e.g., `1d`, `2h`; m, h, d, w units). Use instead of `start`/`end`.

ID or slug of the Sentry organization.

Fetched replay selectors and related Sentry API data/metadata.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The name of the environment (e.g., production, staging, development).

The ID or slug of the Sentry project.

The ID or slug of the Sentry organization.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The unique identifier (ID) or human-readable slug of the Sentry project for which ownership details are to be retrieved. This is used as a path parameter in the API request.

The unique identifier (ID) or human-readable slug of the Sentry organization to which the project belongs. This is used as a path parameter in the API request.

A dictionary containing the project's ownership configuration. This typically includes rules defining ownership based on paths or other criteria.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The version identifier of the release (e.g., '1.0.0', 'my-app@2.3.12').

The unique identifier (ID) or human-readable slug of the project.

The unique identifier (ID) or human-readable slug of the organization.

A dictionary representing the list of files for the given release. Each key is a file identifier, and the value contains file metadata such as 'id', 'name', 'sha1', 'size', 'dateCreated', 'headers', and 'dist'.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

Sentry search query to filter click events (e.g., `(transaction:foo AND release:abc) OR (transaction:[bar,baz] AND release:def)`).

Pagination cursor to navigate through click events.

Maximum number of click events per page (default/max 100).

The ID of the Sentry session replay.

List of environment names to filter click data.

The ID or slug of the Sentry project.

The ID or slug of the Sentry organization.

Response data containing a list of click events, each typically including `clickId`, `nodeId`, `timestamp`, and DOM node information.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The unique identifier of the replay to retrieve. This is a 32-character hexadecimal string (UUID4) without dashes. Example: "a6ef355da2bb43f8a7825c45f98c5177".

The ID of the specific recording segment within the replay to retrieve. This is an integer. Example: 0.

The ID or slug of the project to which the replay belongs. Examples: 'javascript', 'my-project'.

The ID or slug of the organization to which the replay belongs. Examples: 'sentry', 'my-org'.

A dictionary containing the replay recording segment data.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The numeric identifier of the metric alert rule whose activations are to be retrieved.

The unique identifier (ID) or slug of the Sentry organization to which the alert rule belongs.

The API response payload. This field is expected to contain or represent the list of activations for the specified alert rule. Each activation typically includes details such as its unique identifier and the `date_added` timestamp indicating when the alert was triggered.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The unique ID of the integration installed for the specified organization (e.g., 'github').

The Sentry organization's unique ID or human-readable slug (e.g., 'the-acme-corp').

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

Specify `"0"` to exclude project and team details for a more concise organization summary; otherwise, these details are included.

The unique identifier (ID) or human-readable slug of the Sentry organization.

A dictionary containing the details of the retrieved organization.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

Set to `true` to list only organizations where the authenticated user is an owner.

Filter results using Sentry's query syntax. Supported fields: `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).

Opaque cursor for pagination to retrieve next/previous result sets.

Sort results by 'members' (number of members), 'projects' (number of projects), or 'events' (number of events in past 24h), in descending order. Defaults to creation date.

Contains the list of organizations matching the query criteria, along with their respective details.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

Filters environments by visibility: 'all' (includes hidden), 'hidden', or 'visible'. Defaults to 'visible' if not provided.

ID or slug of the Sentry organization.

Raw Sentry API response, typically a list of environment objects, each describing an environment with its 'id' and 'name'.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The unique identifier (ID) of the issue for which details are to be retrieved.

The unique identifier (ID) or URL-friendly slug of the Sentry organization to which the issue belongs.

A dictionary containing the detailed information of the issue. This typically includes attributes such as title, first seen and last seen timestamps, number of comments, user reports, and summarized event data.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

A list of environment names to filter the monitor details by. If omitted, details for all environments are considered.

The unique identifier (ID) or human-readable slug of the monitor whose details are to be retrieved.

The unique identifier (ID) or human-readable slug of the organization to which the monitor belongs.

A dictionary containing the detailed attributes and configuration of the monitor.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

Sorting order for data within release details (e.g., environments by adoption).

Filter data for this release using Sentry's search syntax (e.g., to find specific events). See Sentry documentation for syntax. Example from Sentry: `'''(transaction:foo AND release:abc) OR (transaction:[bar,baz] AND release:def)'''`

Include health data (e.g., crash rates, session statistics) with release details.

Filter release details by status ('open' or 'archived').

The unique version identifier of the release. This can be a semantic version (e.g., '1.2.3'), a commit hash, or any string used to identify the release (e.g., 'backend@1.0.0-alpha').

ID of a specific project to scope release details; if omitted, details may cover multiple projects.

Include information about the release's adoption stages.

Time window for health statistics, used if 'health' is true.

Time window for summary statistics.

The unique identifier (ID) or human-readable slug of the Sentry organization.

A dictionary containing the detailed information for the specified release version. The structure of this dictionary can vary based on the data available for the release and the query parameters used (e.g., inclusion of health data).

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

End of the query period (ISO-8601 format). Ignored if `statsPeriod` is provided.

Fields for session statistics (e.g., `sum(session)`, `count_unique(user)`, `p99(session.duration)`, `crash_free_rate(user)`). Session duration aggregations may be incomplete for data after Jan 12, 2023.

Sentry search query to filter sessions (e.g., `(transaction:foo AND release:abc)`). See Sentry docs for syntax.

Start of the query period (ISO-8601 format). Ignored if `statsPeriod` is provided.

Properties to group session data by (e.g., `project`, `release`, `environment`, `session.status`).

Field from `field` parameter to order results by. Prefix with '-' for descending (e.g., `-sum(session)`).

Project IDs to filter sessions by. Use `[-1]` for all accessible projects.

Time series data resolution (e.g., '1h', '1d'; format like `statsPeriod`). Minimum '1h', maximum '1d'. Must cleanly divide one day.

Maximum number of groups (aggregated data points based on `groupBy`) per request.

Environment names to filter sessions by (e.g., 'production', 'staging').

Relative query period (e.g., '24h', '7d'), overrides `start` and `end`. Uses 'd' (days), 'h' (hours), 'm' (minutes), 's' (seconds), or 'w' (weeks).

Set to `0` to exclude, `1` (API default) to include time series data.

Set to `0` to exclude, `1` (API default) to include totals.

Unique ID or human-readable slug of the Sentry organization.

Retrieved session statistics, including groups, series, and totals, structured based on request parameters.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

Inclusive end of the time series range (UTC ISO8601 datetime string or Unix timestamp). Use with `start` instead of `statsPeriod`.

Aggregation field for event counts. Interpretation depends on event type: `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.

Start of the time series range (UTC ISO8601 datetime string or Unix timestamp). Use with `end` instead of `statsPeriod`.

Reason an event was filtered or dropped (e.g., `project_quota`, `invalid_origin`).

Filter by event outcome status (e.g., accepted, filtered, rate-limited).

List of project IDs (strings or integers) to filter by. Omit or use empty list for all projects.

Filter by event category. If 'attachment', other categories cannot be included. If 'error', `default` and `security` are also included.

If true, triggers a CSV download of the response; otherwise JSON.

Time series resolution (e.g., `1h`). Default is `1h`. Minimum `1h`. Intervals must cleanly divide one day and cannot exceed `1d`.

Relative time series range (e.g., `1d`, `2h`). Units: `m`, `h`, `d`, `w`. Use instead of `start` and `end`.

The ID or slug of the Sentry organization.

Summarized statistics, typically including start/end times, aggregated data (by project or totals), and counts based on request filters.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

If `True`, retrieves full event details including stacktraces; otherwise, a summary is returned.

Opaque cursor for pagination, pointing to the start of the next/previous page, typically from a 'Link' header.

If `True`, returns events in a pseudo-random yet deterministic order.

The ID or slug of the Sentry project.

The ID or slug of the Sentry organization.

Sentry API response containing the list of project events; structure depends on the 'full' parameter and Sentry's API.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

Specifies the type of event statistic to query.

UNIX timestamp (seconds since epoch) for the start of the query period.

UNIX timestamp (seconds since epoch) for the end of the query period.

Time resolution for the statistics.

The unique identifier (ID) or human-readable slug of the project.

The unique identifier (ID) or human-readable slug of the organization.

Queried event statistics, typically a series of [timestamp, count] pairs.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The unique identifier (GUID) of the service hook to be retrieved. This ID is assigned when the hook is created.

The unique identifier (ID) or URL-friendly slug of the Sentry project to which the service hook is bound.

The unique identifier (ID) or URL-friendly slug of the Sentry organization to which the project and its service hook belong.

A dictionary containing the detailed information of the retrieved service hook. This includes its configuration, events it listens to, and other relevant attributes.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

Opaque cursor for paginating through project lists, typically obtained from pagination details in a previous API response.

Dictionary from Sentry containing the list of projects; refer to Sentry's 'List Your Projects' API documentation for schema details.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

ID or slug of the Sentry cron monitor.

ID or slug of the Sentry project.

ID or slug of the Sentry organization.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

ID of the alert rule.

ID or slug of the Sentry project.

ID or slug of the Sentry organization.

Detailed attributes and configuration of the alert rule.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The unique numeric identifier of the Sentry team whose SCIM group information is to be retrieved.

The slug (human-readable identifier) or numeric ID of the Sentry organization to which the team belongs.

SCIM representation of the Sentry team, including attributes and members, conforming to the SCIM Group schema.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The ID or slug of the organization.

A dictionary containing the list of Sentry App installations for the specified organization.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

A pagination cursor used to fetch the next or previous set of results. Obtain this from the 'Link' header of the previous response.

The ID or slug of the Sentry team.

The ID or slug of the Sentry organization.

A list of team members. The structure of each member object is not explicitly detailed but typically includes user information.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The unique identifier of the session replay. This is a 32-character hexadecimal string (UUIDv4 format without dashes).

The unique identifier (ID) or human-readable slug of the Sentry project.

The unique identifier (ID) or human-readable slug of the Sentry organization.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

Opaque cursor for pagination, used to retrieve the next or previous page of dashboards. Obtain from the 'Link' header or pagination metadata of a previous API response.

Maximum number of dashboard records per page. Defaults to Sentry's setting (often 50) if unspecified. Max: 100.

The unique identifier (ID) or human-readable slug of the Sentry organization whose dashboards are to be listed.

Dictionary with the API response, including the list of custom dashboards for the organization and any applicable pagination information.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The unique identifier (ID) or human-readable slug of the Sentry organization.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

An optional string to filter releases. The filter performs a "starts with" match on the release version. For example, "1.0" would match "1.0.1" and "1.0-beta", while "backend-" would match "backend-v2.1". If omitted, all releases are returned.

The unique identifier (ID) or human-readable slug of the Sentry organization whose releases are to be listed.

Raw Sentry API response, typically a JSON array of release objects from the '/api/0/organizations/{organization_id_or_slug}/releases/' endpoint.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The unique identifier (ID or slug) of the Sentry organization for which to list repositories. The slug is the URL-friendly name of the organization.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

Identifier (ID) or slug of the Sentry organization.

List of team objects, each detailing a team the user is a member of in the specified organization.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

An optional query string to filter the list of users. Use prefixes like `id:`, `email:`, `username:`, or `ip:` to target specific fields. For example, `email:foo@example.com` or `username:john.doe`.

The unique identifier (ID) or human-readable slug for the Sentry project.

The unique identifier (ID) or human-readable slug for the Sentry organization.

List of Sentry user objects, each detailing a user (e.g., `id`, `username`, `email`). Note: Sentry API might structure this as a dictionary.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

Maximum number of user records per response (max 100).

SCIM filter expression to narrow down users (e.g., `userName eq "user@example.com"`). Only `eq` operator is supported.

The 1-based starting index for pagination.

Attribute names to exclude from user objects; only `members` is currently supported for exclusion.

The organization's unique identifier (ID) or human-readable slug.

Paginated list of SCIM users matching the query, structured per SCIM User Resource Properties schema.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

Pagination cursor for retrieving the next or previous page of results.

If '1', includes project details for each team. If '0' or not provided, excludes project details.

The ID or slug of the Sentry organization.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The third-party provider of the external team or channel.

Optional ID of a user within the external provider (e.g., Slack user ID).

Name of the external team or channel to link (e.g., #engineering, @dev-team).

Sentry ID for the integration with the specified provider (e.g., a specific Slack workspace or GitHub organization).

The ID or slug of the Sentry team to link.

The ID or slug of the Sentry organization where the team resides.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The new name for the monitor; used in notifications and helps identify the monitor in the Sentry UI.

A new unique slug for the monitor within the organization (pattern: `^[a-z][a-z0-9_\-]*$`). Changing this slug requires updating any instrumented check-in calls for this monitor. Omit to leave current slug unchanged.

The type of the monitor; must be 'cron_job', indicating a recurring task.

The new owner of the monitor, specified as a team or user ID (e.g., 'user:USER_ID' or 'team:TEAM_ID'). Omit to leave current owner unchanged.

The new status for the monitor. 'active' monitors accept events and count towards the quota; 'disabled' monitors do not accept events and are excluded from the quota.

Set to `true` to prevent this monitor from creating incidents (alerts), or `false` to allow them. Omit to leave current muted status unchanged.

ID or slug of the Sentry monitor to be updated.

ID or slug of the Sentry organization to which the monitor belongs.

A dictionary containing the full representation of the updated monitor.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

A list of project slugs for which this notification action will be active, applying only to these projects if provided. An empty list's interpretation (e.g., no projects or all projects) may vary.

The unique numerical ID of the specific notification action to be modified.

The service through which the notification will be sent. Supported services are: `email`, `slack`, `sentry_notification`, `pagerduty`, `opsgenie`.

Specifies the type of event that triggers the notification. Currently, the only supported value is `spike-protection`.

The ID of the integration for the notification service, required if `service_type` is `slack`, `pagerduty`, or `opsgenie`.

A human-readable name for the notification target (e.g., a Slack channel name like '#critical-alerts' or an Opsgenie team name). This is required if `service_type` is `slack` or `opsgenie`.

The unique identifier of the notification target within the chosen service (e.g., a Slack channel ID like 'C012AB3CD' or an Opsgenie team ID). This is required if `service_type` is `slack` or `opsgenie`.

The unique identifier (ID) or human-readable slug of the Sentry organization to which this notification action belongs.

A dictionary containing the details of the modified notification action.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

A new name for the organization.

A new unique slug for the organization, used in URLs.

Base64 encoded image for the organization avatar; required if `avatarType` is 'upload'.

Type of organization avatar: 'letter_avatar' (initials) or 'upload' (custom image).

Enforce two-factor authentication (2FA) for all members.

List of global field names exempt from data scrubbing, ensuring their values are preserved.

Default role for new members when they join the organization.

Allow Sentry to comment on recent GitHub PRs suspected of introducing new issues. Requires GitHub integration.

Enforce server-side data scrubbing for all projects based on defined rules.

Enable Code Coverage Insights (Team plan or higher).

List of local Relay configurations. Each is a dict with `name`, `publicKey`, `description`. Business/Enterprise plans. Warning: Overwrites existing configurations.

Cancel a pending deletion and restore the organization.

Minimum role to download debug files (e.g., ProGuard mappings, source maps).

Hide AI-powered features in the Sentry UI for this organization.

Opt the organization into new Sentry features before public release.

Allow members to freely join any team without invitation or approval.

JSON string defining advanced, project-specific data scrubbing rules. Applies to new events and overwrites existing advanced configuration. Warning: Updating this field overwrites all existing advanced rules.

Minimum role to download event attachments (e.g., crash reports, logs).

Activate enhanced privacy controls, limiting PII and source code display (e.g., in notifications).

Allow Sentry to comment on open GitHub PRs with related error issues. Requires GitHub integration.

List of global field names whose values will be scrubbed from event data across all projects.

Allow Sentry to fetch missing JavaScript source context from public URLs if source maps are incomplete.

Prevent storage of IP addresses for new events in this organization.

Grant members `alerts:write` scope for alert rule management.

Allow users to request to join the organization; admins approve/deny.

Enable sharing limited issue details with anonymous users (e.g., via public links).

Grant members `event:admin` scope to delete events.

Enable Sentry to detect GitHub committers not in Sentry org and suggest inviting them. Requires GitHub integration.

Number of native crash reports (e.g., Minidumps) to store per issue (0=Disabled, -1=Unlimited).

Apply Sentry's default scrubbing rules (e.g., for passwords, credit cards) to event data for all projects.

Configure Sentry Slack integration to post Issue Alert replies in threads. Requires Slack integration.

Configure Sentry Slack integration to post Metric Alert replies in threads. Requires Slack integration.

The ID or slug of the organization.

Dictionary containing the updated organization settings.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

New distribution name for the file, often a unique build or version code.

New name for the file, including its full path.

ID of the file to modify, typically a hash or unique identifier.

Version identifier of the release.

ID or slug of the organization.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The unique identifier of the Sentry team to be updated.

A list of SCIM patch operations to be applied to the team. Each operation specifies an action (e.g., add, remove, replace), a target path, and a value. Multiple operations can be provided to perform several updates in a single request.

The ID or slug of the Sentry organization to which the team belongs.

A dictionary containing the SCIM representation of the team after the PATCH operations have been applied.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The ID of the organization member to update.

A list of SCIM PATCH operations. For this action, must contain one operation setting the member's 'active' attribute to 'false', which deactivates and permanently deletes the member.

The ID or slug of the Sentry organization.

A dictionary containing the SCIM representation of the member after the update operation, if applicable. May be empty if the member is deleted and no content is returned.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

Optional unique identifier (auto-generated if omitted); must not start with `sentry:`.

Base URL for an HTTP symbol source. Required if `type` is `http`.

Human-readable name for the symbol source.

Type of the symbol source (e.g., `http`, `gcs`, `s3`), which determines required configuration fields.

Name of the Google Cloud Storage (GCS) or Amazon S3 bucket containing symbols. Required if `type` is `gcs` or `s3`.

Optional path prefix within the GCS or S3 bucket. Applicable if `type` is `gcs` or `s3`.

AWS region for the S3 bucket (e.g., `us-east-1`). Required if `type` is `s3`.

Password for HTTP basic authentication. Applicable if `type` is `http`.

Username for HTTP basic authentication. Applicable if `type` is `http`.

AWS Access Key ID for S3 authentication. Required if `type` is `s3`.

AWS Secret Access Key for S3 authentication. Required if `type` is `s3`.

Private key (PEM format) for GCS service account. Required if `type` is `gcs`.

Client email for GCS service account. Required if `type` is `gcs`.

Specifies the expected directory structure or layout for symbols.

Specifies the filename casing convention for symbols.

Identifier (ID or slug) of the Sentry project.

Identifier (ID or slug) of the Sentry organization.

Configuration of the newly created symbol source.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

List of project slugs to enable Spike Protection for; use `['$all']` for all projects in the organization.

Unique ID or slug of the Sentry organization.

Result of the spike protection enablement, detailing the status for affected projects.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The numeric ID of the alert rule.

The ID or slug of the Sentry organization.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The version identifier of the release. This can be a semantic version string (e.g., '1.0.0', 'my-project@2.3.4-beta'), a descriptive name (e.g., 'backend-deploy-2024-05-20'), or a commit SHA if used as the version string (e.g., 'abcdef123456').

The slug (e.g., `my-org-slug`) or numerical ID (e.g., `1234567`) of the Sentry organization to which the release belongs.

The API response, detailing files changed in the release's commits (often a list of file objects).

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The unique identifier of the repository.

The unique identifier or short name (slug) of the organization.

A list of commit objects. Each object typically includes fields like 'id', 'message', and 'dateCreated'.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The unique identifier (ID) or human-readable slug of the Sentry project.

The unique identifier (ID) or human-readable slug of the Sentry organization.

A dictionary containing the API's response, typically including a list of debug information files (dSYM files) with details such as ID, UUID, CPU name, object name, symbol type, size, and creation date.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The unique 32-character hexadecimal identifier of the Sentry event to be resolved.

The unique identifier (ID) or human-readable slug of the Sentry organization where the event occurred. This specifies the scope for the event lookup.

A dictionary containing the resolved event information. This includes the `projectSlug`, `groupID` (internal issue ID), and the `id` (internal event ID), along with other event attributes.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The specific version identifier of the release. This can be a commit hash (e.g., '4018a1c'), a semantic version (e.g., '1.0.0'), a custom release name (e.g., 'my-project@1.0.0'), or the literal string 'latest'.

The unique identifier (ID) or human-readable name (slug) of the Sentry organization.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The end timestamp for filtering events, in ISO-8601 format (e.g., `2001-12-14T12:34:56.7890Z`). If provided, `start` must also be specified. This parameter is overridden by `statsPeriod` if both are used.

If set to `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.

An optional Sentry search query string to further filter events. Uses Sentry's search syntax (e.g., 'level:error', 'user.ip:127.0.0.1', 'handled:no tag_name:tag_value').

The start timestamp for filtering events, in ISO-8601 format (e.g., `2001-12-14T12:34:56.7890Z`). If provided, `end` must also be specified. This parameter is overridden by `statsPeriod` if both are used.

If set to `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.

The unique numeric identifier of the Sentry issue for which to retrieve associated events.

A list of environment names (e.g., 'production', 'staging') to filter events by. Only events from these specified environments will be returned.

A relative time period for the query (e.g., '24h', '7d', '2w'), calculated from the current time. This overrides `start` and `end` if specified. Format is a number followed by 'd' (days), 'h' (hours), 'm' (minutes), 's' (seconds), or 'w' (weeks).

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

If `True`, includes comprehensive details for each hash; if `False`, returns a minimal representation.

Pagination cursor to navigate through the list of issue hashes.

Identifier (ID) of the Sentry issue.

Identifier (ID or slug) of the Sentry organization.

Dictionary containing the retrieved data about the issue's hashes, possibly including pagination metadata.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The specific tag key (e.g., 'browser', 'os', 'environment', 'release', custom tags) for which to retrieve detailed values; case-sensitive.

The unique numerical ID of the Sentry issue.

Optional list of environment names to filter tag values; if omitted, all environments are considered.

Details for the specified tag, including `key`, `name`, `uniqueValues`, `totalValues`, and `topValues` (list of most frequent values with `value`, `count`, `firstSeen`, and `lastSeen` timestamps).

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The unique identifier (ID) or URL-friendly slug of the Sentry monitor. This specifies the monitor for which check-ins are to be retrieved.

The unique identifier (ID) or URL-friendly slug of the Sentry project. This specifies the project to which the monitor belongs, within the given organization.

The unique identifier (ID) or URL-friendly slug of the Sentry organization. This specifies the organization to which the project and monitor belong.

A dictionary containing the list of check-in objects from the Sentry API, where the list might be under a specific key. Each check-in provides details like 'id', 'status', 'duration', 'environment', and 'dateCreated'.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The unique identifier (ID) or URL-friendly slug of the monitor.

The unique identifier (ID) or URL-friendly slug of the Sentry organization.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The unique numerical identifier (ID) of the specific notification action to retrieve.

The unique identifier (ID) or human-readable slug of the Sentry organization.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The unique numeric identifier (ID) of the custom dashboard to retrieve within the specified organization.

The unique identifier (ID) or human-readable slug of the Sentry organization.

A dictionary containing detailed information of the retrieved custom dashboard, such as 'id', 'title', 'dateCreated', 'widgets', and 'createdBy'.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The end timestamp for the query period, in ISO-8601 format (e.g., `2024-01-15T12:30:00Z`). This parameter is ignored if `statsPeriod` is provided.

The field by which to sort the query results. Prepend with `-` for descending order (e.g., `-timestamp`).

Specifies the fields, functions, or equations to include in the query results. Each item in the list can be: - A built-in key field (e.g., `transaction`). Refer to Sentry documentation for event property fields. - A tag, using `tag[tagName]` format to avoid ambiguity (e.g., `tag[isEnterprise]`). - A function, in `function_name(parameters,...)` format (e.g., `count_if(transaction.duration,greater,300)`). When a function is included, Discover will group results by any specified tags or fields. Refer to Sentry query builder documentation for available functions. - An equation, prefixed with `equation|` (e.g., `equation|count_if(transaction.duration,greater,300) / count() * 100`). Refer to Sentry documentation on query equations.

A Sentry search query string to filter events. Example: `(transaction:foo AND release:abc) OR (transaction:[bar,baz] AND release:def)`. Refer to Sentry documentation for detailed search syntax.

The start timestamp for the query period, in ISO-8601 format (e.g., `2024-01-01T10:00:00Z`). This parameter is ignored if `statsPeriod` is provided.

A list of project IDs to filter events by. Use `[-1]` to include all accessible projects. For example: `[123, 456]` or `[-1]`.

The maximum number of event rows to return. Defaults to 100, which is also the maximum allowed value.

A list of environment names to filter events by (e.g., `production`, `staging`).

The relative time period for the query (e.g., `24h`, `7d`, `30m`). This overrides `start` and `end` if provided. Valid suffixes: `d` (days), `h` (hours), `m` (minutes), `s` (seconds), `w` (weeks).

The ID or slug of the organization for which to retrieve events.

A dictionary containing the queried event data, structured according to the requested `field` parameters.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

Filters integrations by their supported features. Refer to Sentry's [Integrations Documentation](/product/integrations/) for an updated list of features. Examples include: `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`.

Filters integrations by a specific provider key. Refer to Sentry's [Integrations Documentation](/product/integrations/) for an updated list of providers.

If `True`, fetches detailed third-party configurations for each integration; this may significantly increase response time.

The unique identifier (ID) or human-readable slug of the Sentry organization.

A dictionary containing a list of integration objects available to the organization, matching query criteria. Refer to the Sentry API documentation for the exact structure.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The unique identifier (ID) of the organization member whose details are to be retrieved.

The unique identifier (ID) or URL-friendly slug of the Sentry organization.

A dictionary containing the organization member's details, such as role, teams, status, and other attributes.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

Filter by owner, using `user:<user_id>` or `team:<team_id>` format.

List of project IDs to filter by; use `[-1]` for all accessible projects.

List of environment names (e.g., 'production', 'staging') to filter by.

The ID or slug of the Sentry organization.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

Pagination cursor pointing to the next or previous set of results. If omitted, the first page is returned. Typically obtained from a previous response's 'Link' header.

The ID or slug of the Sentry organization.

Raw Sentry API response as a dictionary, containing the organization's project data and any relevant pagination information.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The unique identifier (ID) or human-readable slug for the Sentry organization. This specifies which organization's relay usage data to retrieve.

A dictionary containing details of the organization's Relay usage. This typically includes a list of trusted relays and potentially other usage statistics or configurations.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The version identifier of the release. This can be a version number, package name with version, or a commit hash.

The unique identifier (ID) or human-readable slug of the Sentry organization to which the release belongs.

A dictionary containing the list of commits associated with the specified release. The structure of the commit data can vary.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

Absolute inclusive end of the time series range (UTC ISO8601 or epoch seconds). Requires `start`. Conflicts with `statsPeriod`.

The field to sort the replays by. Prefix with '-' for descending order (e.g., '-started_at'). Default is 'activity'.

Additional fields to include in the response for each replay; invalid fields are ignored.

Structured query string to filter replays (e.g., 'user.email:"j.doe@example.com" AND browser.name:"Chrome"'). Refer to Sentry documentation for syntax.

Absolute start of the time series range (UTC ISO8601 or epoch seconds). Requires `end`. Conflicts with `statsPeriod`.

Pagination cursor for fetching next/previous page. See Sentry API documentation for details.

A list of project IDs to filter replays by. Use -1 for all projects.

The maximum number of replays to return per page. The default is 50, and the maximum is 100.

The environment name to filter replays by (e.g., 'production', 'staging').

The relative time range for the query (e.g., `1d` for one day). Units: `m` (minutes), `h` (hours), `d` (days), `w` (weeks).

The ID or slug of the Sentry organization.

A dictionary containing the list of replays and related metadata.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The maximum number of SCIM groups to return per page. The API enforces a maximum limit of 100.

A SCIM filter expression to narrow down the list of groups. Currently, only the `eq` (equals) operator is supported, e.g., `displayName eq "Engineering Team"`.

The 1-based index for pagination, indicating the starting point of the results to retrieve. Follows SCIM standards.

A list of attribute names to exclude from the response for each group. Currently, the only supported value for an attribute to exclude is `members`.

The unique identifier (ID) or human-readable slug of the Sentry organization for which to retrieve SCIM groups.

A dictionary containing the SCIM ListResponse. This includes a `Resources` key with a list of group objects, `totalResults`, `itemsPerPage`, `startIndex`, and other SCIM-standard fields.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

Inclusive end timestamp for the time series (ISO 8601 UTC or Unix epoch seconds). Use with `start`; alternative to `statsPeriod`.

Metric to retrieve. `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).

Start timestamp for the time series (ISO 8601 UTC or Unix epoch seconds). Use with `end`; alternative to `statsPeriod`.

Reason an event was filtered/dropped by Sentry (e.g., `filters:release_version`, `spike_protection`). Often used with outcomes like `filtered` or `rate_limited`.

Dimensions to group statistics by. 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.

Filter by event outcome status (e.g., `accepted`, `filtered`, `rate_limited`), indicating how Sentry processed the event.

Project IDs to filter statistics by. Use `["-1"]` to include all accessible projects for the organization.

Filter by data category (e.g., `error`, `transaction`). `attachment` and `profile_duration` categories affect interpretation of `sum(quantity)` in `field` (bytes and milliseconds respectively).

Time series data resolution (e.g., `1h`, `1d`). Must be between `1h` and `1d` (inclusive) and cleanly divide 24 hours (e.g., `1h`, `2h`, `6h`, `12h`, `24h`).

Relative time range for statistics (e.g., `1d` for 1 day, `2w` for 2 weeks). Use `m` (minutes), `h` (hours), `d` (days), `w` (weeks). Provide this or both `start` and `end`.

ID or slug of the Sentry organization.

Queried statistical data. Structure depends on `groupBy` parameters and `interval`. Typically includes start/end timestamps, group keys, and series/totals for the requested `field`.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

Key of a specific integration provider (e.g., 'slack', 'github', 'jira') to filter by; if omitted, returns configurations for all integrations. Refer to Sentry's documentation for supported provider keys.

The ID or slug of the Sentry organization for which to retrieve integration configurations.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

Filters environments by their visibility status: `all`, `hidden`, or `visible`.

The ID or slug of the project for which environments are to be retrieved.

The ID or slug of the organization to which the project belongs.

A list of environment objects associated with the project. Each object contains details such as 'id', 'name', and 'isHidden'.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

The hexadecimal ID of the event to retrieve, as reported by the client.

The unique identifier (ID or slug) of the Sentry project to which the event belongs.

The unique identifier (ID or slug) of the Sentry organization to which the event belongs.

A dictionary object containing the full details of the Sentry event.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

Unique identifier (ID) or human-readable slug of the Sentry project.

Unique identifier (ID) or human-readable slug of the Sentry organization.

Dictionary of project data filters. Keys are filter identifiers (e.g., 'legacyBrowsers', 'localhost', 'webCrawlers'), and values detail filter configuration, including an 'active' status (boolean or list of specific conditions/identifiers).

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

Pagination cursor to retrieve the next or previous set of results (e.g., '100:0:1').

The ID or slug of the Sentry project.

The ID or slug of the Sentry organization.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

Sentry structured search query to filter issues (e.g., "is:resolved", "error.type:TypeError"). Defaults to "is:unresolved"; `""` retrieves all issues regardless of status.

Pagination cursor from a previous response's `Link` header to fetch the next/previous set of issues.

Comma-separated group hashes to retrieve specific issues; incompatible with `query`. Max 100 hashes processed.

Time window for issue statistics (e.g., "24h", "14d"); `""` disables stats. API defaults to "24h" if unspecified.

If `True`, enables issue lookup by short IDs; may return issues from a different project. API default is typically `False`.

Unique identifier (ID) or human-readable slug of the Sentry project.

Unique identifier (ID) or human-readable slug of the Sentry organization.

Error if any occurred during the execution of the action

Whether or not the action execution was successful or not

ID of the client key (DSN).

ID or slug of the project.

ID or slug of the organization.