Sous Chef API
Sous Chef Ordering API
Documentation

Authentication

Send your channel key on every request:

HeaderMeaning
x-api-keyYour channel key, issued per channel. Treat it as a secret.

The key is the whole credential. Do not send an organization header: your channel's organization is known from the key. A request that carries x-mealco-org-id (the Management API's header) is rejected with 401.

Scope

A channel key belongs to your channel, not to any restaurant. It reaches the stores that sell through your channel — in every restaurant organization that runs one — and nothing else. A store that is not on your channel answers 404, exactly as an unknown store does. A Management API key never works on this API, and a channel key never works on the Management API.

Handling keys

  • Keep the key server-side. It is a bearer credential — anyone holding it is you.
  • Treat the whole key as a secret. Its leading otk_… part (up to the second _) identifies the key: quote that part, never the whole key, in a support request.
  • Rotate by asking for a new key, moving traffic to it, then retiring the old one. Both are live during the overlap.
  • If a key is exposed, tell us immediately; a compromised key is revoked, not rotated on a schedule.

Rate limits

A limit is per key: 300 requests a minute for each channel key across /ordering/*. A request without a key is limited to 10 a minute per source IP. If your volume needs more, write to support@yoursouschef.com with the rate you need.

429 is part of the contract: any operation may answer it. Honour Retry-After when present; when it is not, wait 60 seconds and add jitter. See Errors and retries.

What a failure looks like

  • 401 — the key is missing, unknown or revoked, or the request sent x-mealco-org-id.
  • 429 — you are over your rate limit.