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

# List an incident's status history

> The incident's status transitions, oldest first, keyset-paginated.



## OpenAPI

````yaml /api/specs/incident-management-api.json get /incident-management/v1/incidents/{id}/history
openapi: 3.0.0
info:
  title: Lynkwell API
  version: 1.377.0
  description: API Documentation for the Incident Management Service
servers:
  - url: https://api.lynkwell.com
security: []
tags: []
paths:
  /incident-management/v1/incidents/{id}/history:
    get:
      tags:
        - Incidents
      summary: List an incident's status history
      description: The incident's status transitions, oldest first, keyset-paginated.
      parameters:
        - in: path
          name: id
          required: true
          schema:
            type: string
        - in: query
          name: limit
          schema:
            type: string
            pattern: ^[1-9][0-9]?$|^100$
        - in: query
          name: startingAfter
          schema:
            type: string
        - in: query
          name: networkId
          schema:
            type: string
      responses:
        '200':
          description: A page of status-history entries.
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    type: object
                    properties:
                      items:
                        type: array
                        items:
                          $ref: '#/components/schemas/IncidentStatusHistoryEntry'
                      hasMore:
                        type: boolean
                    required:
                      - items
                      - hasMore
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/IncidentBadRequestError'
        '401':
          description: Missing or invalid token
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/IncidentUnauthorizedError'
        '403':
          description: Insufficient scope. The body is a plain-text message, not JSON.
          content:
            text/plain:
              schema:
                type: string
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/IncidentInternalServerError'
      security:
        - oauth2:
            - read:incident
components:
  schemas:
    IncidentStatusHistoryEntry:
      type: object
      description: One status transition in an incident's history.
      properties:
        id:
          type: string
        networkId:
          type: string
        incidentId:
          type: string
        fromStatus:
          $ref: '#/components/schemas/IncidentStatus'
        toStatus:
          $ref: '#/components/schemas/IncidentStatus'
        changedByUserId:
          type: string
          description: NetworkUser id; present only when changedByType is USER.
        changedByType:
          $ref: '#/components/schemas/ActorType'
        reason:
          type: string
        timestamp:
          type: string
          format: date-time
      required:
        - id
        - networkId
        - incidentId
        - toStatus
        - changedByType
        - timestamp
    IncidentBadRequestError:
      type: object
      description: The response body for a 400 request.
      properties:
        type:
          type: string
          enum:
            - BAD_REQUEST
        code:
          type: string
          description: >-
            A stable machine-readable error code identifying the specific
            validation failure.
        message:
          type: string
      required:
        - type
        - code
        - message
    IncidentUnauthorizedError:
      type: object
      description: The response body for a 401 request (missing or invalid token).
      properties:
        message:
          type: string
      required:
        - message
    IncidentInternalServerError:
      type: object
      description: The response body for a 500 request.
      properties:
        type:
          type: string
          enum:
            - INTERNAL_ERROR
        message:
          type: string
      required:
        - type
        - message
    IncidentStatus:
      type: string
      description: >-
        Lifecycle state. NEW, INVESTIGATING, MITIGATING, WAITING_ON_OEM,
        POST_MORTEM, RESOLVED, MERGED. RESOLVED and MERGED are terminal; MERGED
        is set only by a merge, never by a status update.
      enum:
        - NEW
        - INVESTIGATING
        - MITIGATING
        - WAITING_ON_OEM
        - POST_MORTEM
        - RESOLVED
        - MERGED
    ActorType:
      type: string
      description: >-
        Who performed an attributed action. USER = a person (their NetworkUser
        id is on the row). SYSTEM = an automated action by the platform (e.g. a
        trigger opening an incident, or auto-resolution). API is reserved and
        not currently produced.
      enum:
        - USER
        - SYSTEM
        - API
  securitySchemes:
    oauth2:
      type: oauth2
      description: OAuth2 Client Credentials Flow
      flows:
        clientCredentials:
          tokenUrl: https://lynkwell-prod.us.auth0.com/oauth/token
          scopes:
            read:asset: Retrieve assets
            write:asset: Create and update assets
            read:assetgroup: Retrieve asset groups
            write:assetgroup: Create and update asset groups
            read:assetstatus: Retrieve asset statuses
            read:chargingstationmodel: Retrieve charging station models
            write:chargingstationmodel: Create and update charging station models
            write:network: Create and update networks
            write:sitepartner: Create and update site partners
            read:sitepartner: Retrieve site partners
            write:sitepartneruser: Create and update site partner users
            read:sitepartneruser: Retrieve site partner users
            read:networkaccessprofile: Retrieve network access profiles
            write:paymentprofile: Create payment profile
            write:onboardinglink: Create an onboarding link
            read:invoice: Retrieve an invoice
            write:session: Create or update a session
            read:session: Retrieve a session
            write:ticket: Create a ticket
            write:verificationcode: Send and confirm verification codes
            write:driver: Create and update drivers
            read:driver: Retrieve drivers
            write:token: Create and update tokens
            read:token: Retrieve tokens
            read:tokenvalue: Retrieve token by ID including its value
            write:invitecode: Create and update invite codes
            write:invitation: Create and update invitations
            read:invitation: Retrieve invitations
            read:payment_terminals_payment: Read payments from payment terminal
            abort:session: Abruptly end session
            read:paymentprofile: Retrieve payment profile from payment terminal
            write:ocpp: Sends request over OCPP
            write:ocpp.raw_request: Sends raw request over OCPP
            write:notification.email: Create and update email
            read:invoiceitem: Retrieve invoice item
            read:subscription: Retrieve subscription
            write:plugandcharge_enrollment: Update Plug and Charge enrollment status
            write:projects: Create and update projects
            read:projects: Retrieve projects
            write:project_stations: Create and update project stations
            write:panel: Create and update panels.
            read:panel: Retrieve panels.
            write:webhooks: Create, update, and delete webhooks
            read:webhooks: Retrieve webhooks
            read:incident: Retrieve incidents and their sub-resources
            write:incident: Create, update, comment on, merge, split, and link incidents

````