Limits and plans
Every VenueOS plan includes API access. Limits protect the platform for everyone and grow with your plan.
| Starter | Pro | Venue Group | Full access | |
|---|---|---|---|---|
| Rate limit | 60 requests/minute per key | 120/minute | 300/minute | Custom |
| Monthly quota | 10,000 requests per venue | 100,000 | 1,000,000 | Custom |
| Active API keys | 2 | 5 | 20 | Custom |
| Scopes | venue, events, menus | + orders, check-ins | + guest profiles | Everything, including write |
| Embeds and public read API | Unlimited (fair use) | Unlimited | Unlimited | Unlimited |
| Support | Priority | Dedicated |
How limits work
- Rate limit: counted per key in one-minute windows. Over the limit, requests get
429 rate_limiteduntil the window resets. - Monthly quota: counted per venue across all its keys, resetting on the 1st (UTC). Over the quota, requests get
429 monthly_quota_exceeded. - Every response says where you stand:
| Header | Meaning |
|---|---|
X-RateLimit-Limit | Requests allowed per minute for this key |
X-RateLimit-Remaining | Requests left in the current minute |
X-RateLimit-Reset | Unix time when the minute resets |
X-Quota-Limit | Requests allowed this month for the venue |
X-Quota-Used | Requests used this month |
Retry-After | On a 429, seconds to wait |
You can also check usage any time with GET /v1/usage or on the API page in VenueOS, which shows requests per day, errors and each key's usage.
Fair use
- Page through results with
limit(up to 100) andcursorrather than re-fetching everything. - Use
updated_sinceto sync only what changed. - Use webhooks instead of polling for new orders and check-ins.
- Cache event and menu data for at least a minute.
Full API access
Need write access (create events, issue tickets, check guests in), higher limits, multiple venues under one key, or a partner integration? Full access is set up per customer: contact us.