The ask, in one paragraph Give active Premium subscribers a Point Forecast API key that returns real (unmodified) data, rate-limited to 500 requests per day, restricted to a small number of saved locations (2–3 is plenty), under a strict personal, non-commercial licence. Keep ECMWF excluded and keep every commercial use on the Professional plan, exactly as now. If free-with-Premium is a step too far, price it as a modest add-on — most of us would pay it without blinking. Who is asking Home users. Specifically the fast-growing overlap between Windy Premium subscribers and home-automation users (Home Assistant alone has well over a million active installations). We are not businesses. We want the forecast for one location — our own house — machine-readable, a handful of times a day. A concrete, real example (mine): a heat pump that cools a stone-floored house through its underfloor heating. The control system reads tomorrow's maximum temperature to decide whether to pre-chill the floors overnight (cheap electricity, high heat-pump efficiency), and tomorrow's dew point to decide how cold the floors may safely go without condensation. That is eight API calls a day. It is currently impossible to do this with Windy at any price a household can justify. Why the current options don't serve this need Premium includes no API access at all. The Trial key intentionally returns "randomly shuffled and slightly modified data" — unusable, by design, for any real automation. Professional (€990/year, 10,000 req/day, unlimited models) is built and priced for businesses. A household needing 8 requests/day for one lat/lon is not its market, and never will be. This gap is not new. The community has asked repeatedly over many years — see for instance: Basic API access with premium account API access for Windy Premium? API Trial suitable for home use? Pricing for personal use API possibilities for Home Assistant integration Why this is good for Windy, not just for us It sells Premium subscriptions. Today, a home-automation user gets nothing from Premium that their automation can use — so they wire up Open-Meteo.com or met.no, which give hourly temperature, humidity and dew point free, without keys. A Personal API makes Premium the obvious subscription for every Home Assistant user who already loves Windy's app. That is new recurring revenue from people you currently turn away. It cannot cannibalise Professional. Personal licence, hard rate cap, 2–3 fixed locations, no ECMWF, no redistribution, key tied to an active Premium subscription. No business can run on that; every safeguard Professional's price defends is intact. The infrastructure cost is already being paid. Trial keys are allowed 500 requests/day today — the servers already do this work, then scramble the result. Serving the true numbers to a paying subscriber costs the same compute as serving the corrupted ones to a free key. Goodwill, in a community that has asked politely for years. The threads above span half a decade. Meeting a long-standing, reasonable request from paying subscribers is the cheapest marketing available. Suggested shape (open to any variant) Aspect-------Suggestion Eligibility:-----Active Premium subscription Data:---------Real, unmodified point-forecast data Rate limit:-----500 requests/day (fewer would honestly suffice) Locations:-----2–3 saved lat/lon pairs per key Models:-------Standard set (iconEu, gfs, arome, …); ECMWF stays Professional-and-above Licence:------Personal, non-commercial, no redistribution Price:---------Included with Premium, or a small add-on (€xx/yr) Any of these numbers can move. The essential points are only two: real data and a price a household can justify.

@WinnieMP Hello Marketa, Thank you for your reply and for forwarding the issue to the appropriate team. I have now sent an email to webcams@windy.com with a link to this Community post, along with three specific webcam examples, their Windy webcam IDs, API lastUpdatedOn values, and screenshots showing the outdated images. I hope this information will help your developers investigate the issue. Thank you again for your assistance. Kind regards, Andreas MeteoPatras.eu

Hello, you had a typo in the email domain, but I found your account and logged it out from everywhere

Since it uses the official Windy API with a user provided key, it should avoid licensing issues as long as the API terms are followed. It would be interesting to see support for more forecast features in the future.

@Suty Oui bien sûr ! Je sais en effet que les couches de vagues, mer du vent, et houle 1 2 et 3 dispose de l'information sur leur période quand on clique sur un point. Mais je voulais savoir si c'était possible d'ajouter une option via un bouton simple pour que les couleurs sur la carte représente elle aussi la période, actuellement elle représente la hauteur. Le fait de pouvoir varier les deux variables sur la carte permettrai de mieux voir les différentes houles se propager, je trouverais cela intéressant. Je ne sais pas si je suis très clair ou si mon idée est faisable et pertinente, n'hésitez pas à me dire !

Thanks for the explanation. Running the project through a local server and checking browser console errors helped me when testing APIs locally. The note about leaving the domain field empty for localhost is especially useful. Appreciate the guidance.

@navimeteo_fc Unfortunately, this is not possible right now, but you can set limitations in domains for your API key.

@easamoaku Hello, I am afraid that we don't support this. So this has to be a bit of your workaround.

@Karel-Fišer I think you can check it yourself. You can see in Windy that the Tide forecast is also available as POIs in some countries, in USA particularly. The data of these POIs are not provided by WorldTides but by local tide tables based on tide gauges. So you can compared these 2 types of data in USA by clicking on the POIs or out of them. The tide heights are quite similar. Local tide data (in Tide forecast POIs) [image: 1778743589993-img_3693.jpeg] [image: 1778742226710-img_3691-resized.jpeg] WorldTides data (out of Tide forecast POIs) [image: 1778743269014-img_3692-resized.jpeg] Another reason showing that on the US coasts the datum used in Windy for “WorldTides data” is not the LAT datum: it shows negative low tide heights, which is never the case with the LAT datum, as we use in Europe for example. Note on my screenshots that I haven’t converted the height into imperial units, nor the time in 12h format.

@Nicole-Dolezalova any current plans for the solar information being available in the API?

@scrmhawk In Windy, locations can be saved as Favorites And then they appear on the map. [image: 1773170607202-img_3266.jpeg] Or they can be added as GPX or KML files. [image: 1773170810442-img_3268.jpeg] [image: 1773171795801-img_3270.jpeg] Furthermore I understand that the plugins in Windy are not personal plugins, unlike the solutions I mentioned.

@Suty I have confirmed that it is working properly. Thank you for your reply.

@Vittorio-Pirazzoli Please check this article and let me know if you need any further assistance.

@Rolandoz said in PWS API v2 - updating position (lat/lon): What if you ONLY include the lat / lon fields in the json and omits all the other? Appreciate you thinking through the possible angles. I tried that approach previously. Because the station update via API v2 is done with a PUT, if any fields are missing they are overwritten as blanks. @Rolandoz said in PWS API v2 - updating position (lat/lon): And I assume your plugin can save the previous reported position and if it has not changed significant the simply omit the position update at all? The code already has a configurable distance calculation (default: 300m) so that when a boat is at anchor or dock the station update is skipped.

@mcrossley Hello, you are right, but answer was not clear at all. Weather stations primarily report Mean Sea Level (MSL) Pressure, which is the station's atmospheric pressure corrected to sea level.