If you sync users out of monday.com — an SSO deprovisioning job, an HR-to-monday roster sync, a SCIM-ish reconciliation script, a dashboard that counts seats, anything that runs query { users { id email } } — there's a change that went live on July 1, 2026 and fails in the worst way: it returns a 200, valid JSON, and the wrong number of users.
monday.com versions its API by date. Version 2026-07 entered release-candidate on April 1, 2026 and became the Current (default stable) version on July 1, 2026. The detail that makes this silent is monday's own documented default:
If you don't pass an API-Version header, your app will always get the Current version.
So every integration that doesn't pin an explicit version — and a lot of them don't, because the SDKs make it optional — rolled onto 2026-07 on July 1 with no deploy, no changelog read, no error. Integrations pinned to an older version aren't safe either: when monday deprecates a version, requests to it fall forward to the Maintenance version (that's exactly what the February 15, 2026 deprecation did — it routed 2025-01 and 2024-10 to 2025-04). Either path lands you on the new Query.users behavior eventually.
And the 2026-07 release is a full overhaul of the User entity. Most of it is documented as a breaking change. The parts that bite are the ones that don't break loudly.
