Errors

Every error is an RFC 9457 problem details body with a stable code and a link to its page.

Shape

Errors answer with a 4xx or 5xx status and Content-Type: application/problem+json:

{
  "type": "https://api.bymundi.com/problems/invalid_request",
  "title": "Bad Request",
  "status": 400,
  "detail": "The passenger would not be valid.",
  "code": "invalid_request",
  "requestId": "req_7f3c…",
  "errors": [{ "path": "email", "message": "Invalid email" }]
}

code is stable: branch on it, never on detail or title.
type opens a page that explains the code and what to do.
errors[], when present, names each failing field by its path in your request (ops.2.parentId).
requestId is also in the Request-Id header of every response, success or not. Quote it when you report a problem.

Some problems add members: requiresConfirmation on confirmation_required, occupiedDays on days_occupied.

What to retry

Status	Retry?
400, 401, 403, 404, 422	No: fix the request.
409	After re-reading: the resource changed, or a request is still running.
429	Yes, after `Retry-After` seconds.
500, 503	Yes, with backoff and the same `Idempotency-Key` for writes.

Errors

#Shape

#What to retry

#Every code

Shape

What to retry

Every code