Rate Limits
300 requests per minute, per Restro-API-Key credential.
- The limit applies per credential, not per IP or per tenant. Two credentials for the same tenant each get their own 300/min budget.
- It’s one shared budget for the whole API. Menu, orders, and hotels endpoints all count toward the same 300/min limit for that credential; there are no per-endpoint limits.
- There’s currently no way to request a higher limit for a specific credential.
Exceeding the limit
Section titled “Exceeding the limit”A request over the limit returns 429 Too Many Requests with the standard error envelope:
HTTP/1.1 429 Too Many RequestsRetry-After: 42{ "code": "rate_limited", "message": "Too many requests."}The response includes a Retry-After header with the number of seconds to wait. Respect it instead of retrying right away.
Recommended approach
Section titled “Recommended approach”- Track your own request rate per credential and stay under 300/min. Don’t rely on
429responses as your main signal. - On
429, back off for at least theRetry-Aftervalue before retrying, and use exponential backoff if you hit it repeatedly. - If your integration genuinely needs a higher sustained rate, talk to RestroLab instead of working around the limit with retries.
