Partner API Rate Limits

This page explains the Rate Limit policy (sometimes mistyped as rare limit) for the Petoks Partner API.

Rate Limit Principles

• Limits are enforced per API client (not globally).
• Counting uses a rolling 60-second window.
• Limit values are configured in partner admin (rate_limit_per_minute).

Default Value

• If the configured value is empty or invalid, the system applies a safe fallback: 120 requests/minute.

When Limit Is Exceeded

If traffic exceeds the limit, API returns:

• HTTP status: 429
• Body: { "success": false, "error": "Rate limit exceeded" }

Client Implementation Recommendations

• Apply retry with exponential backoff.
• Cache responses for data that does not change frequently.
• Avoid aggressive polling; use stable intervals.
• Use separate API keys per partner/app for accurate monitoring.

Monitoring and Audit

• Every partner access is logged internally for auditing.
• Admins can monitor usage and adjust per-client limits.

Scope & Country Interplay

Rate limits operate together with other controls:

• Scope permission (e.g. pet.profile.read)
• Country allowlist
• Active/inactive API key status

This combination keeps integrations secure, fair, and globally scalable.