Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt

Use this file to discover all available pages before exploring further.

Error format

{
   "code": "<error_code>",
   "title": "<error_title>",
   "message": "<error_message>"
}

Field definitions

  • code – A stable product code that uniquely identifies the error (e.g., MTCH-0001). Useful for programmatic handling and support requests.
  • title – A short, human-readable summary of the issue.
  • message – Detailed guidance to help you resolve the error.
  • details(optional) A structured object with additional context, such as field-level validation errors.
This structure ensures you always get actionable feedback when something doesn’t go as expected.

Field-level error details

For issues specific to individual fields, a details object provides additional context. Examples:
{
  "code": "MTCH-0001",
  "title": "Bad Request",
  "message": "The request body is invalid or malformed. Please verify the JSON format and try again.",
  "details": {
    "context_id": "context_id is a required field"
  }
}

General errors


These errors apply to all Matcher API endpoints.

400

codetitlemessage
MTCH-0001Bad RequestThe request body is invalid or malformed. Please verify the request format and try again.
MTCH-0011Bad RequestThe request failed. Please verify the request and try again.
MTCH-0013Bad RequestThe context ID is invalid. Please verify the ID format and try again.

401

codetitlemessage
MTCH-0003UnauthorizedThe request could not be authenticated. Please verify your credentials and try again.

403

codetitlemessage
MTCH-0004ForbiddenYou do not have permission to perform this action. Please verify your access level.
MTCH-0012ForbiddenThe reconciliation context is not active. Please activate the context before performing this operation.

404

codetitlemessage
MTCH-0005Not FoundThe requested resource does not exist. Please verify the ID and try again.

409

codetitlemessage
MTCH-0007ConflictThe request conflicts with the current state of the resource. Please verify and try again.

413

codetitlemessage
MTCH-0010Request Entity Too LargeThe uploaded file exceeds the maximum allowed size. Please reduce the file size and try again.

422

codetitlemessage
MTCH-0006Unprocessable EntityThe request was well-formed but could not be processed. Please verify the input data and try again.

429

codetitlemessage
MTCH-0009Too Many RequestsThe request rate limit has been exceeded. Please wait before retrying.

500

codetitlemessage
MTCH-0002Internal Server ErrorAn unexpected error occurred. Please try again later or contact support if the issue persists.

503

codetitlemessage
MTCH-0008Service UnavailableA required service is temporarily unavailable. Please try again later.
MTCH-0019Service UnavailableObject storage is temporarily unavailable. Please try again later.

Configuration errors


These errors are returned when there is an issue with the reconciliation configuration (contexts, sources, field maps, match rules, fee rules, schedules).

400

codetitlemessage
MTCH-0109Bad RequestA context name is required. Please provide a valid name and try again.

404

codetitlemessage
MTCH-0110Not FoundThe specified context was not found. Please verify the context ID and try again.
MTCH-0111Not FoundThe specified source was not found. Please verify the source ID and try again.
MTCH-0112Not FoundThe specified field map was not found. Please verify the field map ID and try again.
MTCH-0113Not FoundThe specified match rule was not found. Please verify the match rule ID and try again.
MTCH-0114Not FoundThe specified fee rule was not found. Please verify the fee rule ID and try again.
MTCH-0115Not FoundThe specified fee schedule was not found. Please verify the fee schedule ID and try again.
MTCH-0116Not FoundThe specified schedule was not found. Please verify the schedule ID and try again.

409

codetitlemessage
MTCH-0101ConflictA context with this name already exists. Please choose a different name and try again.
MTCH-0102ConflictA resource with this priority already exists. Please choose a different priority value and try again.
MTCH-0103ConflictThe resource is in an invalid state for this operation. Please verify its current state and try again.
MTCH-0104ConflictThe context has been archived. Please use an active context for this operation.
MTCH-0105ConflictThis resource cannot be deleted because it has an associated field map. Please remove the field map first.
MTCH-0106ConflictThis resource cannot be deleted because it has dependent resources. Please remove the dependent resources first.
MTCH-0107ConflictA resource with this priority already exists. Please choose a different priority value.
MTCH-0108ConflictThe fee schedule is currently in use and cannot be modified or deleted.

Discovery errors


These errors are returned during data source discovery and connection management.

400

codetitlemessage
MTCH-0204Bad RequestThe extraction request is invalid. Please verify the parameters and try again.

404

codetitlemessage
MTCH-0201Not FoundThe specified connection was not found. Please verify the connection ID and try again.
MTCH-0202Not FoundThe specified extraction was not found. Please verify the extraction ID and try again.

