Skip to main content
POST
Process exception callback

Authorizations

X-Callback-Token
string
header
required

Opaque bearer token authenticating an external system's inbound exception callback.

Headers

X-Callback-Token
string
required

Opaque bearer token authenticating the external system

X-Idempotency
string
required

Idempotency key for deduplication

Path Parameters

exceptionId
string<uuid>
required

The unique identifier of the exception. Exception ID (UUID)

Example:

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

Body

application/json

Callback payload from external system

assignee
string
required

Assignee identifier (required when status is ASSIGNED)

Example:

"user@example.com"

callbackType
string
required

Type of callback (e.g. status_update, assignment)

Example:

"status_update"

dueAt
string | null
required

Due date for resolution as an RFC 3339 timestamp

Example:

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

externalIssueId
string
required

Issue ID in the external system

Minimum string length: 1
Example:

"RECON-1234"

externalSystem
string
required

External system identifier (e.g. JIRA, SERVICENOW, WEBHOOK)

Minimum string length: 1
Example:

"JIRA"

payload
object
required

Arbitrary payload from the external system

resolutionNotes
string
required

Optional resolution notes

Example:

"Resolved by external agent"

status
string
required

Target status for the exception (e.g. ASSIGNED, RESOLVED)

Minimum string length: 1
Example:

"RESOLVED"

updatedAt
string | null
required

External system timestamp as an RFC 3339 timestamp

Example:

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

Response

Callback processed successfully.

status
string
required

Processing status of the callback (the handler always returns "accepted" on success)

Example:

"accepted"