ManagementApiError

Schema

The body of every failure response on this API — one envelope, whatever the status code.

Unlike a success reply, every field except txId is always present: when we produce an error body we produce all of it, so you can read path or message without a null check.

Fields

statusCodenumberrequired
The HTTP status, repeated in the body so a caller that logs only the body still knows what happened. Always the same number as the status line — never a second, body-only code.
timestampstring<date-time>required
When we produced the failure, ISO-8601 UTC.
pathstringrequired
The ROUTE that failed — /management/stores/fetchStores. No query string.
methodstringrequired
The HTTP method of the failed call. Always POST on this API today.
messagestringrequired
A human-readable summary — for a human. Do not branch on it: it is not part of the contract and changes without notice. Branch on statusCode and on documented fields.
txIdstring
The support handle: the identifier for THIS one call, the same value on the x-mealco-tx-id response header and on every log line the call produced. Quote it in a ticket and we can pull the complete record of that single call.

Optional for one reason, and nothing to code defensively around beyond checking for absence: a request whose body is not valid JSON is rejected before it reaches an operation, so that one 400 answers a bare {"message": "Bad Request"} with no txId and no header. Every other failure on this API carries the full envelope including this field.