Sinch Numbers API
POST /availableNumbers/{id}:rent endpoint removal
Deprecated, no dateSubscribe to Sinch Numbers APIShare
Sinch Numbers API has deprecated the POST /availableNumbers/{phoneNumber}:rent endpoint without a shutdown date. Calls to this available numbers activation endpoint will fail after it is fully retired. The endpoint currently only supports US LOCAL numbers.
Calls it hits
POST /availableNumbers/{id}:rent
What to use instead of these calls
New integrations should use the Number Order API instead.
In Sinch Numbers API's words
The Available Numbers activation endpoints, "Activate a new phone number" ( availableNumbers/{phoneNumber}:rent ) and "Rent any number that matches the criteria" ( availableNumbers:rentAny ), are deprecated and only support US LOCAL numbers.
Facts
- API
- Sinch Numbers API
numbers.api.sinch.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Changelog
- Last updated
- Verified
- , against Sinch Numbers API's own pages
Questions
When does this change take effect?
Sinch Numbers API deprecated POST /availableNumbers/{id}:rent without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Sinch Numbers 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.
More from Sinch Numbers API 3
-
No date
POST /availableNumbers:rentAnyEndpoint removal Deprecated, no date -
No date
POST /v1/projects/{id}/availableNumbers:rentAnyEndpoint removal Deprecated, no date -
No date
POST /v1/projects/{id}/availableNumbers/{id}:rentEndpoint 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.