OpenWeather API
id query parameter removal on GET /data/2.5/forecast
Deprecated, no dateSubscribe to OpenWeather APIShare
OpenWeather API has deprecated requests using the query parameter id on GET /data/2.5/forecast without a shutdown date. OpenWeather API notes that API requests by city id have been deprecated. Calls continuing to use this parameter will eventually fail.
Calls it hits
GET /data/2.5/forecastquery parameter id
What to use instead of these calls
Resolve the city ID with the Geocoding API and call with lat and lon instead.
In OpenWeather API's words
Please note that API requests by city name, zip-codes and city id have been deprecated.
Facts
- API
- OpenWeather API
api.openweathermap.org - Kind
- Parameter 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, query parameter id 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 9
-
No date
GET /data/2.5/onecallEndpoint removal Deprecated, no date -
No date
GET /data/2.5/forecast/dailyParameter removal Deprecated, no date -
No date
GET /data/2.5/weatherParameter removal Deprecated, no date -
No date
GET /data/2.5/forecastParameter removal Deprecated, no date -
No date
GET /data/2.5/forecast/dailyParameter removal Deprecated, no date -
No date
GET /data/2.5/weatherParameter removal Deprecated, no date -
No date
GET /data/2.5/forecastParameter removal Deprecated, no date -
No date
GET /data/2.5/forecast/dailyParameter removal Deprecated, no date -
No date
GET /data/2.5/weatherParameter 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.