Vonage API
Dispatch API removal
Deprecated, no dateSubscribe to Vonage APIShare
Vonage deprecated the Dispatch API without a shutdown date, closing it to new users on August 31, 2025 while continuing support for existing users. The change targets calls to /v0.1/dispatch* endpoints. Subsequent calls outside supported usage will fail.
Calls it hits
/v0.1/dispatch*
What to use instead of these calls
Send with failover directly in the Messages API by submitting POST /v1/messages with a failover list.
In Vonage API's words
Product deprecation notice From August 31st 2025, the Vonage Dispatch API will be closed to new users, though the product will continue to be supported for existing users.
Facts
- API
- Vonage API
api.nexmo.com - Kind
- Removal
- Announced
- August 31, 2025
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Vonage API's own pages
Questions
When does this change take effect?
Vonage API deprecated /v0.1/dispatch* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Vonage 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 Vonage API 2
-
/ni/*Removal Stops workingin 90 days -
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.