/api/v1/* → version retirement
Calendly API v1
Stopped working
On August 27, 2025, Calendly retired API v1, making all /api/v1/* calls no longer available. Any requests sent to these endpoints after this date fail. The shutdown also retires associated v1 webhooks.
Calls it hits
/api/v1/*
What to use instead of these calls
Migrate to API v2 using a personal access token or OAuth, as API v1 keys do not work with v2. Because v2 payloads differ from v1, moving requires updating your authentication setup and adapting your request and response structures.
API v1 keys do not work with v2: someone must create a personal access token or an OAuth app.
In Calendly API v1's words
The v1 API and Webhooks have been retired as of 8/27/25 and are no longer available.
Facts
- API
- Calendly API v1
calendly.com - Kind
- Version retirement
- Announced
- March 26, 2025
- Takes effect
- August 27, 2025
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Calendly API v1's own pages
Questions
When does this change take effect?
Calls to /api/v1/* on Calendly API v1 stopped working on August 27, 2025.
What happens to calls after August 27, 2025?
They have failed since August 27, 2025.
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.