GET /data/2.5/forecast/daily → endpoint removal
OpenWeather API
Deprecated, no date
OpenWeather has deprecated the query parameter q on GET /data/2.5/forecast/daily without a shutdown date. The built-in geocoder is still available for use, but bug fixes and updates are no longer provided. Eventually, unsupported calls will fail.
Calls it hits
GET /data/2.5/forecast/dailyquery parameter q
What to use instead of these calls
Resolve the city name with the Geocoding API using /geo/1.0/direct or /geo/1.0/zip and call the endpoint with lat and lon instead.
In OpenWeather API's words
Please note that built-in geocoder has been deprecated. Although it is still available for use, bug fixing and updates are no longer available for this functionality.
Facts
- API
- OpenWeather API
api.openweathermap.org - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against OpenWeather API's own pages
Questions
When does this change take effect?
OpenWeather API deprecated GET /data/2.5/forecast/daily, query parameter q without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: OpenWeather API 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 OpenWeather API 6
-
No date
GET /data/2.5/onecallEndpoint removal Deprecated, no date -
No date
GET /data/2.5/forecastEndpoint removal Deprecated, no date -
No date
GET /data/2.5/forecast/dailyEndpoint removal Deprecated, no date -
No date
GET /data/2.5/weatherEndpoint removal Deprecated, no date -
No date
GET /data/2.5/forecastEndpoint removal Deprecated, no date -
No date
GET /data/2.5/weatherEndpoint 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.