What we shipped this month: geocoding, IP, time zone and more
A roundup of recent work across the API: new compatibility hosts, faster time zone and elevation lookups, dashboard features, and clearer quota visibility.
A new bulk endpoint for address lists
Processing a list of addresses one at a time, one HTTP call after another, works fine for small volumes and becomes tedious fast at any real scale. We now support sending an entire address list as a single bulk call, cutting down the round trips needed to process a large list without changing how anything is priced.
The counting rule here is exactly the one we apply everywhere else on the platform: each address inside a bulk call counts as one request, not the call as a whole. Send a list of five hundred addresses in one bulk call, and that consumes five hundred requests against whatever allowance applies, whether that is the free daily allowance, prepaid credit at €0.0001 a request, or coverage under an Unlimited package. There is no discount and no penalty for combining work into a single call versus sending it as many smaller ones.
Quota headers reflect the bulk call accurately as well. X-Quota-Used, X-Quota-Free-Remaining and X-Credits-Remaining all move by the number of addresses actually processed in the call, so a large bulk request updates your visible quota the same way five hundred individual calls would have, just in one round trip instead of five hundred.
This is aimed at exactly the kind of workload that used to mean writing a loop around single-address calls: importing a customer list that needs geocoding, cleaning up an address database, or preparing a large batch job that runs on a schedule rather than in response to a single user action. Sending that list in one bulk call reduces the overhead of managing many separate HTTP connections, particularly useful for jobs that run on infrastructure with its own connection or rate constraints beyond ours.
Authentication and general behavior are unchanged: the same four key methods work, the same quota rules apply, and the same free allowance covers meaningful testing before any real cost is involved. As with any address-based lookup, forward and reverse geocoding results are still part of our currently developing backend for populated real-world results, so this bulk capability is documented around its request shape and counting behavior specifically.
Full documentation for sending bulk requests, including request formatting, is available at /docs/forward-geocoding/ and /docs/reverse-geocoding/. If your workflow currently loops over single-address calls, this is worth a look for anything processing more than a handful of addresses at once.