MTMini Till
Staff POS login
← Back to Help Centre

Billing, Settings & Developer API

Developer API rate limits

Handle both the per-key 100-requests-per-minute guard and the Business plan's daily API allowance.

Overview

  • Public API keys currently have a database-backed fixed-window limit of 100 requests per minute per API key.
  • Responses expose X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset; when blocked they also include Retry-After.
  • Separately, the selected Business plan has a daily API request allowance counted in UTC-day buckets.
  • The standard Pro allowance is currently 1,000 requests/day and the standard Enterprise configuration 100,000/day; custom overrides can differ.
  • Daily-limit responses expose X-Daily-RateLimit-Limit, X-Daily-RateLimit-Remaining, and X-Daily-RateLimit-Reset.
  • These are two independent controls: staying below 100/minute does not guarantee the Business has daily quota remaining.

When to use this

  • Design integrations around these limits before bulk synchronisation or frequent polling.

Step-by-step

  1. Read rate-limit response headers.
  2. Throttle requests below the per-key minute limit.
  3. Cache/read incrementally instead of polling full datasets unnecessarily.
  4. Track the Business's daily usage/allowance.
  5. On 429, respect Retry-After/reset headers.
  6. Request a higher plan/override if legitimate production traffic exceeds the daily entitlement.

Common mistakes

  • Do not retry a 429 in a tight loop.
  • Do not create multiple API keys purely to bypass the Business daily allowance.
  • Do not assume rate-limit reset uses the Store's local midnight; daily usage currently uses UTC buckets.

Troubleshooting

  • If X-RateLimit-Remaining is zero, wait for the minute window reset.
  • If the minute window has reset but calls still fail for quota, inspect X-Daily-RateLimit headers/Billing usage.