Get exception
Use this endpoint to retrieve the details of a specific exception by its identifier.
Autorizações
Bearer token authentication (format: "Bearer {token}")
Cabeçalhos
A unique identifier for tracing the request across services.
Parâmetros de caminho
Exception ID Exception ID (UUID)
"550e8400-e29b-41d4-a716-446655440000"
Resposta
Indicates that the request was successful and the response contains the expected data.
Creation timestamp as an RFC 3339 timestamp
"2025-01-15T10:30:00Z"
Unique identifier for the exception (UUID)
"550e8400-e29b-41d4-a716-446655440000"
Severity level: LOW and MEDIUM are informational, HIGH needs prompt review, CRITICAL requires immediate action
LOW, MEDIUM, HIGH, CRITICAL "HIGH"
Lifecycle status: OPEN (unhandled), ASSIGNED (owned by a user), PENDING_RESOLUTION (a resolution is in flight), RESOLVED (closed out)
OPEN, ASSIGNED, PENDING_RESOLUTION, RESOLVED "OPEN"
Identifier of the transaction this exception was raised for (UUID)
"550e8400-e29b-41d4-a716-446655440001"
Last update timestamp as an RFC 3339 timestamp
"2025-01-15T10:30:00Z"
Enrichment: the exception transaction's amount as a decimal string in the transaction's currency. Present on list rows and get-by-id when the transaction still exists.
"1250.50"
User the exception is currently assigned to
"user@example.com"
Enrichment: id of the reconciliation context the exception's source belongs to (UUID). Present on list rows and get-by-id when the transaction and source still exist; powers the global triage queue's context attribution.
"550e8400-e29b-41d4-a716-446655440004"
Enrichment: ISO 4217 currency code of the exception transaction's amount. Present on list rows and get-by-id when the transaction still exists.
"USD"
Resolution due date as an RFC 3339 timestamp
"2025-01-20T10:30:00Z"
Issue identifier in the external system, when dispatched
"RECON-1234"
External system the exception was dispatched to, when applicable
"JIRA"
Reason the exception was originally raised
"Amount mismatch detected"
Free-text notes captured when the exception was resolved
"Resolved via force match"
Reason code recorded for the resolution
"BUSINESS_DECISION"
How the exception was resolved.
"FORCE_MATCH"
When the exception was resolved, as an RFC 3339 timestamp. Present only for RESOLVED exceptions.
"2025-01-15T12:00:00Z"
Principal that resolved the exception (JWT sub, or 'system' for automated callback resolutions). Empty until resolved or when the resolving path is un-attributed.
"user@example.com"
Identifier of the match run that LATEST surfaced this exception (UUID). Refreshed on every re-run that re-surfaces the break, so it names the most recent run that touched it; powers the run-precise jump from a run to its exceptions. Absent for legacy rows written before run linkage and for ingestion-minted duplicate-transaction breaks (not produced by a match run).
"550e8400-e29b-41d4-a716-446655440002"
Settlement figures for a fee break (expected vs credited and the signed difference), derived from the live fee-variance snapshot recorded for the exception's transaction. Present on get-by-id only, and only when the snapshot and the transaction amount are both available in the same currency.
Enrichment: id of the reconciliation source the exception transaction belongs to (UUID). Present on list rows and get-by-id when the transaction still exists.
"550e8400-e29b-41d4-a716-446655440003"
Enrichment: display name of the reconciliation source. Present on get-by-id when the transaction and its source still exist.
"Bank feed"
Enrichment: the exception transaction's value date as an RFC 3339 timestamp. Present on list rows and get-by-id when the transaction still exists.
"2025-01-14T00:00:00Z"