# Get PIX Incident

One incident with the evidence behind the verdict. Each piece of evidence names the metric, the
entity, the relative deviation from expected and the Z-score — never raw platform volumes.

Returns 404 when the incident does not exist or is outside your scope; the two cases are
deliberately indistinguishable.

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

Endpoint: GET /health/pix/incidents/{id}
Version: 2.2.0
Security: bearerAuth

## Header parameters:

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

## Path parameters:

  - `id` (string, required)
    The incidentId from the picture or from the list.
    Example: "LIVE-202609081530-PAYER_INSTITUTION-00360305"

## Response 200 fields (application/json):

  - `incident` (object)

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

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

  - `incident.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"

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

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

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

  - `incident.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"

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

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

  - `incident.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"

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

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

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

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

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

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

  - `incident.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."

  - `evidence` (array)
    The anomalous points behind the verdict, newest first.

  - `evidence.observedAt` (string)
    Start of the 5-minute window (UTC).
    Example: "2026-09-08T15:35:00Z"

  - `evidence.metric` (string)
    Example: "CONVERSION_MATURED"

  - `evidence.entity` (object)
    Who the incident is attributed to.

  - `evidence.deviationPercent` (number,null)
    (observed − expected) ÷ expected. -0.16 means 16 % below expected. null when there is no expectation.
    Example: -0.16

  - `evidence.z` (number)
    Robust Z-score of the deviation. |Z| ≥ 3 is an anomaly; the farther from 0, the clearer.
    Example: -4.2

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