A new bulk endpoint for address lists
Address lists can now be sent as a single bulk call, with each address counted individually rather than the whole call counting as one request.
Notes on geocoding, IP data, and building on the My Geocode API.
Address lists can now be sent as a single bulk call, with each address counted individually rather than the whole call counting as one request.
A bulk request with thousands of items in one call needs a timeout budget that matches its size, not a default meant for a single lookup.
Elevation data rarely gets its own line on a pricing page, and that absence tells you something real about how seriously it actually gets built.
Classifying an IP address as business or residential is a genuinely useful signal for many applications, but it is an inference from network characteristics, not a guaranteed fact.
Adding mg_extras=1 or an X-MG-Extras header to an IP lookup now returns optional threat and network detail on top of the standard response.
The first week after a provider migration is when subtle issues actually surface. Here is what to monitor closely during that window.
A SaaS company needed to know, for every user session, whether a visitor was connecting from inside the European Union, since that answer changed which servers and which consent flow applied.
A header, a bearer token, and a query parameter all authenticate a request the same way. Charging more for one of them is charging for a preference, not a feature.
When a region merges, splits, or gets renamed, every address and every dataset referencing the old boundary needs to be updated, and that update rarely happens everywhere at once.
Rate limits vary in structure, not just in number, across providers. Here is what to check before assuming your current logic still applies.
New posts in every topic, in one feed. No account, no tracking.
Subscribe with Atom