# List PIX Incidents

Confirmed PIX incidents in your scope, most recent first, paginated. An incident is confirmed
when the engine saw the same pattern in two consecutive 5-minute windows; a one-window blip never
appears here. Defaults to the last 7 days; the window between from and to cannot exceed 92 days.

Each incident tells you who (origin), how bad (severity), how sure we are about the
culprit (confidence) and how we know (originClass: OBSERVED = we saw the error,
INFERRED = deduced from the absence of what should have happened). summary is a diagnosis in
Portuguese written for you — never internal counts of other clients.

## One flat list

Unlike GET /health/pix, which splits the open incidents into incidents and externalIncidents,
this list is flat. Use origin.type to tell the two apart: CONNECTPSP and BANKING_PARTNER
are ours to fix, PAYER_INSTITUTION / PAYER_COHORT / PIX_SYSTEMIC are outside our control, and
MERCHANT is your own operation.

status is matched case-insensitively, so active,worsening works too. The response echoes back
the from and to actually applied, so you can log the window you really got.

This endpoint does not require DigitalSignature or X-Idempotency-Key.

Endpoint: GET /health/pix/incidents
Version: 2.2.0
Security: bearerAuth

## Header parameters:

  - `ApplicationToken` (string, required)
    Fixed GUID that uniquely identifies your integration. Provided during ConnectPSP onboarding.
    Example: "{{ApplicationToken}}"

## Query parameters:

  - `from` (string)
    Start of the window (ISO 8601, UTC). Default is to minus 7 days.

  - `to` (string)
    End of the window (ISO 8601, UTC). Default is now.

  - `status` (string)
    Comma-separated list. Accepted values: ACTIVE, WORSENING, RECOVERING, RESOLVED.
    Example: "ACTIVE,WORSENING"

  - `page` (integer)

  - `pageSize` (integer)

## Response 200 fields (application/json):

  - `items` (array)

  - `items.incidentId` (string)
    Stable id. Use it to correlate the webhooks and the detail endpoint.
    Example: "LIVE-202609081530-PAYER_INSTITUTION-00360305"

  - `items.origin` (object)
    Who the incident is attributed to.

  - `items.origin.type` (string)
    - CONNECTPSP — the platform as a whole.
- BANKING_PARTNER — a settlement partner you route through (id = ISPB).
- PAYER_INSTITUTION — a bank your payers pay from / your payees receive at (id = ISPB).
- PAYER_COHORT — a group of payer banks with the same behaviour.
- MERCHANT — your own operation (id = your customer id).
- PIX_SYSTEMIC — the PIX system itself (DICT, SPI).
    Enum: "CONNECTPSP", "BANKING_PARTNER", "PAYER_INSTITUTION", "PAYER_COHORT", "MERCHANT", "PIX_SYSTEMIC"

  - `items.origin.id` (string)
    Example: "00360305"

  - `items.origin.displayName` (string)
    Example: "CAIXA ECONOMICA FEDERAL"

  - `items.operation` (string)
    CASH_IN = payments you receive; CASH_OUT = withdrawals you send.
    Enum: "CASH_IN", "CASH_OUT"

  - `items.status` (string)
    ACTIVE = confirmed and ongoing. WORSENING = severity went up. RECOVERING = metrics back to
normal, waiting 3 windows to close. RESOLVED = closed.
    Enum: "ACTIVE", "WORSENING", "RECOVERING", "RESOLVED"

  - `items.severity` (string)
    How bad it is (never HEALTHY on an incident).
    Enum: "DEGRADED", "SEVERELY_DEGRADED", "UNAVAILABLE"

  - `items.confidence` (string)
    How sure the engine is about who is at fault — not about how bad it is.
    Enum: "LOW", "MEDIUM", "HIGH"

  - `items.originClass` (string)
    How the engine knows. OBSERVED = it saw the error itself. INFERRED = deduced from the absence of
