Overview
The Ilumiera AI B2B API may apply rate limiting to prevent abuse and ensure service quality for all users. During the beta period, rate limits are generous and subject to change based on usage patterns.Current Status
- Beta Period: Rate limiting may be applied but specific limits are not yet defined
- CORS: Enabled for all origins during beta
- HTTPS Only: All endpoints are served over HTTPS
Rate Limit Headers
When rate limiting is implemented, API responses will include standard rate limit headers:- X-RateLimit-Limit: Your request limit for the time window
- X-RateLimit-Remaining: Number of requests remaining
- X-RateLimit-Reset: Unix timestamp when the limit resets
Best Practices
1. Monitor Response Headers
Always check for rate limit headers in API responses:2. Handle Rate Limit Errors
If rate limiting is enforced, you’ll receive a 429 status code:3. Implement Exponential Backoff
Use exponential backoff for automatic retries:4. Optimize API Usage
To minimize hitting rate limits:Batch Operations
Instead of generating quiz, flashcards, and mindmap in rapid succession:Cache Responses
Store generated content to avoid repeated API calls:Monitor Usage Patterns
Track your API usage to identify optimization opportunities:Planning for Scale
As you scale your usage of the Ilumiera AI B2B API:- Monitor Usage: Keep track of your request patterns
- Implement Caching: Cache responses when appropriate
- Queue Requests: Use a queue system for non-urgent operations
- Contact Support: Reach out if you need higher limits
Future Updates
Rate limits are subject to change as the API evolves. We recommend:- Implementing flexible rate limit handling in your code
- Subscribing to API updates for notifications about changes
- Testing your rate limit handling logic regularly
