On 2025-09-10, around 14:30 UTC, the /batch endpoint stops working. All query to /batch that were running fine for years, all get 400 response, with message “Invalid value for urls”.
We found no change log about it, we did not get any email of that future change, but we found that, on the documentation, that line was added recently:
“Forge and OAuth2 apps cannot access this REST resource.”
According to wayback machine, that line was not there on May 2025.
(edit) that message was added on all api calls in the documentation, but for us, only /batch is not working. So that is not the issue. /batch is really in trouble right now.
Can we get some informations about that change, and why there were no announcement about it?
Will you rollback that and make it work again?
In case someone is interested…
We got a techical response from Trello support, in a very fast response time, which is very appreciated.
In our app (Bridge24.com), we were querying batch using the “array” of urls, and it worked for years.
Something like: urls=url1, urls = url2, … And it was fine. Until yesterday.
The good way to query urls in batch is: urls=url1,url2.
I am almost certain we found a samplle code somewhere that was using the wrong method, but that worked for years, until yesterday.
The list of urls with comma is now the method in place in our app.
The “new way” you describe it is the way I’ve always used it (and I did not have issues yesterday), but have had similar issues over the years where the format of your call suddenly break (example if card pos = 0 was suddenly an issue, or when sending members in a certain way suddenly did not work)