@marekd said in Windy API: missing precipitation data and limited history:

@gptwisted Thank you for the report. It was a bug, uv and precip_1h were accidentally excluded from the response. It is fixed now.

Thanks you for the quick fix! I can confirm it works!

Regarding the date when a station started reporting data, how exactly do you need to use it? It is quite complicated because some stations report data, then stop reporting for a few days or weeks, and then start again. PWS stations are generally not very reliable. What exactly do you need this date for?

Oh, ok I understand the reason - well, I was thinking to use the registration date to reduce the interval of the fetched data (e.g. less than 30 days if the station was registered less that 30 days ago). But since I can query just the last 7 days, I believe it is not needed.

Thanks again for the response.

Hi Windy,

I’m a Premium user and I share data from my personal weather station with Windy.

The API currently returns only a small subset of variables. Precipitation (rain rate / accumulation) is missing, even though it’s part of the station data. That makes the API hard to use for real integrations and analysis.

Historical coverage also seems very limited. Key metadata is not available either, such as when a station started sending data. Without that, it’s difficult to properly validate and interpret time-series data.

Is this the intended scope of the API? Are there plans to expand variable coverage, historical depth, and station metadata, especially for Premium users and contributors?

Thanks.

Hello,

I'm trying to get the last 30 days but it always answers "Timestamp (in seconds) can be a maximum of 7 days into the past.". Docs says "Start timestamp (seconds) for the time series; max 30 days back." Is this a bug?

Endpoint: https://stations.windy.com//api/v2/opendata/station/{id}/observation

When this will be fixed?

Could you provide an estimate for when this might be resolved? With the hurricane in the U.S. and the wildfire season in the Amazon, this disruption really comes at a tough time...