Skip to documentation
DOCUMENTATIONRate limits
BUILD AN INTEGRATION

Rate limits

Understand shared quotas, diagnostics and admission limits.

One account allowance

All external keys on an account share the minute and monthly allowance. CardCounter POS Pro connectors share that account allowance too. UTC minute/month windows are computed in the database. Public plans and documentation do not consume paid allowance.

POS market and scanner calls reserve a durable one-use receipt before source work. Retrying with the same x-market-lookup-id preserves the reservation and charge, while an already dispatched receipt cannot be reused. Omitting this optional header creates a new lookup identity. A catalog retry reserves a new attempt; source results are not replayed from storage. Source failures remain observed attempts, not automatic quota refunds.

Usage at exhaustion

GET /v1/usage is authenticated but does not debit paid allowance, so it remains useful when quota is exhausted. A separate 30 diagnostics per account per minute limit applies per process. Local anonymous or single-key mode returns USAGE_UNAVAILABLE because there is no account to inspect.

Headers and overload

Admitted account-backed responses expose x-plan, x-ratelimit-limit, x-ratelimit-remaining, x-monthly-limit and x-monthly-remaining. Every application response has x-request-id. Retry-After is a nonnegative number of seconds for quota/cooldown/capacity failures.

Invalid authentication attempts are limited per invalid credential identity, with a peer bucket for malformed credentials; service admission, authorization and OCR have capacity limits. These abuse/diagnostic admission limits are process-local. Database paid quotas are shared across replicas. Configure ingress/WAF limits for distributed abuse rather than treating process-local limits as a global guarantee.

Explore the wire contract.

API reference