Tag: Geocoding & Places API
-
New Rate Limits for the Geocoding & Places API Active Are Now Live
The new per-second rate limits for our Geocoding & Places API that we announced on June 3 are now officially in effect.
What’s Now Active
We’ve transitioned from per-minute to per-second rate limits across all endpoints. This allows for more consistent traffic handling and better protection against sudden spikes.…
-
New Rate Limits for the Geocoding & Places API Effective July 1, 2025
We’re making some important updates to how our Geocoding & Places API handles traffic. These changes will go into effect on July 1, 2025, and are designed to make our services more reliable and responsive — especially as more and more users rely on them every day.…
-
Streamline Geocoding with Input Cleaning
Accurate addresses are key—but customers sometimes enter incorrect or even random info, leading to manual checks, callbacks, or wasted resources.
If this sounds familiar, our new address input cleaning feature is for you.
What is Input Cleaning?…
-
Introducing Our New Showcase: Try Out the Batch Geocoding API!
We are excited to announce a new showcase that allows you to experience the power and efficiency of our Batch Geocoding API. The Batch Geocoding is designed to handle large volumes of geocoding requests, making it an valuable tool for businesses and developers who need to process extensive datasets quickly and accurately.…
-
Suggestion by Text Supports Result Language
In the new version of the PTV Developer Geocoding & Places API V1.15.0 we improved the Suggestion by text endpoint.
With this feature, you can now specify the language for the results from the Suggestions by text endpoint, providing more flexibility and accuracy for your geocoding needs. …
-
New Batch Geocoding Service available
We are happy to introduce the new Batch Geocoding Service version 1.0.1.
You now can send several addresses or positions at once. PTV Developer now provides asynchronous batch APIs. The new endpoints by-addresses, by-texts and by-positions provide the same functionality as their corresponding endpoints for single requests.…