monday.com API
/v2* version retirement
RedirectedSubscribe to monday.com APIShare
Since February 15, 2026, monday.com API answers calls to /v2*, header api-version: 2025-01 from a newer version.
Calls it hits
/v2*header api-version: 2025-01
What to use instead of these calls
Send a Current or Maintenance version in API-Version (the release schedule names them) and make the changes its release notes list; past this day monday answers 2025-01 with the Maintenance version.
In monday.com API's words
Version name: 2025-01; Deprecated: February 15th, 2026. Any request to a version of the API that has been deprecated will get the Maintenance version.
Facts
- API
- monday.com API
api.monday.com - Kind
- Version retirement
- Takes effect
- February 15, 2026
- Calls after that day
- Answered by a newer version
- Source
- Lifecycle page
- Last updated
- Verified
- , against monday.com API's own pages
Questions
When does this change take effect?
Since February 15, 2026, monday.com API answers calls to /v2*, header api-version: 2025-01 from a newer version.
What happens to calls after February 15, 2026?
monday.com API answers them from a newer version. The response can differ from what your code expects.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from monday.com API 2
-
/v2*Version retirement Redirected -
/v2*Version retirement Redirectsin 70 days
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.