Rate limits and safe retry behavior

Each plan has a request-rate limit — see plan tiers and usage limits for current numbers (Free, Pro, and Enterprise tiers differ significantly). Design your integration to stay under your plan's limit rather than bursting against it.

Safe retry behavior

• Never retry in a tight loop — use exponential backoff between attempts
• Always check the successful field in the response envelope before deciding whether to retry — see understanding the API response envelope; retrying a request that already logically failed for a non-transient reason just wastes your rate budget
• If you're consistently hitting your limit, that's a signal to check whether you need a higher plan rather than retrying harder

For the exact shape of a rate-limit response, check your API reference — it isn't duplicated here to avoid this article drifting out of sync with the real behavior.