Just to also dump here:
It feels like they don’t know what they want to do with their API.
Every year, specially at the start of the year, there’s breaking changes that force us to change what was working fine, for what feels no real benefit for the end-user.
It is a constant work to maintain an application based on the Monday API.
Do they communicate about the changes? Yes!
But:
First: Not every change is communicated, for example, this one is not on the latest changelog.
Last year I also had another problem with sending files via the API to a file column/update, and that was not on the changelog (at the time at least).
The year before, they changed the API to a non-communicated time, which caught us by surprise (2023-01-16, if my memory doesn’t fail me).
And also recently, they altered the response from the API on the board’s request (only god and the devs knows why). Didn’t change much on the response, but breaks systems that need consistent responses.
This issue was also, not communicated, and was also, ran on a non-communicated time (2025-12-17, at 11:43 AM, GMT -3, caught this on my application logs).
Second: The issue stays the same. I have to continue reading changelogs, continue changing the same applications, for no real benefit. Even if my application just uses ONE request, it is doomed to the API updates.
The problem becomes bigger every time you create something that relies on the API.
Third: They are forcing us to create a middleware to just communicate with the API for a simple query.
That itself brings lots of problems to be solved, like authentication, security, reliability, resources, time, knowledge, IP address.
How do I explain to my client that the system that he relies on every day:
stopped working out of nowhere
it’s not my fault
and now they will need to pay me for an issue that dint exist in the first place.
What if I want, the user, to use a website that uses the Monday API, but I don’t want to make available any middleware to the entire world? Then I’m screwed.
“Just use a VPN” No, why should I? That’s unreasonable.
The issue also goes over the self-hosted applications. Not even applications hosted inside Monday can use the API after this recent update (I’m talking about web apps made by end-users, and hosted on Monday as an application.
Year after year, they add something, next update they deprecate the exact same thing (as the only example that I can remember, settings_str field on columns, because it is recent)
The API is overcomplicated, you have to make multiple requests to get a simple data
The fact that someone had to make a meme about the API speaks for itself. I’ve never seen that in my entire LIFE
These issues are so consistent, happening year, after year, after year, that it makes= me believe they don’t really want us to use the API, neither build applications that rely on it.
Searching for it on this forum, you can see the same issues happening since 2021:
https community monday com/t/api-calls-about-boards-make-no-sense/78811 (removed the dots because for some reason, I can’t add more than 3 links to this post, like that would stop people from doing it…)
Anyway, I’m sorry if I went overboard or if I am mistaken on the rant, but that’s how my experience working with the Monday API has been for the last 3 years.
If you are reading this, and you still want to build something that uses the Monday API, don’t, just don’t.