Skip to main content
The Midaz API returns errors on /v2 routes as an RFC 9457 problem details object, served with the application/problem+json content type:
Routes under /v1 return errors as application/json with code, title, and message. Validation errors on /v1 can also carry entityType and fields.
Field definitions
  • type: A URI that identifies the error type, built as https://errors.lerian.studio/v1/ followed by the error code.
  • title: A brief summary of the issue.
  • status: The HTTP status code of the response.
  • detail: Detailed guidance for resolving the error. The message column in the table below shows the text that the API returns. %v stands for a value that the response fills in.
  • code: A unique, stable identifier for the error.
  • entityType: The entity the error relates to (for example, Organization). Only present when applicable.
For server-side errors (HTTP 5xx), title and detail carry the catalog text. An unexpected error returns a generic body. Use code and type to identify the error.
Field-level error details For issues specific to individual fields, an errors array lists each field with its problem. Examples:

Midaz errors


Refer to the following table for error codes and their descriptions:

Authentication and tenant refusals


A request that authentication refuses returns a code from the authorization layer, not a Midaz code: A refusal that the Access Manager decides carries the Access Manager code. See the Access Manager error list. In a multi-tenant deployment, tenant resolution can refuse a request with these codes: Midaz returns 0042, 0043, or 0525 only for a refusal that carries no code of its own.