Sous Chef API
Sous Chef Ordering API
Documentation

Errors and retries

Status codes

CodeMeaningRetry?
200Accepted. On a write it means we queued the call, not that the restaurant decided.—
400The request body failed validation.No — fix the call.
401Missing, unknown or mismatched credentials (see Authentication).No — fix the credentials.
403The store is not on your channel.No.
404The storeCode is unknown, retired or not on your channel; or the order does not exist yet.No — fix the call.
422The store does not take orders through this API.No — use another store.
429Over the rate limit. Limits apply per channel key.Yes, after backing off.
5xxA fault on our side.Yes, with backoff.

Every failure names itself

A failure body carries statusCode, timestamp, path, method, a human-readable message, and txId — the identifier for that one call. Every operation in the reference points its error codes at the same OrderingApiError schema.

{
  "statusCode": 404,
  "timestamp": "2026-11-18T14:07:22.113Z",
  "path": "/ordering/orders/createOrder",
  "method": "POST",
  "message": "Not Found",
  "txId": "4f0a9c2e-6b31-4d77-9d0e-2a7f5c8b1e44"
}

The same value comes back on every response as the x-mealco-tx-id header. Log it against every call and quote it when you contact us. A request whose body is not valid JSON is rejected before we look at it, so that one 400 carries neither.

Retry policy

Every write on this API is idempotent: storeCode with platformOrderId identifies an order, so re-sending a call after a timeout or a 5xx never creates anything twice.

Retry 429 and 5xx with exponential backoff and jitter — start around one second, cap at a minute, give up after a handful of attempts. Honour Retry-After on a 429; when it is absent, wait 60 seconds. A 429 from our edge has no JSON body and no x-mealco-tx-id; treat it as a rate limit all the same. Do not retry 400, 401, 403, 404 or 422.

Do not parse messages

Branch on the status code and on documented fields. Messages are for humans and change without notice.