Rate Limits
Gale enforces rate limits to ensure consistent performance and prevent abuse.Current Limits
Limits are enforced per API key across all endpoints. All requests count toward your limit regardless of HTTP method (GET, POST, etc.).
Rate Limit Headers
Every API response includes rate limit information:X-RateLimit-Limit: Total requests allowed per minuteX-RateLimit-Remaining: Requests remaining in current windowX-RateLimit-Reset: Unix timestamp when the limit resets
Handling Rate Limits
When you exceed the rate limit, youβll receive a429 response:
Retry-After header indicates seconds to wait before retrying.
Best Practices
1. Implement Exponential Backoff
2. Use Webhooks Instead of Polling
Donβt poll for order status - use webhooks: Bad:3. Batch Operations
Use batch endpoints when available:4. Cache Results
Cache eligibility checks and product data:Request Higher Limits
Need higher limits for your production use case? Contact support@withgale.com with:- Your use case description
- Expected request volume
- Current API key
Related
- Authentication - API key setup
- Errors - Error handling
