Monitor your key's usage before you hit a limit
Watching your quota headers as you go tells you when a limit is approaching, well before a request actually gets rejected.
Tag
#quota
Rate limit differences to expect when you switch providers
Rate limits vary in structure, not just in number, across providers. Here is what to check before assuming your current logic still applies.
Test your integration without spending your daily quota
The free daily allowance exists for exactly this, building and testing an integration before any money or a key is involved.
Network allowance: why a shared office shares one quota
The free daily allowance is counted per network, not per address, so a shared office or building draws from one pool rather than many.
Rate limits, explained in plain language
Rate limits on My Geocode are simpler than they sound: a free daily allowance per network and per key, then prepaid credit or Unlimited coverage.
Set up polling for a large batch job without a webhook
There is no async job queue here, just synchronous bulk requests, so a large job means chunking and polling your own quota headers.
Quota headers on every response: know your limit before you call
Every My Geocode response carries a full set of quota headers, so a script can know exactly where it stands without a separate usage lookup.
Cache geocoding results without breaking your quota math
Caching addresses saves requests, but only if your cache and your quota headers agree on what has actually been looked up.
Read the X-Quota-Used and X-Quota-Limit headers correctly
Every response carries quota headers, but reading them correctly means knowing which one reflects your key and which one reflects your network.
How we count a bulk request: one item, one unit
A single call with a hundred addresses inside it counts as a hundred requests, not one. Here is why we count bulk calls by item instead of by call.