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

# Get Incident

> A single uptime / SSL / DNS / expiry incident by its identifier, including its contributing factors, linked remediation tasks, and the domain it affects. Incident identifiers come from the domain situation endpoints.


A single uptime / SSL / DNS / expiry incident by its identifier, including its contributing factors, linked remediation tasks, and the domain it affects. Incident identifiers come from the domain situation endpoints.


## OpenAPI

````yaml openapi/traffic-health.yaml get /networks/traffic/incidents/{incidentIdentifier}
openapi: 3.0.3
info:
  title: Everflow Network API - Traffic Health
  description: >
    Read endpoints for Traffic Health — the operational health of the domains
    and hosting IPs behind your tracking and conversion links. Surfaces uptime /
    SSL / DNS / expiry incidents, blocklist reputation, the remediation tasks
    that need your attention, and per-domain assignment summaries.


    Traffic Health has two tiers. The capabilities available to a network are
    reported by `GET /networks/traffic/access`. Endpoints marked **Traffic
    Health Premium** (domain and IP blocklist reputation) require the premium
    package; on a network without it they return an authorization error rather
    than data.


    For how these incidents and reputation flags work, see [Traffic Health:
    Incidents & Reputation
    Management](https://helpdesk.everflow.io/customer/traffic-health-incidents-and-reputation-management).
  version: 1.0.0
servers:
  - url: https://api.eflow.team/v1
security: []
tags:
  - name: Traffic Health
paths:
  /networks/traffic/incidents/{incidentIdentifier}:
    get:
      tags:
        - Traffic Health
      summary: Get Incident
      description: >
        A single uptime / SSL / DNS / expiry incident by its identifier,
        including its contributing factors, linked remediation tasks, and the
        domain it affects. Incident identifiers come from the domain situation
        endpoints.
      parameters:
        - in: path
          name: incidentIdentifier
          required: true
          schema:
            type: string
          description: The incident identifier (e.g. `WO8429BKVJ4E7CPE`).
      responses:
        '200':
          description: ''
          content:
            application/json:
              example:
                network_id: 1
                url: track.acme.com
                network_tracking_domain_id: 25004
                network_conversion_domain_id: 0
                identifier: WO8429BKVJ4E7CPE
                type: certificate_issue
                status: active
                time_created: 1781746780
                time_saved: 1782437980
                time_last_observed: 1782437980
                time_resolved: 0
                relationship:
                  factors: []
                  tasks: []
              schema:
                $ref: '#/components/schemas/Incident'
      security:
        - API Key: []
components:
  schemas:
    Incident:
      type: object
      properties:
        network_id:
          type: integer
        url:
          type: string
        network_tracking_domain_id:
          type: integer
        network_conversion_domain_id:
          type: integer
        identifier:
          type: string
        type:
          type: string
          description: Incident type (uptime / SSL / DNS / expiry category).
        status:
          type: string
          description: '`active` or `resolved`.'
        time_created:
          type: integer
        time_saved:
          type: integer
        time_last_observed:
          type: integer
        time_resolved:
          type: integer
          description: Unix seconds; `0` while the incident is active.
        relationship:
          type: object
          properties:
            factors:
              type: array
              description: Contributing signals for the incident.
              items:
                type: object
            tasks:
              type: array
              description: Remediation tasks linked to the incident.
              items:
                $ref: '#/components/schemas/Task'
    Task:
      type: object
      properties:
        network_id:
          type: integer
        url:
          type: string
        network_tracking_domain_id:
          type: integer
        network_conversion_domain_id:
          type: integer
        identifier:
          type: string
        type:
          type: string
          description: Task type (e.g. `renew_domain`).
        category:
          type: string
          description: Urgency category (e.g. `reactive`).
        status:
          type: string
          description: Task status (e.g. `to_do`).
        assignment:
          type: string
          description: Who the task is assigned to (e.g. `customer`).
        title:
          type: string
        description:
          type: string
        time_created:
          type: integer
        time_completed:
          type: integer
          description: Unix seconds; `0` while the task is open.
        relationship:
          type: object
          properties:
            incident_identifier:
              type: string
              description: The incident that generated the task.
  securitySchemes:
    API Key:
      type: apiKey
      in: header
      name: X-Eflow-Api-Key

````