Windy Point Forecast API (gfsWave) Returns Data Where App Shows None

Carlos Fiebig

Hello Windy Team,

I’d like to report an issue with the Point Forecast API and request clarification on data consistency when using the gfsWave model.

Issue: API returns data where the web app shows none

When querying a point with the gfsWave model, the API returns wave data values even when the Windy web application shows no data available at that location.

Example request (using a valid PRO Point Forecast API Key):

{
"lat": -45.382,
"lon": -73.044,
"model": "gfsWave",
"parameters": ["waves"],
"levels": ["surface"]
}

Observed behavior: API responds with wave data.

Expected behavior: The API should return no values (or null/error) at this point, to match the web app behavior.

Inconsistency between API and Web app

For the exact same coordinates and model, the API produces forecast values while the Windy web application shows no result.

I’ll attach two images for reference:

One from the Windy app showing no data for that point.

Another from the API response showing returned values.

This inconsistency makes it difficult to align API-driven outputs with what users see in the Windy app.

Request

Could you confirm whether the API returning values outside the model’s valid coverage area is a bug or an intentional fallback behavior?

Could you clarify why the API and web app behave differently in this case?

Ideally, both should return the same result, so forecasts are consistent between the API and the app.

Thanks for your support and for providing such a powerful forecasting platform.

Best regards,
Carlos Fiebig