what should have happened. CORROBORATED / CONFIRMED = backed by a second independent signal.
    Enum: "OBSERVED", "INFERRED", "CORROBORATED", "CONFIRMED", "UNKNOWN"

  - `items.startedAt` (string)
    Start of the first anomalous window (UTC).
    Example: "2026-09-08T15:30:00Z"

  - `items.detectedAt` (string)
    When the engine confirmed it (UTC).
    Example: "2026-09-08T15:37:59Z"

  - `items.recoveredAt` (string,null)
    When metrics returned to normal; null while ongoing.

  - `items.resolvedAt` (string,null)
    When the incident was closed; null while open.

  - `items.updatedAt` (string,null)
    Example: "2026-09-08T16:52:00Z"

  - `items.affectedPartners` (integer)
    How many settlement partners the incident reached.
    Example: 2

  - `items.summary` (string)
    Diagnosis in Portuguese, written for you. Never contains other clients' data.
    Example: "Forte evidência de degradação em cobranças pagas por clientes da CAIXA ECONOMICA FEDERAL: a conversão desses pagadores ficou em 78,5%, contra 93,0% esperados, enquanto 9 instituições de controle seguem normais."

  - `total` (integer)
    Total incidents matching the filter (all pages).
    Example: 3

  - `page` (integer)
    Example: 1

  - `pageSize` (integer)
    Example: 50

  - `from` (string)
    Effective start of the window (UTC).
    Example: "2026-09-01T16:53:00Z"

  - `to` (string)
    Effective end of the window (UTC).
    Example: "2026-09-08T16:53:00Z"

## Response 401 fields (application/problem+json):

  - `type` (string)
    URI identifying the error type. It can contain non-ASCII characters.
    Example: "https://doc.connectpsp.com/errors/duplicated-external-reference"

  - `title` (string)
    Short, human-readable summary.
    Example: "Referência Externa Duplicada"

  - `status` (integer)
    HTTP status code.
    Example: 409

  - `code` (string)
    Machine-readable error code for programmatic handling. Absent on the 401 for a missing or
invalid ApplicationToken.
    Example: "DUPLICATED_EXTERNAL_REFERENCE"

  - `detail` (string)
    Human-readable explanation of this specific occurrence.
    Example: "Já existe uma operação com o externalReference informado: withdraw_xyz789."

  - `errors` (object)
    Only on VALIDATION_ERROR. Field name → list of validation messages for that field.

  - `instance` (string)
    Request path where the error occurred. Present on some errors, such as INTERNAL_ERROR.

  - `traceId` (string)
    Only on INTERNAL_ERROR. Send it to support to locate the occurrence.

## Response 422 fields (application/problem+json):

  - `type` (string)
    URI identifying the error type. It can contain non-ASCII characters.
    Example: "https://doc.connectpsp.com/errors/duplicated-external-reference"

  - `title` (string)
    Short, human-readable summary.
    Example: "Referência Externa Duplicada"

  - `status` (integer)
    HTTP status code.
    Example: 409

  - `code` (string)
    Machine-readable error code for programmatic handling. Absent on the 401 for a missing or
invalid ApplicationToken.
    Example: "DUPLICATED_EXTERNAL_REFERENCE"

  - `detail` (string)
    Human-readable explanation of this specific occurrence.
    Example: "Já existe uma operação com o externalReference informado: withdraw_xyz789."

  - `errors` (object)
    Only on VALIDATION_ERROR. Field name → list of validation messages for that field.

  - `instance` (string)
    Request path where the error occurred. Present on some errors, such as INTERNAL_ERROR.

  - `traceId` (string)
    Only on INTERNAL_ERROR. Send it to support to locate the occurrence.

## Response 503 fields (application/problem+json):

  - `type` (string)
    URI identifying the error type. It can contain non-ASCII characters.
    Example: "https://doc.connectpsp.com/errors/duplicated-external-reference"

  - `title` (string)
    Short, human-readable summary.
    Example: "Referência Externa Duplicada"

  - `status` (integer)
    HTTP status code.
    Example: 409

  - `code` (string)
    Machine-readable error code for programmatic handling. Absent on the 401 for a missing or
invalid ApplicationToken.
    Example: "DUPLICATED_EXTERNAL_REFERENCE"

  - `detail` (string)
    Human-readable explanation of this specific occurrence.
    Example: "Já existe uma operação com o externalReference informado: withdraw_xyz789."

  - `errors` (object)
    Only on VALIDATION_ERROR. Field name → list of validation messages for that field.

  - `instance` (string)
    Request path where the error occurred. Present on some errors, such as INTERNAL_ERROR.

  - `traceId` (string)
    Only on INTERNAL_ERROR. Send it to support to locate the occurrence.