TomTom Maps APIs
roadUse query parameter removal on GET /search/2/reverseGeocode/*
Deprecated, no dateSubscribe to TomTom Maps APIsShare
TomTom Maps APIs deprecated the roadUse query parameter on GET /search/2/reverseGeocode/* without a shutdown date. TomTom Maps APIs announced on September 19, 2023, that support for the roadUse parameter will be removed. Once removed, requests relying on this parameter fail.
Calls it hits
GET /search/2/reverseGeocode/*query parameter roadUse
What to use instead of these calls
Stop filtering by roadUse. Instead, request returnRoadClass=Functional and filter on the roadClass array of the results.
In TomTom Maps APIs's words
Deprecated Support for the roadUse parameter will be removed.
Facts
- API
- TomTom Maps APIs
api.tomtom.com - Kind
- Parameter removal
- Announced
- September 19, 2023
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against TomTom Maps APIs's own pages
Questions
When does this change take effect?
TomTom Maps APIs deprecated GET /search/2/reverseGeocode/*, query parameter roadUse without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: TomTom Maps APIs has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from TomTom Maps APIs 4
-
No date
GET /search/2/reverseGeocode/*Parameter removal Deprecated, no date -
No date
GET /search/2/reverseGeocode/*Parameter removal Deprecated, no date -
No date
GET /maps-sdk-for-web/cdn/*Removal Deprecated, no date -
No date
GET /search/2/geocode/*Parameter removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.