Sentry Alerts API

Manage alerts (beta)

Operations 7

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

GET /organizations/{organization_id_or_slug}/alerts/ List an organization's alerts · Sentry Fetch alerts #
Ask an LLM
“Which alerts are set up across my Sentry organization?”
“Can I page through every alert my org has configured?”
Tell an agent
List all alerts in organization {org}.
Show the next page of alerts for {org} starting at cursor {cursor}.
POST /organizations/{organization_id_or_slug}/alerts/ Create an organization alert · Sentry Create an alert for an organization #
Ask an LLM
“How can I add a new alert to my organization?”
“What do I need to supply to create an alert besides a name?”
Tell an agent
Create an alert named {name} in organization {org}.
Add a new org-level alert called {name}.
PUT /organizations/{organization_id_or_slug}/alerts/ Bulk update alert status · Sentry Mutate an organization's alerts #
Ask an LLM
“How do I change the status of several alerts at once?”
“Is there a way to mute or enable a batch of alerts in one call?”
Tell an agent
Set the status of alerts {ids} in {org} to {status}.
Bulk change status to {status} for every alert listed in {ids}.
DELETE /organizations/{organization_id_or_slug}/alerts/ Delete several alerts at once · Sentry Bulk delete alerts #
Ask an LLM
“Can I remove multiple alerts in a single request?”
“Is bulk deletion of alerts permanent?”
Tell an agent destructive · confirm first
Bulk delete alerts {id} from organization {org}.
Remove all the alerts with ids {id} in one go.
GET /organizations/{organization_id_or_slug}/alerts/{alert_id}/ Get one alert's details · Sentry Fetch an alert #
Ask an LLM
“What is configured on a specific alert?”
“Where can I see the full details of a single alert by its ID?”
Tell an agent
Show alert {alert_id} in organization {org}.
Fetch the details of alert {alert_id}.
PUT /organizations/{organization_id_or_slug}/alerts/{alert_id}/ Rename or update an alert · Sentry Update an alert by ID #
Ask an LLM
“How do I rename an existing alert?”
“Can I edit a single alert without touching the others?”
Tell an agent
Rename alert {alert_id} in {org} to {name}.
Update alert {alert_id} with the name {name}.
DELETE /organizations/{organization_id_or_slug}/alerts/{alert_id}/ Delete a single alert · Sentry Delete an alert #
Ask an LLM
“How do I get rid of one alert I no longer need?”
“What happens when I delete one specific alert by ID?”
Tell an agent destructive · confirm first
Delete alert {alert_id} from organization {org}.
Remove the alert {alert_id}.

Documentation

Specifications

Schemas & Data

Other Resources

🔗
SDKs
https://docs.sentry.io/platforms/
🔗
PostmanCollection
https://www.postman.com/sentryio/sentry-api-collection/documentation/xtzhckg/sentry-api-collection
🔗
Webhooks
https://docs.sentry.io/organization/integrations/integration-platform/webhooks/
🔗
Pagination
https://docs.sentry.io/api/pagination/
🔗
Permissions
https://docs.sentry.io/api/permissions/
🔗
Reference
https://docs.sentry.io/api/requests/
🔗
JSONLD
https://raw.githubusercontent.com/api-evangelist/sentry-system/refs/heads/main/json-ld/sentry-context.jsonld
🔗
APIsJSON
https://raw.githubusercontent.com/api-evangelist/sentry-system/refs/heads/main/apis.yml
🔗
Arazzo
https://raw.githubusercontent.com/api-evangelist/sentry-system/refs/heads/main/arazzo/sentry-system-capture-user-feedback-workflow.yml
🔗
Arazzo
https://raw.githubusercontent.com/api-evangelist/sentry-system/refs/heads/main/arazzo/sentry-system-create-cron-monitor-workflow.yml
🔗
Arazzo
https://raw.githubusercontent.com/api-evangelist/sentry-system/refs/heads/main/arazzo/sentry-system-create-metric-alert-workflow.yml
🔗
Arazzo
https://raw.githubusercontent.com/api-evangelist/sentry-system/refs/heads/main/arazzo/sentry-system-create-team-add-member-workflow.yml
🔗
Arazzo
https://raw.githubusercontent.com/api-evangelist/sentry-system/refs/heads/main/arazzo/sentry-system-cut-release-deploy-workflow.yml
🔗
Arazzo
https://raw.githubusercontent.com/api-evangelist/sentry-system/refs/heads/main/arazzo/sentry-system-grant-team-project-access-workflow.yml
🔗
Arazzo
https://raw.githubusercontent.com/api-evangelist/sentry-system/refs/heads/main/arazzo/sentry-system-investigate-issue-tags-workflow.yml
🔗
Arazzo
https://raw.githubusercontent.com/api-evangelist/sentry-system/refs/heads/main/arazzo/sentry-system-invite-member-onboard-team-workflow.yml
🔗
Arazzo
https://raw.githubusercontent.com/api-evangelist/sentry-system/refs/heads/main/arazzo/sentry-system-provision-project-key-workflow.yml
🔗
Arazzo
https://raw.githubusercontent.com/api-evangelist/sentry-system/refs/heads/main/arazzo/sentry-system-seer-autofix-issue-workflow.yml
🔗
Arazzo
https://raw.githubusercontent.com/api-evangelist/sentry-system/refs/heads/main/arazzo/sentry-system-sync-prevent-repos-workflow.yml
🔗
Arazzo
https://raw.githubusercontent.com/api-evangelist/sentry-system/refs/heads/main/arazzo/sentry-system-triage-resolve-issue-workflow.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/sentry-system:sentry-system-alerts-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

