Integration guides
Rate limits
Request limits, the headers that report them and how to back off.
TeePay limits requests per API key and per application so one integration cannot affect others. Responses carry the current state:
RateLimit-Limit: 120
RateLimit-Remaining: 117
RateLimit-Reset: 42When you exceed a limit you receive 429 rate_limited with a Retry-After header in seconds. Wait
that long before retrying. 503 responses also include Retry-After.
Operation limits
Some operations have their own limits on top of the general ones:
- Checkout sessions
- 30 creations per account per minute
- Control Numbers
- 10 creations per account per minute, plus daily and monthly quotas
- Link API and MCP
- 60 requests per account per minute, shared
- Collections
- Your account's per-transaction and daily amount limits
Good practice
- Back off on
429and503usingRetry-After; add jitter when many workers retry. - Poll payment status every 3 to 5 seconds at most, and prefer webhooks.
- Cache
GET /v1/capabilitiesfor a few minutes instead of calling it on every request.