api.nexmo.com · CommunicationSubscribeShare
Vonage API breaking changes
The breaking changes Vonage API announced that Okapi tracks: 3 in all.
Do you run the Vonage API? Make sure your users call it right →
At a glance
- API host
api.nexmo.com- Kind
- Communication
- Versions with breaking changes
- v0.1 (1)
- Next breaking change
- Number Insight API removal,
- Breaking changes tracked
- 1 breaking change coming up and 2 with no date yet
- Last updated
Coming up 1
-
/ni/*Removal Stops workingin 90 days
Deprecated, no date yet 2
-
No date
/v0.1/dispatch*Removal Deprecated, no date -
No date
/verify/*Version retirement Deprecated, no date
Where Okapi reads it
- OpenAPI spec developer.vonage.com/api/v1/developer/api/file/messages?format=json&vendorId=vonage
- OpenAPI spec developer.vonage.com/api/v1/developer/api/file/verify.v2?format=json&vendorId=vonage
- OpenAPI spec developer.vonage.com/api/v1/developer/api/file/voice?format=json&vendorId=vonage
- Announcement developer.vonage.com/en/api/number-insight
- Announcement developer.vonage.com/en/dispatch/overview
- Announcement developer.vonage.com/en/verify/verify-v1/overview
Know before your API calls break.
Okapi finds the calls a breaking change hits in your code and opens the pull request that fixes them.
Add to GitHub