Windy api got 500 "We are sorry, but something broke."

[Suty]

@Woraphol-Wananiyakul Can you please share how you implemented the API or how you use it more specifically?

[Woraphol Wananiyakul]

@Suty Thank you for the reply.
It just a normal axios call you can try this on your swagger it got same output

[Suty]

@Woraphol-Wananiyakul Could you please test it once again, it is possible that there was a certain local issue and we did some changes. Let me know then.

[arv-rsw]

@Suty I’m still seeing the same issue.

[Suty]

@arv-rsw Can you please provide more info about that?

[Woraphol Wananiyakul]

@Suty I’ve tested it again: the GFS model is working correctly, but the other models are still not functioning as expected.

[Oleksandr Honcharov]

@Woraphol-Wananiyakul Hello! Thanks for reporting. We've discovered an issue specific to users in your region and it should be fixed now. Could you please try again?

[Woraphol Wananiyakul]

@Oleksandr-Honcharov Thanks for rolling out the fix—after testing, I can confirm that the endpoint is no longer throwing errors and is responding successfully. However, I’m seeing that every field in the JSON payload is coming back as null


[Woraphol Wananiyakul]

@Oleksandr-Honcharov 

[Oleksandr Honcharov]

@Woraphol-Wananiyakul arome model covers only some part of Europe. Unfortunately it doesn't provide data for US region (pic. 1).

If you want to visually check which models cover your area, you can visit windy.com, select a layer you want to get data of (a temp in the provided example) and in the bottom right corner select a model from a list (pic. 2).

The best approach is to click some city label. In the opened Point Forecast window you can enter a compare mode. There is a complete list of supported models for the location.