Overview

API requests are rate limited per organization and API key to maintain platform stability. Standard plans include sustained request rates suitable for CI pipelines and moderate polling; enterprise plans support higher quotas.

Who should read this

QA engineers, SREs, platform teams, and developers operating Zof Console and APIs.

When to use this workflow

Onboarding new team members to Zof terminology and workflows
Authoring internal runbooks aligned with Console labels
Designing CI/CD or webhook integrations against documented behavior

Step-by-step procedure

Monitor usage

Inspect X-RateLimit-* response headers in integration logs.

Alert when Remaining drops below threshold during pipelines.

Request increase

Contact support with organization ID, expected peak RPS, and timeline.

Key concepts

Default quota: Typical: 100 requests/minute per organization on standard plans (contact support for current limits).
Burst allowance: Short bursts above sustained rate may succeed before throttling.
429 response: Rate limit exceeded; honor Retry-After header before retrying.

Best practices

Use webhooks instead of polling run status every few seconds
Implement exponential backoff with jitter on 429
Request quota increase before major migration events