/v1/* → endpoint removal
Calendly API
Deprecated, no date
Calendly API v1 is being retired without an announced shutdown date. This deprecation affects all /v1/* endpoints. Once retired, calls to these endpoints fail.
Calls it hits
/v1/*
What to use instead of these calls
Integrations must migrate to API v2. Refer to the migration guide for details.
In Calendly API's words
Calendly API v1 is being retired. All integrations must migrate to API v2. See our [migration guide](/docs/getting-started/how-to-migrate-from-api-v1-to-api-v2) for details.
Facts
- API
- Calendly API
api.calendly.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Changelog
- Last updated
- Verified
- , against Calendly API's own pages
Questions
When does this change take effect?
Calendly API deprecated /v1/* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Calendly API has not given a shutdown date yet.
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.
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.