paytrack docs
Rate limits
Plan-based limits protect paytrack workspaces and keep integrations reliable.
How limits work
Each workspace has a monthly request quota and a per-minute rate limit. The limits depend on subscription plan and workspace overrides.
Headers
API responses include headers so clients can slow down before hitting a hard limit.
Example
X-RateLimit-Limit: 300 X-RateLimit-Remaining: 294 X-RateLimit-Reset: 2026-07-08T10:05:00.000Z
429 response
Example
{
"success": false,
"error": {
"code": "rate_limit_exceeded",
"message": "Rate limit exceeded. Retry after the reset time.",
"details": {
"retry_after": 30
}
},
"request_id": "req_xxx"
}Best practices
- Cache read-heavy data where possible.
- Use exponential backoff with jitter for retries.
- Respect
X-RateLimit-Resetand retry-after guidance. - Do not retry validation errors or missing-scope errors.
Upgrade signal
If usage is consistently above 80% of quota, review your plan before production launch.