Rate Limits
Rate limits are set per API key at onboarding, matched to your expected call volume - there is no single published number that applies to every account.
Confirm your limits
Exact limits and burst behavior for your key are confirmed when access is provisioned. If you're not sure what your current tier allows, contact support with your tenant subdomain.
What happens when you exceed your limit
A request over your limit returns 429 Too Many Requests. Back off and retry - a fixed delay is
safer than retrying immediately, since immediate retries just extend the throttled window.
Requesting a higher tier
If your integration's call volume has grown past your current limit, or you're moving from evaluation to production traffic, talk to sales with your expected monthly volume and we'll adjust your tier.
Designing for scale
- Batch where the API supports it - the Batch Geocoding and Batch Reverse Geocoding APIs cost one call for many records instead of many.
- Cache stable lookups - administrative boundaries and pincode lookups change rarely; cache them client-side rather than re-querying.
- Use the Route Matrix API instead of looping individual Distance API calls for many-to-many calculations.
