Skip to main content

Rate Limits by Plan

Limits are applied per user account, not per API key. If you generate in both the Telegram bot and via API, both count toward the same limits.

Rate Limit Headers

Every API response includes headers showing your current status:

Handling Rate Limit Errors

When you exceed the rate limit, the API returns 429 Too Many Requests:
The retry_after field tells you how many seconds until the limit resets.

Best Practices

Don’t hammer the API after a 429. Wait, then retry with increasing delays:
Check X-RateLimit-Remaining-Hour in each response and slow down when you’re close to the limit, rather than waiting for a 429.
For bulk tasks (e.g. generating 100 product images), spread requests over time. A VIP user can do 100/hour — you can saturate this with a simple queue.
If you’re building a production service with unpredictable load, the Elite plan’s unlimited rate is designed for that use case.

Auth Endpoint Limits

Authentication endpoints have stricter rate limits to prevent abuse: