BigPanda Incidents API

Search, read, assign, comment, tag, snooze, merge, split and resolve correlated incidents.

Operations 21

POST /resources/v2.0/environments/{environment_id}/incidents/{incident_id}/tags Add Multiple Incident Tags to an Incident #
DELETE /resources/v2.0/environments/{environment_id}/incidents/{incident_id}/tags Delete All Tags for an Incident #
GET /resources/v2.0/environments/{environment_id}/incidents/{incident_id}/tags Retrieve All Tags for an Incident #
POST /resources/v2.0/environments/{environment_id}/incidents/{incident_id}/tags/{incidenttag_id} Add an Incident Tag to an Incident #
DELETE /resources/v2.0/environments/{environment_id}/incidents/{incident_id}/tags/{incidenttag_id} Delete an Incident Tag from an Incident #
GET /resources/v2.0/environments/{environment_id}/incidents/{incident_id}/tags/{incidenttag_id} Retrieve an Incident Tag from an Incident #
PUT /resources/v2.0/environments/{environment_id}/incidents/{incident_id}/assignment Assign Incident #
DELETE /resources/v2.0/environments/{environment_id}/incidents/{incident_id}/assignment Unassign Incident #
POST /resources/v2.0/environments/{environment_id}/incidents/{incident_id}/comments Comment on Incident #
POST /resources/v2.0/incidents/tags/definitions Create an Incident Tag Definition #
GET /resources/v2.0/incidents/tags/definitions Get All Incident Tags Definitions #
GET /resources/v2.0/incidents/{incident_id}/activities Get Incident Activities #
GET /resources/v2.0/incidents/tags/definitions/{incidenttag_id} Get an Incident Tag Definition #
PUT /resources/v2.0/incidents/tags/definitions/{incidenttag_id} Update an Incident Tag Definition #
POST /resources/v2.0/environments/{environment_id}/incidents/{incident_id}/merge Merge Incidents #
POST /resources/v2.0/environments/{environment_id}/incidents/{incident_id}/resolve Resolve Incident #
GET /resources/v2.0/environments/{environment_id}/incidents/{incident_id} Retrieve Incident by ID #
GET /resources/v2.0/environments/{environment_id}/incidents Search Incidents #
PUT /resources/v2.0/environments/{environment_id}/incidents/{incident_id}/snooze Snooze Incident #
DELETE /resources/v2.0/environments/{environment_id}/incidents/{incident_id}/snooze Unsnooze Incident #
POST /resources/v2.0/environments/{environment_id}/incidents/{incident_id}/split Split Incident #

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/bigpanda-incidents-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

bigpanda-incidents-api-openapi.yml Raw ↑
openapi: 3.0.3
info:
  title: BigPanda Incidents API
  description: BigPanda Incidents operations, assembled verbatim from the OpenAPI fragments BigPanda publishes on its own
    API reference at https://api-docs.bigpanda.io/. Each operation carries x-source-url naming the exact provider page it
    was read from. BigPanda hosts each organization in a single data management region (US or EU); send requests to the base
    URL for your region.
  version: 1.0.0
  contact:
    name: BigPanda Support
    url: https://api-docs.bigpanda.io/
  license:
    name: Proprietary
    url: https://www.bigpanda.io/legal/
  x-provenance:
    method: searched
    source: https://api-docs.bigpanda.io/llms.txt
    harvested: '2026-09-04'
    assembly: 'Operations copied verbatim from the per-endpoint OpenAPI 3.0.1 fragments BigPanda publishes at https://api-docs.bigpanda.io/<endpoint>.md.
      Assembly-only normalizations: Apidog x-apidog security metadata stripped, securityScheme type "bearer" corrected to
      type http/scheme bearer, schema name collisions suffixed. No operation, parameter, schema or response was authored by
      API Evangelist.'
    operations: 21
servers:
- url: https://api.bigpanda.io
  description: US Region
- url: https://api.eu.bigpanda.io
  description: EU Region
