API offers only data in 3-hour intervals for the layers that are mentioned in the license detail. In other words, the data available on Windy.com (standard version) are the same as you get through the API.
The point-weather API documentation does not make any reference to include application/json content-type header. Please update the so people don't have stumble around trying to find out why their posts are returning 400.
@tungtrinh Hello, we do not show a 14-day forecast on Windy, so there is no 14-day forecast via API either. The 1-hour forecast is only available through Windy Premium and we do not plan to add it to the API.
@helgiben After a few days of hacking and kludges we got windy to work again in a SPA in angular. It worked just fine with an old version of windy. Windy changed something Aug 1st. and I had to spend a few days trying to get the lastest up-to-date version of windy to work.
Anyway, to make a long story short even if you do get windy to work in a SPA, the solution will be short lived. This message now appears in the console: Repeatedly calling "windyInit" of an already initialized API is an unsupported functionality and will be removed in future versions
Due to the way angular works after you leave or destroy a component the div with windy is destroyed. When you visit the component again it is resurrected. You need to call windyInit again to get windy to work with the new div. That works just fine today. They are warning you that it will no longer work in the future. I suspect that windy divs in react or vue SPA's work the similarly?
I exchanged a few emails with windy tech support and they suggest to use windy in an iframe. That will not work with our setup.