Skip to main content

Error format

Field definitions

  • type – A URI that identifies the error, built as https://errors.lerian.studio/v1/<code>.
  • title – The HTTP status text (for example, Bad Request).
  • status – The HTTP status code.
  • detail – A short description of this occurrence of the error. Use code to branch programmatically.
  • code – A stable product code that uniquely identifies the error (e.g., MTCH-0001). Useful for programmatic handling and support requests.
  • errors – (optional) A list with field-level validation details.

Field-level error details

When the request fails schema validation, Matcher returns 422 Unprocessable Entity with an errors array and no code. Examples:

General errors


These errors apply to all Matcher API endpoints. 400 403 404 409 413 422 500 503

Configuration errors


Matcher returns these errors for a problem in the reconciliation configuration (contexts, sources, field maps, match rules, fee rules, schedules). 400 404 409

Discovery errors


Matcher returns these errors for data source discovery and connection management. Discovery relies on Matcher’s embedded extraction engine. See Discovery for how it works. 400 404 409 422 503

Ingestion errors


Matcher returns these errors for transaction file upload and processing. 400 403 404 408 409 422 503

Matching errors


Matcher returns these errors for the reconciliation matching process. 400 403 409 422 503

Exception errors


Matcher returns these errors for exception handling, disputes, and callback processing. 404 409 422 429

Governance errors


Audit log and governance operations return the general errors, such as MTCH-0005 when an audit log, actor mapping, or archive does not exist.

Reporting errors


Report export operations return the general errors. An export job that does not exist returns MTCH-0005, a job that is not ready for download or has already finished returns MTCH-0007, a disabled export worker returns MTCH-0702, and unavailable object storage returns MTCH-0019. An expired export file returns 410 with no code.

Rate limit errors


Matcher limits how many requests each caller can send in a time window. A request over the limit returns 429 before it reaches the operation, with a flat body in which code is the number 429. The Retry-After header gives the number of seconds to wait before you retry.
When Matcher cannot reach the store that counts requests, it rejects the request with 503 and a flat body of the same shape:

Authentication errors


Access Manager checks the token and the caller’s permissions. A refusal from that check is not a problem object and carries no MTCH code. When Access Manager does not answer, Matcher answers 503. 401 403

Idempotency errors


Matcher returns these errors for a problem with idempotency key handling. 400 409 500