409

codetitlemessage
MTCH-0205ConflictA discovery refresh is already in progress. Please wait for it to complete before starting a new one.

503

codetitlemessage
MTCH-0203Service UnavailableThe Fetcher service is temporarily unavailable. Please try again later.

Ingestion errors


These errors are returned during transaction file upload and processing.

400

codetitlemessage
MTCH-0303Bad RequestThe file format is required. Please specify the format and try again.
MTCH-0304Bad RequestThe uploaded file is empty. Please provide a non-empty file and try again.

404

codetitlemessage
MTCH-0301Not FoundThe specified ingestion source was not found. Please verify the source ID and try again.
MTCH-0302Not FoundThe specified ingestion field map was not found. Please verify the field map ID and try again.
MTCH-0306Not FoundThe specified ingestion job was not found. Please verify the job ID and try again.

409

codetitlemessage
MTCH-0305ConflictThe ingestion job is in an invalid state for this operation. Please verify its current state.

Matching errors


These errors are returned during the reconciliation matching process.

400

codetitlemessage
MTCH-0401Bad RequestNo sources are configured for this context. Please configure at least one source before running a match.
MTCH-0402Bad RequestAt least two sources are required for matching. Please configure additional sources.
MTCH-0403Bad RequestEach source must have a defined side. Please specify the source side and try again.
MTCH-0404Bad RequestThe one-to-one topology configuration is invalid. Please verify the source configuration.
MTCH-0405Bad RequestThe one-to-many topology configuration is invalid. Please verify the source configuration.

409

codetitlemessage
MTCH-0408ConflictA matching run is already in progress for this context. Please wait for it to complete.

422

codetitlemessage
MTCH-0406Unprocessable EntityFee rules are required but not configured. Please add fee rules before running a match.
MTCH-0407Unprocessable EntityFee rules are misconfigured. Please review the fee rule settings and try again.

Exception errors


These errors are returned during exception handling, disputes, and callback processing.

404

codetitlemessage
MTCH-0501Not FoundThe specified exception was not found. Please verify the exception ID and try again.
MTCH-0502Not FoundThe specified dispute was not found. Please verify the dispute ID and try again.
MTCH-0507Not FoundThe specified comment was not found. Please verify the comment ID and try again.

409

codetitlemessage
MTCH-0504ConflictA callback for this exception is already being processed. Please wait for it to complete.
MTCH-0505ConflictThe callback encountered a transient error and can be retried. Please retry the request.

422

codetitlemessage
MTCH-0503Unprocessable EntityThe exception is in an invalid state for this operation. Please verify its current state.
MTCH-0508Unprocessable EntityThe dispatch target type is not supported. Please verify the target configuration.
MTCH-0509Unprocessable EntityThe dispatch connector is not configured. Please configure the connector and try again.

429

codetitlemessage
MTCH-0506Too Many RequestsThe callback rate limit has been exceeded. Please wait before retrying.

Governance errors


These errors are returned during audit log and governance operations.

404

codetitlemessage
MTCH-0601Not FoundThe specified audit log was not found. Please verify the audit log ID and try again.
MTCH-0602Not FoundThe specified actor mapping was not found. Please verify the actor mapping ID and try again.
MTCH-0603Not FoundThe specified archive was not found. Please verify the archive ID and try again.

Reporting errors


These errors are returned during report export operations.

400

codetitlemessage
MTCH-0705Bad RequestThe specified export format is invalid. Please verify the format and try again.

404

codetitlemessage
MTCH-0701Not FoundThe specified export job was not found. Please verify the job ID and try again.

409

codetitlemessage
MTCH-0703ConflictThe export is not yet ready for download. Please wait for the export to complete.

410

codetitlemessage
MTCH-0704GoneThe export has expired and is no longer available. Please create a new export request.

503

codetitlemessage
MTCH-0702Service UnavailableThe export worker is currently disabled. Please contact support to enable it.

Idempotency errors


These errors are returned when there is an issue with idempotency key handling.

400

codetitlemessage
MTCH-0015Bad RequestThe provided idempotency key is invalid. Please verify the key format and try again.

409

codetitlemessage
MTCH-0018ConflictA request with this idempotency key is currently being processed. Please wait for it to complete before retrying.

500

codetitlemessage
MTCH-0016Internal Server ErrorThe idempotency configuration is invalid. Please contact support if the issue persists.
MTCH-0017Internal Server ErrorAn unexpected error occurred while processing the idempotency key. Please try again later.