> ## 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.

# List Domain Situations

> Per-domain Traffic Health rollup for every monitored domain — each entry's overall state (`up` / `down`), domain type, and active/resolved incident and blocklist-incident counts (with vendor breakdowns). Send an empty object `{}` for all domains.


A per-domain Traffic Health rollup for every monitored domain — each domain's overall state plus its active and resolved incident and blocklist-incident counts. Send an empty object `{}` for all domains.


## OpenAPI

````yaml openapi/traffic-health.yaml post /networks/traffic/situation/domains
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/situation/domains:
    post:
      tags:
        - Traffic Health
      summary: List Domain Situations
      description: >
        Per-domain Traffic Health rollup for every monitored domain — each
        entry's overall state (`up` / `down`), domain type, and active/resolved
        incident and blocklist-incident counts (with vendor breakdowns). Send an
        empty object `{}` for all domains.
      requestBody:
        required: false
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/SituationFilter'
      responses:
        '200':
          description: ''
          content:
            application/json:
              example:
                entries:
                  - network_id: 1
                    url: track.acme.com
                    type: down
                    domain_type: tracking
                    active_incident_count: 2
                    resolved_incident_count: 1
                    active_blacklist_incident_count: 0
                    resolved_blacklist_incident_count: 0
              schema:
                type: object
                properties:
                  entries:
                    type: array
                    description: One entry per monitored domain.
                    items:
                      $ref: '#/components/schemas/DomainSituationShort'
      security:
        - API Key: []
components:
  schemas:
    SituationFilter:
      type: object
      description: Optional filters. Send an empty object `{}` for the default rollup.
    DomainSituationShort:
      type: object
      properties:
        network_id:
          type: integer
        url:
          type: string
        type:
          type: string
          description: Overall state of the domain (`up` or `down`).
        domain_type:
          type: string
          description: '`tracking`, `conversion`, or `third_party`.'
        active_incident_count:
          type: integer
        resolved_incident_count:
          type: integer
        active_blacklist_incident_count:
          type: integer
        resolved_blacklist_incident_count:
          type: integer
  securitySchemes:
    API Key:
      type: apiKey
      in: header
      name: X-Eflow-Api-Key

````