Sinch Numbers API
POST /v1/projects/{id}/availableNumbers:rentAny endpoint removal
Deprecated, no dateSubscribe to Sinch Numbers APIShare
The POST /v1/projects/{id}/availableNumbers:rentAny endpoint is deprecated without a shutdown date and only supports US local numbers. The endpoint remains available for existing integrations, but affected calls will eventually fail. Sinch Numbers API advises new integrations to move to a replacement API.
Calls it hits
POST /v1/projects/{id}/availableNumbers:rentAny
What to use instead of these calls
Order by criteria using the Number Order API by calling POST /v1/projects/{projectId}/numberOrders:createNumberOrder and then POST /v1/projects/{projectId}/numberOrders/{numberOrderId}/submit.
In Sinch Numbers API's words
are deprecated and only support US LOCAL numbers. They remain available for existing integrations, but new integrations should use the Number Order API.
Facts
- API
- Sinch Numbers API
numbers.api.sinch.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Sinch Numbers API's own pages
Questions
When does this change take effect?
Sinch Numbers API deprecated POST /v1/projects/{id}/availableNumbers:rentAny 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 /availableNumbers/{id}:rentEndpoint 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.