sentry-system-alerts-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Sentry Monitors Alerts API
  description: The Monitors and Alerts API provides beta endpoints for managing monitors and alerts in Sentry, including creating, retrieving, updating, and deleting monitors and alerts, as well as bulk operations at the organization level. These endpoints are currently in beta and may be subject to change.
  version: 0.0.1
  contact:
    name: Sentry Support
    url: https://sentry.io/support/
    email: support@sentry.io
servers:
- url: https://sentry.io/api/0
  description: Sentry Production API
security:
- BearerAuth: []
tags:
- name: Alerts
  description: Manage alerts (beta)
paths:
  /organizations/{organization_id_or_slug}/alerts/:
    get:
      operationId: fetchAlerts
      summary: Sentry Fetch alerts
      description: Returns a list of alerts for the organization.
      tags:
      - Alerts
      parameters:
      - $ref: '#/components/parameters/OrganizationIdOrSlug'
      - name: cursor
        in: query
        description: Pagination cursor.
        schema:
          type: string
      responses:
        '200':
          description: A list of alerts.
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/MonitorAlert'
        '401':
          description: Unauthorized.
        '403':
          description: Forbidden.
    post:
      operationId: createAlert
      summary: Sentry Create an alert for an organization
      description: Creates a new alert for the organization.
      tags:
      - Alerts
      parameters:
      - $ref: '#/components/parameters/OrganizationIdOrSlug'
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
              - name
              properties:
                name:
                  type: string
                  description: The name of the alert.
      responses:
        '201':
          description: Alert created.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/MonitorAlert'
        '400':
          description: Bad request.
        '401':
          description: Unauthorized.
    put:
      operationId: mutateOrganizationAlerts
      summary: Sentry Mutate an organization's alerts
      description: Bulk update alerts for an organization.
      tags:
      - Alerts
      parameters:
      - $ref: '#/components/parameters/OrganizationIdOrSlug'
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                ids:
                  type: array
                  items:
                    type: string
                status:
                  type: string
      responses:
        '200':
          description: Alerts updated.
        '401':
          description: Unauthorized.
        '403':
          description: Forbidden.
    delete:
      operationId: bulkDeleteAlerts
      summary: Sentry Bulk delete alerts
      description: Bulk delete alerts for an organization.
      tags:
      - Alerts
      parameters:
      - $ref: '#/components/parameters/OrganizationIdOrSlug'
      - name: id
        in: query
        description: IDs of alerts to delete.
        schema:
          type: array
          items:
            type: string
      responses:
        '204':
          description: Alerts deleted.
        '401':
          description: Unauthorized.
        '403':
          description: Forbidden.
  /organizations/{organization_id_or_slug}/alerts/{alert_id}/:
    get:
      operationId: fetchAlert
      summary: Sentry Fetch an alert
      description: Returns details for a specific alert.
      tags:
      - Alerts
      parameters:
      - $ref: '#/components/parameters/OrganizationIdOrSlug'
      - $ref: '#/components/parameters/AlertId'
      responses:
        '200':
          description: Alert details.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/MonitorAlert'
        '401':
          description: Unauthorized.
        '404':
          description: Alert not found.
    put:
      operationId: updateAlert
      summary: Sentry Update an alert by ID
      description: Updates an alert.
      tags:
      - Alerts
      parameters:
      - $ref: '#/components/parameters/OrganizationIdOrSlug'
      - $ref: '#/components/parameters/AlertId'
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                name:
                  type: string
      responses:
        '200':
          description: Alert updated.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/MonitorAlert'
        '400':
          description: Bad request.
        '401':
          description: Unauthorized.
        '404':
          description: Alert not found.
    delete:
      operationId: deleteAlert
      summary: Sentry Delete an alert
      description: Deletes an alert.
      tags:
      - Alerts
      parameters:
      - $ref: '#/components/parameters/OrganizationIdOrSlug'
      - $ref: '#/components/parameters/AlertId'
      responses:
        '204':
          description: Alert deleted.
        '401':
          description: Unauthorized.
        '404':
          description: Alert not found.
components:
  schemas:
    MonitorAlert:
      type: object
      properties:
        id:
          type: string
        name:
          type: string
        status:
          type: string
        dateCreated:
          type: string
          format: date-time
      required:
      - id
      - name
  parameters:
    AlertId:
      name: alert_id
      in: path
      required: true
      description: The ID of the alert.
      schema:
        type: string
    OrganizationIdOrSlug:
      name: organization_id_or_slug
      in: path
      required: true
      description: The ID or slug of the organization.
      schema:
        type: string
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      description: Authentication token for the Sentry API.