BigPanda Major Incident Management API

Execute a major-incident workflow from a template, then list, inspect, cancel or resolve the execution.

Operations 7

POST /mim/executions/{executionId}/cancel Cancel a MIM Execution
POST /mim/execute Execute a MIM Workflow From a Template
GET /mim/templates List Templates
POST /mim/executions/{executionId}/resolve Resolve a MIM execution
GET /mim/executions/{executionId} Retrieve MIM Execution Details
GET /mim/executions Retrieve MIM Executions
GET /mim/templates/{templateId} Retrieve Template Details

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-mim-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-mim-api-openapi.yml Raw ↑
openapi: 3.0.3
info:
  title: BigPanda Major Incident Management API
  description: BigPanda Major Incident Management 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: 7
servers:
- url: https://api.bigpanda.io
  description: US Region
- url: https://api.eu.bigpanda.io
  description: EU Region
tags:
- name: Major Incident Management
paths:
  /mim/executions/{executionId}/cancel:
    post:
      summary: Cancel a MIM Execution
      deprecated: false
      description: "Cancels an active execution without resolving it. \n\nUnlike the resolve endpoint, cancellation moves\
        \ the execution directly to `cancelled` status without performing closing-out work.\n\n> \U0001F6A7 **Authentication**\n\
        > \n> All BigPanda APIs require Bearer Token Authorization in the call headers.\n>\n> This API uses the User API Key\
        \ type of Authorization token.\n\n> ❗ **Rate limitations**\n> \n> To maintain quality of service, the Biggy API is\
        \ limited to 100 requests per minute. Additional requests will return a 429 response code and the request will need\
        \ to be retried."
      tags:
      - Major Incident Management
      parameters:
      - name: executionId
        in: path
        description: Unique identifier of the MIM execution. (24 character string)
        required: true
        example: 665b2c3d4e5f6a7b8c9d0e1f
        schema:
          type: string
      requestBody:
        content:
          multipart/form-data:
            schema:
              type: object
              properties:
                reason:
                  description: Reason for the cancellation.
                  type: string
                  examples:
                  - Duplicate incident - already handled by another team.
                  example: Duplicate incident - already handled by another team.
      responses:
        '200':
          x-apidog-ordering: 0
          description: ''
          content:
            application/json:
              schema:
                type: object
                properties:
                  executionId:
                    type: string
                    description: Unique idenfitier of the MIM execution.
                    examples:
                    - 665b2c3d4e5f6a7b8c9d0e1f
                  status:
                    type: string
                    description: Status of the MIM execution.
                    examples:
                    - cancelled
                  mimName:
                    type: string
                    description: Name of the inicdent.
                    examples:
                    - Payments Outage 2026-03-11
                  templateId:
                    type: string
                    description: Template used in the MIM execution.
                    examples:
                    - 665a1b2c3d4e5f6a7b8c9d0e
                  createdAt:
                    type: string
                    description: Date and time the execution was crated.
                    examples:
                    - '2026-03-11T22:30:00.000Z'
                  createdBy:
                    type: object
                    properties:
                      system:
                        type: string
                        description: Who created the execution.
                        examples:
                        - user
                    required:
                    - system
                    x-apidog-orders:
                    - system
                  communicationEntities:
                    type: array
                    items:
                      type: string
                    description: Communication entities associated with the MIM execution.
                  actions:
                    type: array
                    items:
                      type: string
                    description: Actions associated with the MIM execution.
                x-apidog-orders:
                - executionId
                - status
                - mimName
                - templateId
                - createdAt
                - createdBy
                - communicationEntities
                - actions
          headers: {}
          x-apidog-name: ''
        '400':
          x-apidog-ordering: 1
          description: ''
          content:
            application/json:
              schema:
                type: object
                properties:
                  statusCode:
                    type: integer
                    description: Status code associated with the error.
                    examples:
                    - 400
                  error:
                    type: string
                    description: Error type.
                    examples:
                    - MimValidationError
                  message:
                    type: string
                    description: Error message.
                    examples:
                    - Cannot cancel execution in terminal status completed
                x-apidog-orders:
                - statusCode
                - error
                - message
          headers: {}
          x-apidog-name: ''
        '404':
          x-apidog-ordering: 2
          description: ''
          content:
            application/json:
              schema:
                type: object
                properties:
                  statusCode:
                    type: integer
                    description: Status code associated with the error.
                    examples:
                    - 404
                  error:
                    type: string
                    description: Error type.
                    examples:
                    - MimNotFoundError
                  message:
                    type: string
                    description: Error message.
                    examples:
                    - Execution not found.
                x-apidog-orders:
                - statusCode
                - error
                - message
          headers: {}
          x-apidog-name: ''
      x-publication-status: live
      x-run-in-apidog: https://app.apidog.com/web/project/1203004/apis/api-37769968-run
      x-source-url: https://api-docs.bigpanda.io/cancel-a-mim-execution-37769968e0.md
      x-source-page: Cancel a MIM Execution
  /mim/execute:
    post:
      summary: Execute a MIM Workflow From a Template
      deprecated: false
      description: "Start a major incident workflow from a template. Create communication channels, provision resources, and\
        \ kick off automated actions. \n\nImmediately returns an executionId that can be polled via the executions endpoints.\
        \ \n\nBanner posting and LLM enrichment happen asynchronously after creation and do not block the response.\n\nLookback\
        \ backfill failures are returned in warnings rather than failing the request.\n\n> \U0001F6A7 **valueSource**\n> \n\
        > If `valueSource` is `runtime` and `isRequired` is `true`, you must have values in `communicationEntityValues` or\
        \ the request fails with a 400 return.\n\n> \U0001F4D8 **MIM creator**\n>\n> The user associated with the API key\
        \ is automatically assigned as the MIM creator.\n\n> \U0001F6A7 **Authentication**\n> \n> All BigPanda APIs require\
        \ Bearer Token Authorization in the call headers.\n>\n> This API uses the User API Key type of Authorization token.\n\
        \n> ❗ **Rate limitations**\n> \n> To maintain quality of service, the Biggy API is limited to 100 requests per minute.\
        \ Additional requests will return a 429 response code and the request will need to be retried."
      tags:
      - Major Incident Management
      parameters: []
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                templateId:
                  type: string
                  description: Unique identifier of the MIM template.
                  examples:
                  - 665a1b2c3d4e5f6a7b8c9d0e
                mimName:
                  type: string
                  description: Name of the MIM template.
                  examples:
                  - Payments Outage 2026-03-11
                incidentPriority:
                  type: string
                  description: Priority level of the incident.
                  examples:
                  - P1
                communicationEntityValues:
                  type: array
                  items:
                    type: object
                    properties:
                      entityId:
                        type: string
                        description: Unique identifier of the communication entity.
                        examples:
                        - 665b2c3d4e5f6a7b8c9d0e1f
                      value:
                        type: object
                        properties:
                          channelId:
                            type: string
                            description: Unique identifier of the communication entity channel.
                            examples:
                            - C0123456789
                          channelName:
                            type: string
                            description: Name of the communication entity channel.
                            examples:
                            - null
                        x-apidog-orders:
                        - channelId
                        - channelName
                    x-apidog-orders:
                    - entityId
                    - value
                incidentDetails:
                  type: object
                  properties:
                    title:
                      type: string
                      description: Title of the incident.
                      examples:
                      - Payment processing outage
                    description:
                      type: string
                      description: Description of the incident.
                      examples:
                      - All payment processing is down across all regions.
                    impact:
                      type: object
                      properties:
                        services:
                          type: array
                          items:
                            type: string
                          description: Services impacted by the incident.
                          examples:
                          - payments-api
                        statement:
                          type: string
                          description: Statement associated with the incident.
                          examples:
                          - All customers unable to complete purchases
                      description: Impact of the incident.
                      x-apidog-orders:
                      - services
                      - statement
                  x-apidog-orders:
                  - title
                  - description
                  - impact
              x-apidog-orders:
              - templateId
              - mimName
              - incidentPriority
              - communicationEntityValues
              - incidentDetails
            example: "curl -sS -X POST \"https://api.biggy.io/mim/execute\" \\\r\n  -H \"Authorization: Bearer your-api-key\"\
              \ \\\r\n  -H \"Content-Type: application/json\" \\\r\n  -d '{\r\n    \"templateId\": \"665a1b2c3d4e5f6a7b8c9d0e\"\
              ,\r\n    \"mimName\": \"Payments Outage 2026-03-11\",\r\n    \"incidentPriority\": \"P1\",\r\n    \"communicationEntityValues\"\
              : [\r\n        {\r\n            \"entityId\": \"665b2c3d4e5f6a7b8c9d0e1f\",\r\n            \"value\": {\r\n\
              \                \"channelId\": \"C0123456789\",\r\n                \"channelName\": \"#payments-outage-war-room\"\
              \r\n            }\r\n        }\r\n    ],\r\n    \"incidentDetails\": {\r\n        \"title\": \"Payment processing\
              \ outage\",\r\n        \"description\": \"All payment processing is down across all regions.\",\r\n        \"\
              impact\": {\r\n            \"services\": [\r\n                \"payments-api\",\r\n                \"checkout-service\"\
              \r\n            ],\r\n            \"statement\": \"All customers unable to complete purchases\"\r\n        }\r\
              \n    }\r\n}'"
      responses:
        '201':
          x-apidog-ordering: 0
          description: ''
          content:
            application/json:
              schema:
                type: object
                properties:
                  executionId:
                    type: string
                    description: Unique identifier of the MIM execution.
                  status:
                    type: string
                    description: Status of the MIM execution
                  message:
                    type: string
                    description: 'Message associated with the MIM execution. '
                  resolvedEntities:
                    type: array
                    items:
                      type: object
                      properties:
                        entityId:
                          type: string
                          description: Unique identifier of the entity.
                        type:
                          type: string
                          description: Type of entity.
                        label:
                          type: string
                          description: Label associated with the entity.
                        value:
                          type: object
                          properties:
                            channelId:
                              type: string
                              description: Unique identifier of the channel.
                            channelName:
                              type: string
                              description: Name of the channel.
                            link:
                              type: string
                              description: Link to the channel.
                          required:
                          - channelId
                          - channelName
                          - link
                          x-apidog-orders:
                          - channelId
                          - channelName
                          - link
                      x-apidog-orders:
                      - entityId
                      - type
                      - label
                      - value
                    description: MIM entities that have been resolved.
                  warnings:
                    type: array
                    items:
                      type: string
                    description: Warnings associated with the execution.
                required:
                - executionId
                - status
                - message
                - resolvedEntities
                - warnings
                x-apidog-orders:
                - executionId
                - status
                - message
                - resolvedEntities
                - warnings
          headers: {}
          x-apidog-name: ''
        '400':
          x-apidog-ordering: 1
          description: ''
          content:
            application/json:
              schema:
                type: object
                properties:
                  statusCode:
                    type: integer
                  error:
                    type: string
                  message:
                    type: string
                required:
                - statusCode
                - error
                - message
                x-apidog-orders:
                - statusCode
                - error
                - message
          headers: {}
          x-apidog-name: ''
        '404':
          x-apidog-ordering: 2
          description: ''
          content:
            application/json:
              schema:
                type: object
                properties:
                  statusCode:
                    type: integer
                    description: Status code of the error.
                  error:
                    type: string
                    description: Type of error.
                  message:
                    type: string
                    description: Error message.
                required:
                - statusCode
                - error
                - message
                x-apidog-orders:
                - statusCode
                - error
                - message
          headers: {}
          x-apidog-name: ''
      x-publication-status: live
      x-run-in-apidog: https://app.apidog.com/web/project/1203004/apis/api-37769964-run
      x-source-url: https://api-docs.bigpanda.io/execute-a-mim-workflow-from-a-template-37769964e0.md
      x-source-page: Execute a MIM Workflow From a Template
  /mim/templates:
    get:
      summary: List Templates
      deprecated: false
      description: "Return a paginated list of MIM templates configured for your organization. \n\nEach template summary includes\
        \ the communication entities and a count of automated actions.\n\n> \U0001F6A7 **Authentication**\n> \n> All BigPanda\
        \ APIs require Bearer Token Authorization in the call headers.\n>\n> This API uses the User API Key type of Authorization\
        \ token.\n\n> ❗ **Rate limitations**\n> \n> To maintain quality of service, the Biggy API is limited to 100 requests\
        \ per minute. Additional requests will return a 429 response code and the request will need to be retried."
      tags:
      - Major Incident Management
      parameters:
      - name: limit
        in: query
        description: Maximum number of templates to return. (1-100)
        required: false
        example: 3
        schema:
          type: integer
      - name: offset
        in: query
        description: Maximum number of templates to skip. (Minimum is 0)
        required: false
        example: 0
        schema:
          type: integer
      responses:
        '200':
          x-apidog-ordering: 0
          description: ''
          content:
            application/json:
              schema:
                type: object
                properties:
                  templates:
                    type: array
                    items:
                      type: object
                      properties:
                        templateId:
                          type: string
                          description: Unique identifier of the MIM template.
                          examples:
                          - 665a1b2c3d4e5f6a7b8c9d0e
                        name:
                          type: string
                          description: Name of the MIM template.
                          examples:
                          - P1 Bridge
                        description:
                          type: string
                          description: Short description of the MIM template.
                          examples:
                          - Full incident bridge with all communication channels.
                        communicationEntities:
                          type: array
                          items:
                            type: object
                            properties:
                              entityId:
                                type: string
                                description: Unique identifier of the communication entity.
                                examples:
                                - 665b2c3d4e5f6a7b8c9d0e1f
                              type:
                                type: string
                                description: Type of communication entity.
                                examples:
                                - slack_channel
                              label:
                                type: string
                                description: Short label for the communication entity.
                                examples:
                                - War Room Channel
                              isRequired:
                                type: boolean
                                description: Whether or not the communication entity is required.
                                examples:
                                - false
                              valueSource:
                                type: string
                                description: Value source of the communication entity. One of  `runtime` (caller supplies),
                                  `static` (pre-configured), or `create_on_mim_creation` (auto-created).
                                examples:
                                - runtime
                              hintText:
                                type: string
                                description: Short text describing how to use the communication entity.
                                examples:
                                - Select or create a Slack channel for the war room
                            x-apidog-orders:
                            - entityId
                            - type
                            - label
                            - isRequired
                            - valueSource
                            - hintText
                          description: Communication entities configured in the MIM template.
                        actionsCount:
                          type: integer
                          description: Number of actions associated with the MIM template.
                          examples:
                          - 5
                        swarmInvestigationEligibility:
                          type: string
                          description: Whether or not swarm is enabled. One of `always_on`, `optionally_on`, `not_enabled`.
                      x-apidog-orders:
                      - templateId
                      - name
                      - description
                      - communicationEntities
                      - actionsCount
                      - swarmInvestigationEligibility
                  total:
                    type: integer
                    description: Total number of MIM templates.
                    examples:
                    - 3
                required:
                - templates
                - total
                x-apidog-orders:
                - templates
                - total
              example:
                templates:
                - templateId: 665a1b2c3d4e5f6a7b8c9d0e
                  name: P1 - Full Bridge
                  description: Full incident bridge with all communication channels.
                  communicationEntities:
                  - entityId: 665b2c3d4e5f6a7b8c9d0e1f
                    type: slack_channel
                    label: War Room Channel
                    isRequired: true
                    valueSource: runtime
                    hintText: Select or create a Slack channel for the war room
                  actionsCount: 5
                  swarmInvestigationEligibility: optionally_on
                total: 3
          headers: {}
          x-apidog-name: ''
      x-publication-status: live
      x-run-in-apidog: https://app.apidog.com/web/project/1203004/apis/api-37769965-run
      x-source-url: https://api-docs.bigpanda.io/list-templates-37769965e0.md
      x-source-page: List Templates
  /mim/executions/{executionId}/resolve:
    post:
      summary: Resolve a MIM execution
      deprecated: false
      description: "Marks an active execution as resolved. The execution transitions to `pending_resolution` status while\
        \ the MIM orchestrator performs closing-out work (final reports, channel archiving, etc.).\n\nExecutions in `active`,\
        \ `paused`, or `pending_resolution` status can be resolved.\n\n> \U0001F6A7 **Authentication**\n> \n> All BigPanda\
        \ APIs require Bearer Token Authorization in the call headers.\n>\n> This API uses the User API Key type of Authorization\
        \ token.\n\n> ❗ **Rate limitations**\n> \n> To maintain quality of service, the Biggy API is limited to 100 requests\
        \ per minute. Additional requests will return a 429 response code and the request will need to be retried."
      tags:
      - Major Incident Management
      parameters:
      - name: executionId
        in: path
        description: Unique identifier of the MIM execution. (24 character string)
        required: true
        example: 665b2c3d4e5f6a7b8c9d0e1f
        schema:
          type: string
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                reason:
                  type: string
                  description: Reason for the resolution.
                  examples:
                  - Root cause identified and fix deployed. Payments restored.
              x-apidog-orders:
              - reason
            example: "curl -sS -X POST \"https://api.biggy.io/mim/executions/:executionId/resolve\" \\\r\n  -H \"Authorization:\
              \ Bearer your-api-key\" \\\r\n  -H \"Content-Type: application/json\" \\\r\n  -d '{\r\n    \"reason\": \"Root\
              \ cause identified and fix deployed. Payments restored.\"\r\n}'"
      responses:
        '200':
          x-apidog-ordering: 0
          description: ''
          content:
            application/json:
              schema:
                type: object
                properties:
                  executionId:
                    type: string
                    description: Unique identifier of the MIM execution.
                    examples:
                    - 665b2c3d4e5f6a7b8c9d0e1f
                  status:
                    type: string
                    description: Status of the MIM execution.
                    examples:
                    - active
                  mimName:
                    type: string
                    description: Name of the inicdent.
                    examples:
                    - Payments Outage 2026-03-11
                  templateId:
                    type: string
                    description: Unique identifier of the MIM template.
                    examples:
                    - 665a1b2c3d4e5f6a7b8c9d0e
                  createdAt:
                    type: string
                    description: Date and time the execution was created.
                    examples:
                    - '2026-03-11T22:30:00.000Z'
                  createdBy:
                    type: object
                    properties:
                      system:
                        type: string
                        description: Who created the MIM execution.
                        examples:
                        - user
                    x-apidog-orders:
                    - system
                  communicationEntities:
                    type: array
                    items:
                      type: string
                    description: Communication entities associated with the MIM execution.
                  actions:
                    type: array
                    items:
                      type: string
                    description: Actions associated with the MIM execution.
                x-apidog-orders:
                - executionId
                - status
                - mimName
                - templateId
                - createdAt
                - createdBy
                - communicationEntities
                - actions
          headers: {}
          x-apidog-name: ''
        '400':
          x-apidog-ordering: 1
          description: ''
          content:
            application/json:
              schema:
                type: object
                properties:
                  statusCode:
                    type: integer
                    description: Status code associated with the error.
                    examples:
                    - 400
                  error:
                    type: string
                    description: Error type.
                    examples:
                    - MimValidationError
                  message:
                    type: string
                    description: Error message.
                    examples:
                    - Cannot resolve execution in terminal status completed
                x-apidog-orders:
                - statusCode
                - error
                - message
          headers: {}
          x-apidog-name: ''
        '404':
          x-apidog-ordering: 2
          description: ''
          content:
            application/json:
              schema:
                type: object
                properties:
                  statusCode:
                    type: integer
                    description: Status code associated with the error.
                    examples:
                    - 404
                  error:
                    type: string
                    description: Type of error.
                    examples:
                    - MimNotFoundError
                  message:
                    type: string
                    description: Error message.
                    examples:
                    - Execution not found.
                x-apidog-orders:
                - statusCode
                - error
                - message
          headers: {}
          x-apidog-name: ''
      x-publication-status: live
      x-run-in-apidog: https://app.apidog.com/web/project/1203004/apis/api-37769967-run
      x-source-url: https://api-docs.bigpanda.io/resolve-a-mim-execution-37769967e0.md
      x-source-page: Resolve a MIM execution
  /mim/executions/{executionId}:
    get:
      summary: Retrieve MIM Execution Details
      deprecated: false
      description: "Returns full details of a single MIM execution, including all communication entities and action statuses.\n\
        \n> \U0001F6A7 **Authentication**\n> \n> All BigPanda APIs require Bearer Token Authorization in the call headers.\n\
        >\n> This API uses the User API Key type of Authorization token.\n\n> ❗ **Rate limitations**\n> \n> To maintain quality\
        \ of service, the Biggy API is limited to 100 requests per minute. Additional requests will return a 429 response\
        \ code and the request will need to be retried."
      tags:
      - Major Incident Management
      parameters:
      - name: executionId
        in: path
        description: Unique identifier of the MIM execution. (24 character string).
        required: true
        example: 665b2c3d4e5f6a7b8c9d0e1f
        schema:
          type: string
      responses:
        '200':
          x-apidog-ordering: 0
          description: ''
          content:
            application/json:
              schema:
                type: object
                properties:
                  executionId:
                    type: string
                    description: Unique identififer of the MIM execution.
                    examples:
                    - 665b2c3d4e5f6a7b8c9d0e1f
                  status:
                    type: string
                    description: Status of the MIM execution.
                    examples:
                    - active
                  mimName:
                    type: string
    

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