Skip to main content
POST
Resolve an exception

Autorizações

Authorization
string
header
obrigatório

Bearer token authentication (format: "Bearer {token}")

Parâmetros de caminho

exceptionId
string<uuid>
obrigatório

Exception ID (UUID)

Exemplo:

"550e8400-e29b-41d4-a716-446655440000"

Corpo

application/json
resolution
string
obrigatório

Resolution type applied

Required string length: 1 - 255
Exemplo:

"ACCEPTED"

reason
string

Optional reason for the resolution

Maximum string length: 1000
Exemplo:

"Variance within tolerance"

Resposta

OK

Exception details

assignedTo
string

User the exception is assigned to

Exemplo:

"user@example.com"

createdAt
string

Creation timestamp in RFC3339 format

Exemplo:

"2025-01-15T10:30:00.000Z"

dueAt
string

Due date for resolution in RFC3339 format

Exemplo:

"2025-01-20T10:30:00.000Z"

externalIssueId
string

External issue ID in the external system

Exemplo:

"RECON-1234"

externalSystem
string

External system where exception was dispatched

Exemplo:

"JIRA"

id
string

Unique identifier for the exception

Exemplo:

"019c96a0-10d2-7134-ba5f-664142ee7052"

reason
string

Reason the exception was raised

Exemplo:

"Amount mismatch detected"

resolutionNotes
string

Resolution notes when resolved

Exemplo:

"Resolved via force match"

resolutionReason
string

Reason for the resolution

Exemplo:

"BUSINESS_DECISION"

resolutionType
enum<string>

Type of resolution applied

Opções disponíveis:
FORCE_MATCH,
ADJUST_ENTRY
Exemplo:

"FORCE_MATCH"

severity
enum<string>

Severity level

Opções disponíveis:
LOW,
MEDIUM,
HIGH,
CRITICAL
Exemplo:

"HIGH"

status
enum<string>

Current status

Opções disponíveis:
OPEN,
ASSIGNED,
PENDING_RESOLUTION,
RESOLVED
Exemplo:

"OPEN"

transactionId
string

Transaction ID this exception is for

Exemplo:

"019c96a0-10ce-75fc-a273-dc799079a99c"

updatedAt
string

Last update timestamp in RFC3339 format

Exemplo:

"2025-01-15T10:30:00.000Z"