Skip to main content
POST
Add a comment to an exception

Authorizations

Authorization
string
header
required

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

Headers

X-Request-Id
string

A unique identifier for tracing the request across services.

X-Idempotency
string

Optional idempotency key for safe retries. Matcher reads the key only from this header, and only when you send one. A request that carries a key only in X-Idempotency-Key or Idempotency-Key is refused with 400 (MTCH-0015), and nothing is processed. If the same key is sent again and the original request was already processed, the stored response is returned with X-Idempotency-Replayed: true. A malformed key returns 400, a key whose first request is still in progress returns 409, and an idempotency storage failure returns 500. These refusals are problem documents.

Path Parameters

exceptionId
string<uuid>
required

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

Example:

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

Body

application/json

Comment payload

content
string
required

Comment content

Required string length: 1 - 5000
Example:

"This transaction needs review by the finance team."

Response

Comment added successfully.

author
string
required

Author of the comment

Example:

"user@example.com"

content
string
required

Comment content

Example:

"This transaction needs review."

createdAt
string
required

Creation timestamp as an RFC 3339 timestamp

Example:

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

exceptionId
string
required

Identifier of the exception this comment belongs to (UUID)

Example:

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

id
string
required

Unique identifier for the comment (UUID)

Example:

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

updatedAt
string
required

Last update timestamp as an RFC 3339 timestamp

Example:

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