<![CDATA[We are sorry, but something broke.]]>Hello I trying to update my software to PWS API V2.
The old V1 API endpoint all return HTTP/410, even so it was suppose to be end of 2026!
Anyhow, If I add a wind, temp or any other parameters, I received a HTTP/500. Without any metrics parameters, it works, however no data is register!

curl -X GET -k -H 'Authorization: Bearer 9..0' -i 'https://stations.windy.com/api/v2/observation/update?wind=4.2&id=1....e&time=2026-01-13T13%3A41%3A00Z'
HTTP/2 500

but

curl -X GET -k -H 'Authorization: Bearer 9..0' -i 'https://stations.windy.com/api/v2/observation/update?&id=1....e&time=2026-01-13T13%3A42%3A00Z'
HTTP/2 200
]]>https://community.windy.com/topic/43284/we-are-sorry-but-something-broke.RSS for NodeSun, 11 Oct 2026 12:46:25 GMTSat, 17 Jan 2026 16:51:07 GMT60<![CDATA[Reply to We are sorry, but something broke. on Thu, 22 Jan 2026 10:51:39 GMT]]>@Francois-Lacroix It should now throttle by station PASSWORD. Also, a 429 status code is returned when the limit is hit, to make it clearer what is going on. I hope this solves your issue.

]]>https://community.windy.com/post/223822https://community.windy.com/post/223822Thu, 22 Jan 2026 10:51:39 GMT<![CDATA[Reply to We are sorry, but something broke. on Wed, 21 Jan 2026 11:56:55 GMT]]>@marekd I'm definitely hitting the throttling limit, as I get HTTP/403. I do manage few numbers of stations and growing. less restrictive would be nice. otherwise stationId specific

]]>https://community.windy.com/post/223769https://community.windy.com/post/223769Wed, 21 Jan 2026 11:56:55 GMT<![CDATA[Reply to We are sorry, but something broke. on Wed, 21 Jan 2026 07:02:45 GMT]]>@Francois-Lacroix Thank you for the feedback.

  • No, bulk processing is not available anymore. Are you hitting the throttling limit? We can make it less restrictive or stationId specific.
  • You can use the PWS endpoints (CRUD + list) to update stations programmatically. See the second group of endpoints: https://stations.windy.com/api-reference
]]>https://community.windy.com/post/223761https://community.windy.com/post/223761Wed, 21 Jan 2026 07:02:45 GMT<![CDATA[Reply to We are sorry, but something broke. on Tue, 20 Jan 2026 09:11:23 GMT]]>@marekd thanks the issue got solve in the weekend.
Quick questions:
I could not find a bulk processing available with the API v2, and there is an very strict rate limiting. Do you plan to implement it?
To my understanding you assume the station is stationary, the prevouis API allowed to specify the coords if or when there is movement. Do you plan to implement it?

]]>https://community.windy.com/post/223741https://community.windy.com/post/223741Tue, 20 Jan 2026 09:11:23 GMT<![CDATA[Reply to We are sorry, but something broke. on Mon, 19 Jan 2026 07:27:38 GMT]]>@Francois-Lacroix Sorry about the issues. We had some system problems over the weekend. Are you still seeing 500 errors, or is everything working as expected?

Regarding the 410 response: you can simply remove the stations property from your request. We’re sorry about this change, but it was not possible to handle station updates via the observation update request. This was the only backward-incompatible change we had to make. We tried hard to avoid breaking changes, but this one was unavoidable and the feature could not be kept.

We decided to return a 410 response to clearly communicate this to users. Your observation data is still safely stored, as the error message indicates. Only station metadata updates are no longer allowed.

I’ve also updated the 410 response message to be more instructive.

Thank you for letting us know!

]]>https://community.windy.com/post/223663https://community.windy.com/post/223663Mon, 19 Jan 2026 07:27:38 GMT<![CDATA[Reply to We are sorry, but something broke. on Sat, 17 Jan 2026 18:57:21 GMT]]>@Francois-Lacroix
I’m not sure about it but it could be due to this issue

]]>https://community.windy.com/post/223616https://community.windy.com/post/223616Sat, 17 Jan 2026 18:57:21 GMT