monday.com API
/v2* version retirement
RedirectsSubscribe to monday.com APIShare
On January 15, 2027, default routing for /v2* calls without an api-version header will change. monday.com API will answer these requests from a newer version instead of the previous default. After that day, calls missing the header are redirected to version 2027-01 as the new Current release.
Calls it hits
/v2*no api-version header
What to use instead of these calls
Send API-Version with the version the calls are built for. On January 15, 2027, calls without this header will automatically receive 2027-01, the new Current version.
In monday.com API's words
Current: Used as the default version when no header is passed. Version name: 2027-01; Current (default): January 15th, 2027
Facts
- API
- monday.com API
api.monday.com - Kind
- Version retirement
- Takes effect
- January 15, 2027
- 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?
From January 15, 2027, monday.com API answers calls to /v2*, no api-version header from a newer version.
What happens to calls after January 15, 2027?
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 Redirected
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix before January 15, 2027.