> ## 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. # Bulk-change incident status > Apply the same status change to up to 50 incidents. Each is applied independently; incidents that cannot take the transition are skipped and reported in the results rather than failing the call. ## OpenAPI ````yaml /api/specs/incident-management-api.json post /incident-management/v1/incidents/bulk/status 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/bulk/status: post: tags: - Incidents summary: Bulk-change incident status description: >- Apply the same status change to up to 50 incidents. Each is applied independently; incidents that cannot take the transition are skipped and reported in the results rather than failing the call. requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/BulkStatusParams' responses: '200': description: Per-incident results plus applied/skipped tallies. content: application/json: schema: type: object properties: data: $ref: '#/components/schemas/IncidentBulkStatusResult' '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: - write:incident components: schemas: BulkStatusParams: type: object description: >- Apply the same status change to up to 50 incidents. Each is applied independently and may be skipped. properties: incidentIds: type: array items: type: string minItems: 1 maxItems: 50 status: type: string description: >- The target status to apply. Must be a transition target — NEW and MERGED are not accepted. enum: - INVESTIGATING - MITIGATING - WAITING_ON_OEM - POST_MORTEM - RESOLVED reason: type: string maxLength: 10000 resolutionNotes: type: string maxLength: 10000 description: Required when status is RESOLVED. changedByUserId: type: string description: >- NetworkUser id of the acting Support Operator. Required on every write; attributes the change. networkId: type: string description: >- Network id. Required for machine (M2M) callers whose token carries no network claim; ignored when the token has one. required: - incidentIds - status - changedByUserId IncidentBulkStatusResult: type: object description: >- The outcome of a bulk status change: a per-incident result plus applied/skipped tallies. properties: results: type: array items: type: object properties: incidentId: type: string applied: type: boolean fromStatus: $ref: '#/components/schemas/IncidentStatus' toStatus: $ref: '#/components/schemas/IncidentStatus' skipReason: type: string description: Why an incident was skipped, when applied is false. enum: - NOT_FOUND - ALREADY_MERGED - INVALID_TRANSITION - FAILED required: - incidentId - applied appliedCount: type: integer skippedCount: type: integer required: - results - appliedCount - skippedCount 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 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 ````