Vonage API
Number Insight API removal
Stops workingSubscribe to Vonage APIShare
On February 4, 2027, Vonage will sunset Vonage Number Insights and remove the service. Calls to endpoints under /ni/* will fail after this date. Any integration relying on these endpoints must be updated before the cutoff.
Calls it hits
/ni/*
What to use instead of these calls
Migrate your calls to the Identity Insights API instead.
In Vonage API's words
Effective February 4, 2027, Vonage will sunset Vonage Number Insights.
Facts
- API
- Vonage API
api.nexmo.com - Kind
- Removal
- Takes effect
- February 4, 2027
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Vonage API's own pages
Questions
When does this change take effect?
Calls to /ni/* on Vonage API stop working on February 4, 2027.
What happens to calls after February 4, 2027?
They fail from that day.
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 Vonage API 2
-
No date
/v0.1/dispatch*Removal Deprecated, no date -
No date
/verify/*Version retirement 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 before February 4, 2027.