Cal.com API
/v1/* version retirement
Stopped workingSubscribe to Cal.com APIShare
On April 8, 2026, Cal.com API shut down API v1. All endpoints matching /v1/* were removed and calls to them fail. Requests sent to these routes no longer succeed because the entire version was retired.
Calls it hits
/v1/*
What to use instead of these calls
Direct calls to the v2 API base endpoint with the API key in an Authorization Bearer header and a cal-api-version header such as 2024-08-13. Moving from v1 requires following the endpoint-by-endpoint migration guide rather than simply updating the base path.
In Cal.com API's words
API v1 was shut down on April 8, 2026. All v1 endpoints have been removed.
Facts
- API
- Cal.com API
api.cal.com - Kind
- Version retirement
- Takes effect
- April 8, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Cal.com API's own pages
Questions
When does this change take effect?
Calls to /v1/* on Cal.com API stopped working on April 8, 2026.
What happens to calls after April 8, 2026?
They have failed since April 8, 2026.
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.
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.