Rate limits
Respect organization-wide REST API limits and back off safely.
Production REST API limits are organization-wide sliding windows of 60 seconds. Paid plans currently expose 120 requests per minute for Hobby, 300 for Standard, 600 for Pro, and 1,000 for Enterprise. Free organizations have a nominal lower limit but do not have API access. Treat limits as an integration constraint, not as a reason to spread calls across uncoordinated workers.
Successful responses include X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset. When a request is limited, the API returns 429 with RATE_LIMIT_EXCEEDED and a Retry-After value in seconds. Centralize backoff in the service that owns your API key, honor Retry-After, and add jitter so concurrent jobs do not resume in lockstep.
Reduce avoidable traffic before increasing concurrency: cache stable reads, page through lists instead of repeatedly restarting them, poll asynchronous work at a measured interval, and batch your own follow-up processing. Local development may not reproduce production limit enforcement when its backing services are absent, so test the recovery path as well as the happy path.