Quo API (formerly OpenPhone)
phoneNumberId body parameter removal on POST /v1/messages
Deprecated, no dateSubscribe to Quo API (formerly OpenPhone)Share
The body parameter phoneNumberId on POST /v1/messages has been deprecated without a shutdown date. Calls continuing to rely on this parameter will eventually fail once it is fully removed. Quo API (formerly OpenPhone) announced this change on October 21, 2024.
Calls it hits
POST /v1/messagesbody parameter phoneNumberId
What to use instead of these calls
Send the sending Quo number in from instead of phoneNumberId.
In Quo API (formerly OpenPhone)'s words
The phoneNumberId field for “send text message” has been deprecated. Please use from instead.
Facts
- API
- Quo API (formerly OpenPhone)
api.quo.com - Kind
- Parameter removal
- 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 POST /v1/messages, body parameter phoneNumberId 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
/v0/*Version retirement 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.