Upon requesting forecast data for more than 9 days, the API would return "400 Bad Request".
Here are some values I tried (as of 2024-07-02T15:00:00Z):
(dailyStart is in past)
dailyStart=2024-07-01T15:00:00Z
dailyEnd=2024-07-11T15:00:00Z
expected= 10 days forecast
actual= 10 days forecast
(dailyStart is current date, forcecast > 9 days) fails
dailyStart=2024-07-02T15:00:00Z
dailyEnd=2024-07-12T15:00:00Z
expected= 10 days forecast
actual= 400 Bad Request
(dailyStart is current date, forecast <= 9 days)
dailyStart=2024-07-02T15:00:00Z
dailyEnd=2024-07-11T15:00:00Z
expected= 9 days forecast
actual= 9 days forecast
(no values passed) fails
dailyStart=
dailyEnd=
expected= 10 days forecast
actual= 9 days forecast
The official documentation says:
dailyEnd: The time to end the daily forecast. If this parameter is absent, daily forecasts run for 10 days.
dailyStart: The time to start the daily forecast. If this parameter is absent, daily forecasts start on the current day.
This started happening sometime last week.
Would someone please tell me what changed with the API?
Thank you.
Post
Replies
Boosts
Views
Activity
Hello,
I'm migrating my app to use WeatherKit from Dark Sky, and although most of the data fields is transformable, there are a few that are missing from WeatherKit's response; for example, summary and icon for daily/hourly/current weather data blocks.
I'm curious, what workarounds have people used for these fields that can bridge that gap? My app relies on these values to render icons.
Thank you!