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

# Resolve a Signal Incident

> Closes an open Signal Incident, recording `resolverUserId` as the person who resolved it, exactly as resolving it in the ProVision portal would — the same status and timestamp are written and the incident’s Slack messages are updated to show it was resolved. Idempotent: resolving an already-resolved incident succeeds, changes nothing, and keeps the original resolver and resolution time. An incident that was canceled (superseded by a newer one) cannot be resolved and is rejected with 400. Requires the `signalIncident:write` scope.



## OpenAPI

````yaml /openapi.yaml post /v1/signal-incident/{id}/resolve
openapi: 3.1.0
info:
  title: ProVision Public API
  version: 1.0.0
  description: >-
    Use the ProVision Public API to integrate with ProVision conversations,
    clients, users, and addresses. All endpoints accept and return JSON, are
    authenticated with an `x-api-key` header, and are scoped to a single partner
    tenant.
  contact:
    email: support@onevisionresources.com
    name: OneVision Resources Support
  license:
    name: Proprietary
servers:
  - url: https://connect.provisionapp.io
    description: Production
security: []
paths:
  /v1/signal-incident/{id}/resolve:
    post:
      tags:
        - signal-incident
      summary: Resolve a Signal Incident
      description: >-
        Closes an open Signal Incident, recording `resolverUserId` as the person
        who resolved it, exactly as resolving it in the ProVision portal would —
        the same status and timestamp are written and the incident’s Slack
        messages are updated to show it was resolved. Idempotent: resolving an
        already-resolved incident succeeds, changes nothing, and keeps the
        original resolver and resolution time. An incident that was canceled
        (superseded by a newer one) cannot be resolved and is rejected with 400.
        Requires the `signalIncident:write` scope.
      operationId: resolveSignalIncident
      parameters:
        - schema:
            type: string
            format: uuid
            example: 57f2d879-20f8-4106-9abb-44fa099e0448
          required: true
          name: id
          in: path
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ResolveSignalIncidentBody'
      responses:
        '200':
          description: The incident in its resolved state
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/SignalIncident'
        '400':
          description: Bad Request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '401':
          description: Unauthorized
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '403':
          description: Forbidden
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '404':
          description: Not Found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '422':
          description: Unprocessable Entity
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
      security:
        - OpenApiKeyAuth: []
components:
  schemas:
    ResolveSignalIncidentBody:
      type: object
      properties:
        resolverUserId:
          allOf:
            - $ref: '#/components/schemas/UserId'
            - description: >-
                Platform user recorded as the resolver. Must belong to your
                partner and be active. Newer ids are `ovuid-<uuid>`; legacy
                users may have bare (e.g. numeric) ids.
      required:
        - resolverUserId
      additionalProperties: false
    SignalIncident:
      type: object
      properties:
        id:
          type: string
          format: uuid
        conversationId:
          type: string
          format: uuid
        status:
          $ref: '#/components/schemas/SignalIncidentStatus'
        urgency:
          $ref: '#/components/schemas/SignalIncidentUrgency'
        notificationTargetType:
          $ref: '#/components/schemas/SignalIncidentNotificationTargetType'
        createdAt:
          type: string
          format: date-time
        updatedAt:
          type: string
          format: date-time
        resolvedAt:
          type:
            - string
            - 'null'
          format: date-time
          description: When an agent resolved the incident. Null while it is unresolved.
        resolverId:
          type:
            - string
            - 'null'
          description: >-
            Id of the user who resolved the incident. May reference a ProVision
            internal user, who is not visible through `/v1/user/list`.
          example: ovuid-2b6d4d8e-9f1a-4b2c-8d4e-5f6011223344
      required:
        - id
        - conversationId
        - status
        - urgency
        - notificationTargetType
        - createdAt
        - updatedAt
        - resolvedAt
        - resolverId
      additionalProperties: false
    ErrorResponse:
      type: object
      properties:
        error:
          $ref: '#/components/schemas/ApiError'
      required:
        - error
    UserId:
      type: string
      minLength: 1
      description: >-
        Platform user id. Newer ids are `ovuid-<uuid>`; legacy users may have
        bare (e.g. numeric) ids.
      example: ovuid-2b6d4d8e-9f1a-4b2c-8d4e-5f6011223344
    SignalIncidentStatus:
      type: string
      enum:
        - pending
        - canceled
        - resolved
        - ignored
    SignalIncidentUrgency:
      type:
        - string
        - 'null'
      enum:
        - life_safety
        - urgent
        - normal
        - low
        - null
    SignalIncidentNotificationTargetType:
      type:
        - string
        - 'null'
      enum:
        - partner
        - platform
        - null
      description: >-
        Who was notified about this incident. `partner` means the partner's own
        on-call agents; `platform` means ProVision internal staff.
    ApiError:
      type: object
      properties:
        code:
          type: string
          description: Machine-readable error code
          example: NOT_FOUND
        message:
          type: string
          description: Human-readable error description
      required:
        - code
        - message
  securitySchemes:
    OpenApiKeyAuth:
      type: apiKey
      in: header
      name: x-api-key
      description: Send the API key in the x-api-key header.

````

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