Quo API (formerly OpenPhone)
/v0/* version retirement
Deprecated, no dateSubscribe to Quo API (formerly OpenPhone)Share
Endpoints under /v0/* are deprecated without a shutdown date. Calls made to these endpoints will eventually fail. Quo API (formerly OpenPhone) announced on October 21, 2024, that /v0 endpoints have been deprecated in favor of /v1.
Calls it hits
/v0/*
What to use instead of these calls
Call the same resources under /v1 instead, such as GET /v1/calls or POST /v1/messages.
In Quo API (formerly OpenPhone)'s words
/v0 endpoints have been deprecated. Please use /v1 instead.
Facts
- API
- Quo API (formerly OpenPhone)
api.quo.com - Kind
- Version retirement
- Announced
- October 21, 2024
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Quo API (formerly OpenPhone)'s own pages
Questions
When does this change take effect?
Quo API (formerly OpenPhone) deprecated /v0/* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Quo API (formerly OpenPhone) 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.
More from Quo API (formerly OpenPhone) 3
-
No date
POST /v1/messagesParameter removal Deprecated, no date -
No date
GET /v1/callsParameter removal Deprecated, no date -
No date
GET /v1/messagesParameter removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.