v1

latestOpenAPI 3.1.02026-07-263644911022.4 KB
Exception

Assign an exception

Assigns a single exception to a user. Mirrors the bulk-assign auth and validation but acts on exactly one exception addressed by path. Returns the updated exception.

post/v1/exceptions/{exceptionId}/assign

Path parameters

exceptionIdstring uuid required

Exception ID (UUID)

Example:550e8400-e29b-41d4-a716-446655440000

Exception ID (UUID)

Request body

assigneestring required

User to assign the exception to

Example request

{
  "assignee": "user@example.com"
}

Response

OK

assignedTostring

User the exception is assigned to

createdAtstring

Creation timestamp in RFC3339 format

dueAtstring

Due date for resolution in RFC3339 format

externalIssueIdstring

External issue ID in the external system

externalSystemstring

External system where exception was dispatched

idstring

Unique identifier for the exception

reasonstring

Reason the exception was raised

resolutionNotesstring

Resolution notes when resolved

resolutionReasonstring

Reason for the resolution

resolutionType'FORCE_MATCH' | 'ADJUST_ENTRY'

Type of resolution applied

severity'LOW' | 'MEDIUM' | 'HIGH' | 'CRITICAL'

Severity level

status'OPEN' | 'ASSIGNED' | 'PENDING_RESOLUTION' | 'RESOLVED'

Current status

transactionIdstring

Transaction ID this exception is for

updatedAtstring

Last update timestamp in RFC3339 format

Example response

{
  "assignedTo": "user@example.com",
  "createdAt": "2025-01-15T10:30:00.000Z",
  "dueAt": "2025-01-20T10:30:00.000Z",
  "externalIssueId": "RECON-1234",
  "externalSystem": "JIRA",
  "id": "019c96a0-10d2-7134-ba5f-664142ee7052",
  "reason": "Amount mismatch detected",
  "resolutionNotes": "Resolved via force match",
  "resolutionReason": "BUSINESS_DECISION",
  "resolutionType": "FORCE_MATCH",
  "severity": "HIGH",
  "status": "OPEN",
  "transactionId": "019c96a0-10ce-75fc-a273-dc799079a99c",
  "updatedAt": "2025-01-15T10:30:00.000Z"
}