> ## Documentation Index
> Fetch the complete documentation index at: https://docs.statusstack.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Get a specific incident



## OpenAPI

````yaml /openapi/api-docs.yaml get /v1/incidents/{incident_id}
openapi: 3.0.3
info:
  title: StatusStack API
  description: >
    API for managing status monitoring, incidents, stacks, and website
    monitoring.


    You can import this specification directly into Postman, Insomnia or any
    other

    OpenAPI-compatible client.


    Only the operations documented here are part of the supported public API.
    Any other

    endpoint is unstable and may change without a version bump.
  version: 1.4.0
  contact:
    name: StatusStack Support
    url: https://statusstack.com/support
servers:
  - url: https://statusstack.com/api
    description: Production server
security: []
paths:
  /v1/incidents/{incident_id}:
    parameters:
      - name: incident_id
        in: path
        required: true
        schema:
          type: string
          format: uuid
    get:
      summary: Get a specific incident
      responses:
        '200':
          description: Incident details
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Incident'
      security:
        - bearerAuth: []
components:
  schemas:
    Incident:
      type: object
      properties:
        id:
          type: string
          format: uuid
        source_id:
          type: string
          format: uuid
        title:
          type: string
        status:
          type: string
          enum:
            - investigating
            - identified
            - monitoring
            - resolved
        impact:
          type: string
          enum:
            - none
            - minor
            - major
            - critical
        started_at:
          type: string
          format: date-time
        resolved_at:
          type: string
          format: date-time
        updates:
          type: array
          items:
            $ref: '#/components/schemas/IncidentUpdate'
        affected_components:
          type: array
          items:
            $ref: '#/components/schemas/Component'
        created_at:
          type: string
          format: date-time
        updated_at:
          type: string
          format: date-time
    IncidentUpdate:
      type: object
      properties:
        id:
          type: string
          format: uuid
        incident_id:
          type: string
          format: uuid
        status:
          type: string
          enum:
            - investigating
            - identified
            - monitoring
            - resolved
        message:
          type: string
        created_at:
          type: string
          format: date-time
    Component:
      type: object
      properties:
        id:
          type: string
          format: uuid
        name:
          type: string
        source_id:
          type: string
          format: uuid
        latest_status:
          type: string
          enum:
            - operational
            - degraded
            - degraded_performance
            - partial_outage
            - major_outage
            - maintenance
            - unknown
          description: >
            The component's display status. `degraded_performance` is returned
            as-is; every

            other degraded state maps to `degraded`. A status that cannot be
            classified

            becomes `unknown` rather than being reported as healthy.
        description:
          type: string
        created_at:
          type: string
          format: date-time
        updated_at:
          type: string
          format: date-time
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: >
        StatusStack authenticates requests with API keys, created via the
        dashboard with

        granular permissions (read, write, delete, admin, *).


        API keys support version compatibility:

        - v1 keys: Can only access v1 endpoints

        - v2 keys: Can access both v1 and v2 endpoints


        Available permissions:

        - `read`: View resources (GET requests)

        - `write`: Create and update resources (POST, PUT requests)

        - `delete`: Delete resources (DELETE requests)

        - `admin`: Administrative access to all resources

        - `*`: Wildcard permission (all actions allowed)

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.