paytrack
Read docs

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. X-RateLimit-Reset is Unix time in seconds (not an ISO date string) — the start of the next per-minute window.

Example
X-RateLimit-Limit: 300
X-RateLimit-Remaining: 294
X-RateLimit-Reset: 1783670700

429 response

Example
{
  "success": false,
  "error": {
    "code": "rate_limited",
    "message": "Rate limit exceeded.",
    "details": {}
  },
  "request_id": "req_xxx"
}

Best practices

  • Cache read-heavy data where possible.
  • Use exponential backoff with jitter for retries.
  • Respect X-RateLimit-Reset and 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.

Related docs

Usage dashboardErrorsTesting