Skip to main content

Limits and plans

Every VenueOS plan includes API access. Limits protect the platform for everyone and grow with your plan.

StarterProVenue GroupFull access
Rate limit60 requests/minute per key120/minute300/minuteCustom
Monthly quota10,000 requests per venue100,0001,000,000Custom
Active API keys2520Custom
Scopesvenue, events, menus+ orders, check-ins+ guest profilesEverything, including write
Embeds and public read APIUnlimited (fair use)UnlimitedUnlimitedUnlimited
SupportEmailEmailPriorityDedicated

How limits work​

  • Rate limit: counted per key in one-minute windows. Over the limit, requests get 429 rate_limited until 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:
HeaderMeaning
X-RateLimit-LimitRequests allowed per minute for this key
X-RateLimit-RemainingRequests left in the current minute
X-RateLimit-ResetUnix time when the minute resets
X-Quota-LimitRequests allowed this month for the venue
X-Quota-UsedRequests used this month
Retry-AfterOn 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) and cursor rather than re-fetching everything.
  • Use updated_since to 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.