Skip to main content
Error format Lerian STA returns errors as RFC 9457 problem details with the application/problem+json media type:
Field definitions
  • type – A URI that identifies the error in the Lerian error catalog, built as https://errors.lerian.studio/v1/<code>. A response with no code carries the RFC default about:blank.
  • title – The HTTP status text (for example, Not Found).
  • status – The HTTP status code.
  • detail – A human-readable explanation of this occurrence. For 5xx responses, STA replaces the detail with internal error. An internal cause stays out of the response body. Branch on code instead.
  • code – A stable identifier for the error (STA-NNNN). Branch on this field. A request that fails request-schema validation carries no code, and errors names the fields at fault. Two errors can share a title and a status and still differ here. STA-0005 and STA-0016 both answer 404 with the title Not Found. The code tells you which one you got.
  • errors – Optional list of individual error details, each with a location, a message, and a value.

Request and routing errors


These errors apply to the request itself. They cover its syntax, its fields, its route, and the state of the service that received it.

Credential and transfer errors


These errors apply to BACEN credentials, to inbound source configuration, and to the credential a transfer sends under.