Basics
Rate limiting
A Redis-based rate limit per key and hour protects the platform from overload – a fair-use safeguard with no performance penalty.
#Per key and hour
Every API key has an hourly limit. The count runs through Redis, so it's fast and doesn't affect response times.
#Handling limits
When the limit is reached, the API responds with the corresponding HTTP status. Plan integrations to batch requests and retry conservatively if needed.
Was this helpful?
Suggest an edit