tags:
- name: Incidents
paths:
  /resources/v2.0/environments/{environment_id}/incidents/{incident_id}/tags:
    post:
      summary: Add Multiple Incident Tags to an Incident
      deprecated: false
      description: "Create or update multiple incident tags for a single incident.\n\n## Authentication\nAll BigPanda APIs\
        \ require Bearer Token Authorization in the call headers.\nThis API uses the User API Key type of Authorization token.\
        \ Your User API Key must be provided in the header, prefixed by the word `Bearer`.\n\nExample:\n`Authorization: Bearer\
        \ [YOUR_USER_API_KEY]`\n\n> \U0001F6A7 **Tag value format**\n> \n> Incident tag values are generally a single string.\
        \ When this value is for an incident tag with a fixed list type, the value must be encased in brackets '[]'\n\n**Rate\
        \ limit:** 5 requests per second."
      operationId: create-multiple-incident-tags
      tags:
      - Incidents
      parameters:
      - name: environment_id
        in: path
        description: The system id of a BigPanda environment
        required: true
        example: ''
        schema:
          type: string
          examples:
          - 63bd568809cb331300ffa555
      - name: incident_id
        in: path
        description: The system id of a BigPanda incident
        required: true
        example: ''
        schema:
          type: string
          examples:
          - 681102f731824249f48df555
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/tag_array'
      responses:
        '204':
          x-apidog-ordering: 0
          description: '204'
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/incident_tag_return'
          headers: {}
          x-apidog-name: ''
      security:
      - BearerUser131: []
      x-publication-status: live
      x-run-in-apidog: https://app.apidog.com/web/project/1203004/apis/api-37770110-run
      x-source-url: https://api-docs.bigpanda.io/add-multiple-incident-tags-to-an-incident-37770110e0.md
      x-source-page: Add Multiple Incident Tags to an Incident
    delete:
      summary: Delete All Tags for an Incident
      deprecated: false
      description: "Delete all incident tags for a single incident by ID.\n\n## Authentication\nAll BigPanda APIs require\
        \ Bearer Token Authorization in the call headers.\nThis API uses the User API Key type of Authorization token. Your\
        \ User API Key must be provided in the header, prefixed by the word `Bearer`.\n\nExample:\n`Authorization: Bearer\
        \ [YOUR_USER_API_KEY]`\n\n> \U0001F6A7 **Tag value format**\n> \n> Incident tag values are generally a single string.\
        \ When this value is for an incident tag with a fixed list type, the value must be encased in brackets '[]'\n\n**Rate\
        \ limit:** 5 requests per second."
      operationId: delete-all-incident-tags
      tags:
      - Incidents
      parameters:
      - name: environment_id
        in: path
        description: The system id of a BigPanda environment
        required: true
        example: ''
        schema:
          type: string
          examples:
          - 63bd568809cb331300ffa555
      - name: incident_id
        in: path
        description: The system id of a BigPanda incident
        required: true
        example: ''
        schema:
          type: string
          examples:
          - 681102f731824249f48df555
      responses:
        '204':
          x-apidog-ordering: 0
          description: '204'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/generic204response'
          headers: {}
          x-apidog-name: ''
      security:
      - BearerUser131: []
      x-publication-status: live
      x-run-in-apidog: https://app.apidog.com/web/project/1203004/apis/api-37770111-run
      x-source-url: https://api-docs.bigpanda.io/delete-all-tags-for-an-incident-37770111e0.md
      x-source-page: Delete All Tags for an Incident
    get:
      summary: Retrieve All Tags for an Incident
      deprecated: false
      description: "Retrieve all incident tags from a single incident.\n\n## Authentication\nAll BigPanda APIs require Bearer\
        \ Token Authorization in the call headers.\nThis API uses the User API Key type of Authorization token. Your User\
        \ API Key must be provided in the header, prefixed by the word `Bearer`.\n\nExample:\n`Authorization: Bearer [YOUR_USER_API_KEY]`\n\
        \n> \U0001F6A7 **Tag value format**\n> \n> Incident tag values are generally a single string. When this value is for\
        \ an incident tag with a fixed list type, the value must be encased in brackets '[]'\n\n**Rate limit:** 5 requests\
        \ per second."
      operationId: retrieve-multiple-incident-tags-from-a-single-incident
      tags:
      - Incidents
      parameters:
      - name: environment_id
        in: path
        description: The system id of a BigPanda environment
        required: true
        example: ''
        schema:
          type: string
          examples:
          - 63bd568809cb331300ffa555
      - name: incident_id
        in: path
        description: The system id of a BigPanda incident
        required: true
        example: ''
        schema:
          type: string
          examples:
          - 681102f731824249f48df555
      responses:
        '200':
          x-apidog-ordering: 0
          description: '200'
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/incident_tag'
          headers: {}
          x-apidog-name: ''
      security:
      - BearerUser131: []
      x-publication-status: live
      x-run-in-apidog: https://app.apidog.com/web/project/1203004/apis/api-37770109-run
      x-source-url: https://api-docs.bigpanda.io/retrieve-all-tags-for-an-incident-37770109e0.md
      x-source-page: Retrieve All Tags for an Incident
  /resources/v2.0/environments/{environment_id}/incidents/{incident_id}/tags/{incidenttag_id}:
    post:
      summary: Add an Incident Tag to an Incident
      deprecated: false
      description: "Create or update an incident tag for a single incident.\n\n## Authentication\nAll BigPanda APIs require\
        \ Bearer Token Authorization in the call headers.\nThis API uses the User API Key type of Authorization token. Your\
        \ User API Key must be provided in the header, prefixed by the word `Bearer`.\n\nExample:\n`Authorization: Bearer\
        \ [YOUR_USER_API_KEY]`\n\n> \U0001F6A7 **Tag value format**\n> \n> Incident tag values are generally a single string.\
        \ When this value is for an incident tag with a fixed list type, the value must be encased in brackets '[]'\n\n**Rate\
        \ limit:** 5 requests per second."
      operationId: create-an-incident-tag
      tags:
      - Incidents
      parameters:
      - name: environment_id
        in: path
        description: The system id of a BigPanda environment
        required: true
        example: ''
        schema:
          type: string
          examples:
          - 63bd568809cb331300ffa555
      - name: incident_id
        in: path
        description: The system id of a BigPanda incident
        required: true
        example: ''
        schema:
          type: string
          examples:
          - 681102f731824249f48df555
      - name: incidenttag_id
        in: path
        description: The ID of the incident tag.
        required: true
        example: ''
        schema:
          type: string
          examples:
          - 1611g13t1461
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/tag_value_post'
      responses:
        '204':
          x-apidog-ordering: 0
          description: '204'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/incident_tag_return'
          headers: {}
          x-apidog-name: ''
      security:
      - BearerUser131: []
      x-publication-status: live
      x-run-in-apidog: https://app.apidog.com/web/project/1203004/apis/api-37770107-run
      x-source-url: https://api-docs.bigpanda.io/add-an-incident-tag-to-an-incident-37770107e0.md
      x-source-page: Add an Incident Tag to an Incident
    delete:
      summary: Delete an Incident Tag from an Incident
      deprecated: false
      description: 'Delete a single incident tag of a single incident by ID.


        ## Authentication

        All BigPanda APIs require Bearer Token Authorization in the call headers.

        This API uses the User API Key type of Authorization token. Your User API Key must be provided in the header, prefixed
        by the word `Bearer`.


        Example:

        `Authorization: Bearer [YOUR_USER_API_KEY]`


        **Rate limit:** 5 requests per second.'
      operationId: delete-an-incident-tag
      tags:
      - Incidents
      parameters:
      - name: environment_id
        in: path
        description: The system id of a BigPanda environment
        required: true
        example: ''
        schema:
          type: string
          examples:
          - 63bd568809cb331300ffa555
      - name: incident_id
        in: path
        description: The system id of a BigPanda incident
        required: true
        example: ''
        schema:
          type: string
          examples:
          - 681102f731824249f48df555
      - name: incidenttag_id
        in: path
        description: The ID of the incident tag.
        required: true
        example: ''
        schema:
          type: string
          examples:
          - 1611g13t1461
      responses:
        '204':
          x-apidog-ordering: 0
          description: '204'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/generic204response'
          headers: {}
          x-apidog-name: ''
      security:
      - BearerUser131: []
      x-publication-status: live
      x-run-in-apidog: https://app.apidog.com/web/project/1203004/apis/api-37770108-run
      x-source-url: https://api-docs.bigpanda.io/delete-an-incident-tag-from-an-incident-37770108e0.md
      x-source-page: Delete an Incident Tag from an Incident
    get:
      summary: Retrieve an Incident Tag from an Incident
      deprecated: false
      description: "Retrieve a single incident tag of a single incident by ID.\n\n## Authentication\nAll BigPanda APIs require\
        \ Bearer Token Authorization in the call headers.\nThis API uses the User API Key type of Authorization token. Your\
        \ User API Key must be provided in the header, prefixed by the word `Bearer`.\n\nExample:\n`Authorization: Bearer\
        \ [YOUR_USER_API_KEY]`\n\n> \U0001F6A7 **Tag value format**\n> \n> Incident tag values are generally a single string.\
        \ When this value is for an incident tag with a fixed list type, the value must be encased in brackets '[]'\n\n**Rate\
        \ limit:** 5 requests per second."
      operationId: retrieve-an-incident-tag-from-a-single-incident
      tags:
      - Incidents
      parameters:
      - name: environment_id
        in: path
        description: The system id of a BigPanda environment
        required: true
        example: ''
        schema:
          type: string
          examples:
          - 63bd568809cb331300ffa555
      - name: incident_id
        in: path
        description: The system id of a BigPanda incident
        required: true
        example: ''
        schema:
          type: string
          examples:
          - 681102f731824249f48df555
      - name: incidenttag_id
        in: path
        description: The ID of the incident tag.
        required: true
        example: ''
        schema:
          type: string
          examples:
          - 1611g13t1461
      responses:
        '200':
          x-apidog-ordering: 0
          description: '200'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/incident_tag_return'
          headers: {}
          x-apidog-name: ''
      security:
      - BearerUser131: []
      x-publication-status: live
      x-run-in-apidog: https://app.apidog.com/web/project/1203004/apis/api-37770106-run
      x-source-url: https://api-docs.bigpanda.io/retrieve-an-incident-tag-from-an-incident-37770106e0.md
      x-source-page: Retrieve an Incident Tag from an Incident
  /resources/v2.0/environments/{environment_id}/incidents/{incident_id}/assignment:
    put:
      summary: Assign Incident
      deprecated: false
      description: 'Assign a user to be responsible for an incident.


        ## Authentication

        All BigPanda APIs require Bearer Token Authorization in the call headers.

        This API uses the User API Key type of Authorization token. Your User API Key must be provided in the header, prefixed
        by the word `Bearer`.


        Example:

        `Authorization: Bearer [YOUR_USER_API_KEY]`


        **Rate limit:** 5 requests per second.'
      operationId: assign-incident
      tags:
      - Incidents
      parameters:
      - name: environment_id
        in: path
        description: The system id of a BigPanda environment
        required: true
        example: ''
        schema:
          type: string
          examples:
          - 63bd568809cb331300ffa555
      - name: incident_id
        in: path
        description: The system id of a BigPanda incident
        required: true
        example: ''
        schema:
          type: string
          examples:
          - 681102f731824249f48df555
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/assign_incident'
      responses:
        '204':
          x-apidog-ordering: 0
          description: '204'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/generic204response'
          headers: {}
          x-apidog-name: ''
      security:
      - BearerUser131: []
      x-publication-status: live
      x-run-in-apidog: https://app.apidog.com/web/project/1203004/apis/api-37770102-run
      x-source-url: https://api-docs.bigpanda.io/assign-incident-37770102e0.md
      x-source-page: Assign Incident
    delete:
      summary: Unassign Incident
      deprecated: false
      description: 'Unassign a user from an incident.


        ## Authentication

        All BigPanda APIs require Bearer Token Authorization in the call headers.

        This API uses the User API Key type of Authorization token. Your User API Key must be provided in the header, prefixed
        by the word `Bearer`.


        Example:

        `Authorization: Bearer [YOUR_USER_API_KEY]`


        **Rate limit:** 5 requests per second.'
      operationId: unassign-incident
      tags:
      - Incidents
      parameters:
      - name: environment_id
        in: path
        description: The system id of a BigPanda environment
        required: true
        example: ''
        schema:
          type: string
          examples:
          - 63bd568809cb331300ffa555
      - name: incident_id
        in: path
        description: The system id of a BigPanda incident
        required: true
        example: ''
        schema:
          type: string
          examples:
          - 681102f731824249f48df555
      responses:
        '204':
          x-apidog-ordering: 0
          description: '204'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/generic204response'
          headers: {}
          x-apidog-name: ''
        '400':
          x-apidog-ordering: 1
          description: '400'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/generic400response'
          headers: {}
          x-apidog-name: ''
      security:
      - BearerUser131: []
      x-publication-status: live
      x-run-in-apidog: https://app.apidog.com/web/project/1203004/apis/api-37770103-run
      x-source-url: https://api-docs.bigpanda.io/unassign-incident-37770103e0.md
      x-source-page: Unassign Incident
  /resources/v2.0/environments/{environment_id}/incidents/{incident_id}/comments:
    post:
      summary: Comment on Incident
      deprecated: false
      description: 'Add a comment to a BigPanda incident.


        ## Authentication

        All BigPanda APIs require Bearer Token Authorization in the call headers.

        This API uses the User API Key type of Authorization token. Your User API Key must be provided in the header, prefixed
        by the word `Bearer`.


        Example:

        `Authorization: Bearer [YOUR_USER_API_KEY]`


        **Rate limit:** 5 requests per second.'
      operationId: comment-on-incident
      tags:
      - Incidents
      parameters:
      - name: environment_id
        in: path
        description: The system id of a BigPanda environment
        required: true
        example: ''
        schema:
          type: string
          examples:
          - 63bd568809cb331300ffa555
      - name: incident_id
        in: path
        description: The system id of a BigPanda incident
        required: true
        example: ''
        schema:
          type: string
          examples:
          - 681102f731824249f48df555
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/incident_comments'
      responses:
        '204':
          x-apidog-ordering: 0
          description: '204'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/generic204response'
          headers: {}
          x-apidog-name: ''
      security:
      - BearerUser131: []
      x-publication-status: live
      x-run-in-apidog: https://app.apidog.com/web/project/1203004/apis/api-37770099-run
      x-source-url: https://api-docs.bigpanda.io/comment-on-incident-37770099e0.md
      x-source-page: Comment on Incident
  /resources/v2.0/incidents/tags/definitions:
    post:
      summary: Create an Incident Tag Definition
      deprecated: false
      description: "Create an incident tag definition.\n\n## Authentication\nAll BigPanda APIs require Bearer Token Authorization\
        \ in the call headers.\nThis API uses the User API Key type of Authorization token. Your User API Key must be provided\
        \ in the header, prefixed by the word `Bearer`.\n\nExample:\n`Authorization: Bearer [YOUR_USER_API_KEY]`\n\n> \U0001F6A7\
        \ **Tag value format**\n> \n> Incident tag values are generally a single string. When this value is for an incident\
        \ tag with a fixed list type, the value must be encased in brackets '[]'\n\n**Rate limit:** 5 requests per second."
      operationId: create-an-incident-tag-definition
      tags:
      - Incidents
      parameters: []
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/incident_tag_schema'
      responses:
        '204':
          x-apidog-ordering: 0
          description: '204'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/incident_tag_schema_response'
          headers: {}
          x-apidog-name: ''
      security:
      - BearerUser131: []
      x-publication-status: live
      x-run-in-apidog: https://app.apidog.com/web/project/1203004/apis/api-37770113-run
      x-source-url: https://api-docs.bigpanda.io/create-an-incident-tag-definition-37770113e0.md
      x-source-page: Create an Incident Tag Definition
    get:
      summary: Get All Incident Tags Definitions
      deprecated: false
      description: "Get all incident tags definitions.\n\n## Authentication\nAll BigPanda APIs require Bearer Token Authorization\
        \ in the call headers.\nThis API uses the User API Key type of Authorization token. Your User API Key must be provided\
        \ in the header, prefixed by the word `Bearer`.\n\nExample:\n`Authorization: Bearer [YOUR_USER_API_KEY]`\n\n> \U0001F6A7\
        \ **Tag value format**\n> \n> Incident tag values are generally a single string. When this value is for an incident\
        \ tag with a fixed list type, the value must be encased in brackets '[]'\n\n**Rate limit:** 5 requests per second."
      operationId: get-all-incident-tags-definitions
      tags:
      - Incidents
      parameters:
      - name: active
        in: query
        description: Whether to filter results to only active items.
        required: false
        example: ''
        schema:
          type: boolean
          default: true
          examples:
          - false
      - name: type
        in: query
        description: 'Incident tag definition''s type. One of [`Text`, `MultiValue`, `Priority`, `ClosedListValuesMulti`,
          `ClosedListValuesSingle`].

          '
        required: false
        example: ''
        schema:
          type: string
      responses:
        '200':
          x-apidog-ordering: 0
          description: '200'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/incident_tag_schema_response'
          headers: {}
          x-apidog-name: ''
      security:
      - BearerUser131: []
      x-publication-status: live
      x-run-in-apidog: https://app.apidog.com/web/project/1203004/apis/api-37770112-run
      x-source-url: https://api-docs.bigpanda.io/get-all-incident-tags-definitions-37770112e0.md
      x-source-page: Get All Incident Tags Definitions
  /resources/v2.0/incidents/{incident_id}/activities:
    get:
      summary: Get Incident Activities
      deprecated: false
      description: "Retrieve a list of enrichment actions taken on an incident.\n\n## Authentication\nAll BigPanda APIs require\
        \ Bearer Token Authorization in the call headers.\nThis API uses the User API Key type of Authorization token. Your\
        \ User API Key must be provided in the header, prefixed by the word `Bearer`.\n\nExample:\n`Authorization: Bearer\
        \ [YOUR_USER_API_KEY]`\n\n## Filter by activity\nIncident Activities can be filtered by activity type, using a comma\
        \ separated query string of one or more activity types with the call.\n\nExample queries:\n- `​/activities?page=5`​​\
        \ - will return results from the 5th set of results\n- ​​`/activities?per_page=40​​` - will return 40 results per\
        \ page instead of the default 20\n- ​`/activities?types=incident_commented,incident_snoozed​​` - will return only\
        \ comment and snooze activity\n- `/activities?types=incident_created,incident_resolved_ui_manually,incident_resolved_api,incident_resolved_by_alerts,incident_reopen`​​\
        \ - will return only opening and closing activity for the incident.\n\nActivities available for retrieval are:​\n\
        \    - incident_created​\n    - incident_assigned​\n    - incident_unassigned\n    - incident_become_flapping\n  \
        \  - incident_commented​\n    - incident_resolved_ui_manually​\n    - incident_resolved_api\n    - incident_alerts_resolved\n\
        \    - incident_tag_removed\n    - incident_tag_updated​\n    - incident_merged_destination\n    - incident_merged_source\n\
        \    - incident_rcc_update\n    - incident_shared\n    - incident_splitted_destination\n    - incident_splitted_source\n\
        \    - incident_snoozed\n    - incident_unsnoozed\n    - incident_opened\n    - incident_reopen\n    - incident_resolved_by_alerts\n\
        \n## Return order\nActivities are returned in reverse timestamp order, most recent activities to oldest.\n\n## Time-based\
        \ alert resolution activity type\nStale incident resolution through time-based alert resolution is included under\
        \ the ​`incident_resolved_api`​​ activity type.\n"
      operationId: get-incident-activities
      tags:
      - Incidents
      parameters:
      - name: incident_id
        in: path
        description: The system id of a BigPanda incident
        required: true
        example: ''
        schema:
          type: string
          examples:
          - 681102f731824249f48df555
      - name: page
        in: query
        description: Which set of results to return.
        required: false
        example: 0
        schema:
          type: integer
          default: 1
          examples:
          - 4
      - name: per_page
        in: query
        description: Number of results to show for each page.
        required: false
        example: 0
        schema:
          type: integer
          default: 20
          examples:
          - 30
      - name: types
        in: query
        description: 'A list of activity types to return, separated by commas. Leave blank to return all activity

          types.


          Activities available for retrieval are:​

          - incident_created​

          - incident_assigned​

          - incident_unassigned

          - incident_become_flapping

          - incident_commented​

          - incident_resolved_ui_manually​

          - incident_resolved_api

          - incident_alerts_resolved

          - incident_tag_removed

          - incident_tag_updated​

          - incident_merged_destination

          - incident_merged_source

          - incident_rcc_update

          - incident_shared

          - incident_splitted_destination

          - incident_splitted_source

          - incident_snoozed

          - incident_unsnoozed

          - incident_opened

          - incident_reopen

          - incident_resolved_by_alerts

          '
        required: false
        example: ''
        schema:
          type: string
      responses:
        '200':
          x-apidog-ordering: 0
          description: '200'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/incident_activities'
          headers: {}
          x-apidog-name: ''
      security:
      - BearerUser131: []
      x-publication-status: live
      x-run-in-apidog: https://app.apidog.com/web/project/1203004/apis/api-37770105-run
      x-source-url: https://api-docs.bigpanda.io/get-incident-activities-37770105e0.md
      x-source-page: Get Incident Activities
  /resources/v2.0/incidents/tags/definitions/{incidenttag_id}:
    get:
      summary: Get an Incident Tag Definition
      deprecated: false
      description: "Get incident tag definition by ID.\n\n## Authentication\nAll BigPanda APIs require Bearer Token Authorization\
        \ in the call headers.\nThis API uses the User API Key type of Authorization token. Your User API Key must be provided\
        \ in the header, prefixed by the word `Bearer`.\n\nExample:\n`Authorization: Bearer [YOUR_USER_API_KEY]`\n\n> \U0001F6A7\
        \ **Tag value format**\n> \n> Incident tag values are generally a single string. When this value is for an incident\
        \ tag with a fixed list type, the value must be encased in brackets '[]'\n\n**Rate limit:** 5 requests per second."
      operationId: get-an-incident-tag-definition
      tags:
      - Incidents
      parameters:
      - name: incidenttag_id
        in: path
        description: The ID of the incident tag.
        required: true
        example: ''
        schema:
          type: string
          examples:
          - 1611g13t1461
      responses:
        '200':
          x-apidog-ordering: 0
          description: '200'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/incident_tag_schema_response'
          headers: {}
          x-apidog-name: ''
      security:
      - BearerUser131: []
      x-publication-status: live
      x-run-in-apidog: https://app.apidog.com/web/project/1203004/apis/api-37770114-run
      x-source-url: https://api-docs.bigpanda.io/get-an-incident-tag-definition-37770114e0.md
      x-source-page: Get an Incident Tag Definition
    put:
      summary: Update an Incident Tag Definition
      deprecated: false
      description: "Update an incident tag definition by ID.\n\n## Authentication\nAll BigPanda APIs require Bearer Token\
        \ Authorization in the call headers.\nThis API uses the User API Key type of Authorization token. Your User API Key\
        \ must be provided in the header, prefixed by the word `Bearer`.\n\nExample:\n`Authorization: Bearer [YOUR_USER_API_KEY]`\n\
        \n> \U0001F6A7 **Tag value format**\n> \n> Incident tag values are generally a single string. When this value is for\
        \ an incident tag with a fixed list type, the value must be encased in brackets '[]'\n\n**Rate limit:** 5 requests\
        \ per second."
      operationId: update-an-incident-tag-definition
      tags:
      - Incidents
      parameters:
      - name: incidenttag_id
        in: path
        description: The ID of the incident tag.
        required: true
        example: ''
        schema:
          type: string
          examples:
          - 1611g13t1461
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/incident_tag_schema'
      responses:
        '200':
          x-apidog-ordering: 0
          description: '200'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/incident_tag_schema_response'
          headers: {}
          x-apidog-name: ''
      security:
      - BearerUser131: []
      x-publication-status: live
      x-run-in-apidog: https://app.apidog.com/web/project/1203004/apis/api-37770115-run
      x-source-url: https://api-docs.bigpanda.io/update-an-incident-tag-definition-37770115e0.md
      x-source-page: Update an Incident Tag Definition
  /resources/v2.0/environments/{environment_id}/incidents/{incident_id}/merge:
    post:
      summary: Merge Incidents
      deprecated: false
      description: "Merges a list of BigPanda incidents into 1 incident.\n\n> \U0001F6A7 **Alert limit**\n> \n> The maximum\
        \ number of alerts that can be correlated into a single incident is 300. \n>\n> If the combined number of alerts in\
        \ the incidents being merged exceeds 300, the merge will fail.\n\n## Authentication\nAll BigPanda APIs require Bearer\
        \ Token Authorization in the call headers.\nThis API uses the User API Key type of Authorization token. Your User\
        \ API Key must be provided in the header, prefixed by the word `Bearer`.\n\nExample:\n`Authorization: Bearer [YOUR_USER_API_KEY]`\n\
        \n**Rate limit:** 5 requests per second."
      operationId: merge-incidents-1
      tags:
      - Incidents
      parameters:
      - name: environment_id
        in: path
        description: The system id of a BigPanda environment
        required: true
        example: ''
        schema:
          type: string
          examples:
          - 63bd568809cb331300ffa555
      - name: incident_id
        in: path
        description: The system id of a 

# --- truncated at 32 KB (64 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/bigpanda/refs/heads/main/openapi/bigpanda-incidents-api-openapi.yml