Using Open-licence Windy station data in an app

Nick 111

Hi,
I’m developing VeriSky, a weather app, and I’m interested in using the open-licence stations from the Windy Stations API to show observations alongside forecasts.
The station data would simply be displayed in the app when a user views a location or select a station. I wouldn’t resell the data, expose it through another API or redistribute it.
Before building this, I wanted to check a few things:

Is this kind of use allowed under the Open Data Licence?
For attribution, is showing the station name with a link to its Windy station page sufficient?
Are there rate limits or daily quotas for the Stations API?
Is caching allowed, including keeping observations for longer than the 7 days returned by the API?

Verisky is freemium, but viewing Windy station observations would be free. If that still requires a separate commercial agreement, let me know.
Thanks!

Suty

@Nick-111 Hello, if I understand this, you want to get our station data from our app, correct? If you do, I am afraid that this is not possible. We don't offer any station API to get these data from our end.

Nick 111

@Suty said in Using Open-licence Windy station data in an app:

Hello, if I understand this, you want to get our station data from our app, correct? If you do, I am afraid that this is not possible. We don't offer any station API to get these data from our end.

Thanks for the answer. I mean this endpoint: https://stations.windy.com//api/v2/opendata/station/{id}/observation

So for example curl -s "https://stations.windy.com/api/v2/opendata/station/f07a673e/observation"
-H "windy-api-key: " that gives me a Davis Vantage Pro 2 in westkapelle

Suty

@nick-111 Hi,

Thanks for reaching out about VeriSky!

Allowed use: Yes — for stations shared under the "Open" option, use is governed by our Aggregator Open Data Licence, and inline display alongside forecasts (per location/station) fits within that. Just don't expose the data via your own API, resell it, or redistribute it to third parties.

Attribution: Two parts — (a) where a station requires it, show the station name with a link to its Windy station page (not needed on map/list overview screens); (b) separately, our terms require displaying a link/button to our station registration page

Rate limits/quotas: We don't publish a fixed number, but continuous scanning of many stations or bulk-downloading station history is treated as misuse. As long as you're fetching data for stations a user is actually viewing, you should be fine.

Caching: You can cache beyond the 7-day query window (that cap is just on how far back a single request can look). If a provider stops sharing or requests deletion, please be able to purge it on your end.

Freemium/commercial terms: Since this only involves Open-licensed data and is used for display within your own app, it should fall under the standard Open Data Licence rather than needing a separate commercial agreement

Nick 111

@Suty Thank you! I will make sure to clearly show the attribution everywhere you mentioned. To confirm the rest: the data stays inside the app. We don't expose it through an API of our own, we only fetch a station when a user actually opens it, so there's no background scanning of the network and no bulk history downloads.
If a provider stops sharing or asks for deletion, we can delete their cached data on our side.

Thanks for the quick and clear answer, that's everything I needed. Best, Nick