Skip to main content
POST
Ignore a transaction

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-Key
string

Optional idempotency key for safe retries. Also accepts Idempotency-Key as an alternative header name. If the same key is sent again and the original request was already processed, the cached response is returned with X-Idempotency-Replayed: true.

See Retries and idempotency for details.

Path Parameters

contextId
string<uuid>
required

The unique identifier of the reconciliation context.

transactionId
string
required

The unique identifier of the transaction.

Body

application/json

Ignore transaction request

Ignore transaction request

reason
string
required

Reason for ignoring the transaction

Example:

"Duplicate entry - already processed manually"

Response

Indicates that the request was successful and the response contains the expected data.

The response includes the X-Idempotency-Replayed header.

If the value is false, the request was just processed. If the value is true, the response is a replay of a previously processed request.

See Retries and idempotency for more details.

Ignore transaction response

amount
string

Transaction amount as string

Example:

"1000.50"

contextId
string

Context ID this transaction belongs to

Example:

"019c96a0-10a0-72d2-9fb0-2b7de8093182"

createdAt
string

Creation timestamp in RFC3339 format

Example:

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

currency
string

Currency code

Example:

"BRL"

date
string

Transaction date in RFC3339 format

Example:

"2025-01-15T00:00:00.000Z"

description
string

Description of the transaction

Example:

"Wire transfer from ABC Corp"

externalId
string

External identifier from the source system

Example:

"TXN-12345"

extractionStatus
enum<string>

Extraction status

Available options:
PENDING,
EXTRACTED,
FAILED
Example:

"EXTRACTED"

id
string

Unique identifier for the transaction

Example:

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

jobId
string

Job ID that ingested this transaction

Example:

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

sourceId
string

Source ID this transaction belongs to

Example:

"019c96a0-108c-7a74-8e31-3789daffe1ed"

status
enum<string>

Current matching status

Available options:
PENDING,
MATCHED,
UNMATCHED
Example:

"PENDING"