Ignore a transaction

Use this endpoint to mark a transaction as “Do Not Match” with a required reason. Only UNMATCHED transactions can be ignored.

POST /v1/imports/contexts/{contextId}/transactions/{transactionId}/ignore

Ignore a transaction

cURL

curl --request POST \
  --url https://matcher.sandbox.lerian.net/v1/imports/contexts/{contextId}/transactions/{transactionId}/ignore \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "reason": "Duplicate entry - already processed manually"
}
'

200

Example

{
  "amount": "1000.50",
  "contextId": "550e8400-e29b-41d4-a716-446655440000",
  "createdAt": "2025-01-15T10:30:00Z",
  "currency": "USD",
  "date": "2025-01-15T00:00:00Z",
  "dedupeKey": "v1|external_id=9:TXN-12345",
  "externalId": "TXN-12345",
  "extractionStatus": "COMPLETE",
  "id": "550e8400-e29b-41d4-a716-446655440000",
  "jobId": "550e8400-e29b-41d4-a716-446655440000",
  "sourceId": "550e8400-e29b-41d4-a716-446655440000",
  "status": "UNMATCHED",
  "description": "Wire transfer from ABC Corp",
  "metadata": {}
}

Autorizaciones

Authorization · string · header · requerido

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

Encabezados

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 (MTCH-0018), a key whose earlier attempt already ran but whose answer cannot be replayed returns 409 (MTCH-0022), and an idempotency storage failure returns 500. POST, PUT, PATCH and DELETE requests accept the header. These refusals are problem documents.

Parámetros de ruta

contextId · string<uuid> · requerido

The unique identifier of the reconciliation context. Context ID

transactionId · string<uuid> · requerido

The unique identifier of the transaction. Transaction ID

Cuerpo

application/json

Ignore transaction request

reason · string · requerido

Reason for ignoring the transaction

Minimum string length: 1

Ejemplo:

"Duplicate entry - already processed manually"

Respuesta

200

application/json

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

amount · string · requerido

Transaction amount as a decimal string in the transaction currency (precision preserved verbatim; never a float)

Ejemplo:

"1000.50"

contextId · string<uuid> · requerido

Reconciliation context this transaction belongs to

Ejemplo:

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

createdAt · string<date-time> · requerido

Creation timestamp (RFC 3339)

Ejemplo:

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

currency · string · requerido

ISO 4217 currency code of the amount

Ejemplo:

"USD"

date · string<date-time> · requerido

Transaction value date (RFC 3339)

Ejemplo:

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

dedupeKey · string · requerido

Read-only: the duplicate-key value this row was imported under, derived from the source's duplicate key declaration at import time. A source can change that declaration later, so this is the only place that says which identity THIS row carries. Prefixed v1 when the key spells out the fields it was derived from, v1h when those fields were hashed because the spelled-out key was too long to index.

Ejemplo:

"v1|external_id=9:TXN-12345"

externalId · string · requerido

External identifier carried from the source system

Ejemplo:

"TXN-12345"

extractionStatus · enum<string> · requerido

Field-extraction status: PENDING (queued), COMPLETE (fields parsed), FAILED (extraction error)

Opciones disponibles: PENDING, COMPLETE, FAILED

Ejemplo:

"COMPLETE"

id · string<uuid> · requerido

Unique identifier for the transaction

Ejemplo:

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

jobId · string<uuid> · requerido

Ingestion job that produced this transaction

Ejemplo:

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

sourceId · string<uuid> · requerido

Source this transaction belongs to

Ejemplo:

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

status · enum<string> · requerido

Matching status: UNMATCHED (no match found), MATCHED (reconciled), IGNORED (excluded from reconciliation by an operator), PENDING_REVIEW (imported under the blank-external-id review policy and awaiting an operator decision)

Opciones disponibles: UNMATCHED, MATCHED, IGNORED, PENDING_REVIEW

Ejemplo:

"UNMATCHED"

description · string

Free-text description carried from the source

Ejemplo:

"Wire transfer from ABC Corp"

metadata · object

Normalized source metadata: unmapped source columns the engine projects into composite match keys and FX-conversion inputs (e.g. counterparty, bank_transaction_code, fx_rate). Arbitrary key/value, tenant-scoped to the caller's own data.

Show child attributes