Okapi Okapi

GET /data/2.5/forecast/daily → endpoint removal

OpenWeather API

Deprecated, no date

The provider has deprecated the query parameter id on GET /data/2.5/forecast/daily without a shutdown date. Calls using this parameter will eventually fail. The provider notes that the built-in geocoder is deprecated and no longer receives bug fixes or updates.


Calls it hits

  • GET /data/2.5/forecast/daily
  • query parameter id

What to use instead of these calls

Resolve the city ID with the Geocoding API (/geo/1.0/direct or /geo/1.0/zip) and call the endpoint using 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.

OpenWeather API, Announcement

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 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 6

  1. No date GET /data/2.5/onecallEndpoint removal Deprecated, no date
  2. No date GET /data/2.5/forecastEndpoint removal Deprecated, no date
  3. No date GET /data/2.5/weatherEndpoint removal Deprecated, no date
  4. No date GET /data/2.5/forecastEndpoint removal Deprecated, no date
  5. No date GET /data/2.5/forecast/dailyEndpoint removal Deprecated, no date
  6. 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.

Add to GitHub