NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Packagist, #1087 most downloaded on Packagist
PHP Client for using Vonage's API.
Latest stable
4.15.0
Last release 1 months ago
19 Oct 2026
Ships unpredictably
gaps range from 1 weeks to 11 months
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
11 years old
138 releases · first in 2016
Drag across the ruler to compare, or tap a release to open it.
This patch fixes the incorrectly assigned AuthHandlers for the MessagesAPI. The behaviour now is that it will look for a KeyPair object, then use Basi
This patch fixes the incorrectly assigned AuthHandlers for the MessagesAPI. The behaviour now is that it will look for a KeyPair object, then use Basic in that order. If the Handler can't find the right auth, the exception will be thrown as before.
We also have new behaviour for incoming SMS webhooks that determine what entity it is (this is if you have configured both callback URLs from the Vonage Dashboard to point to the same route). If there is no text field present, it's a DeliveryReciept. If all other fields match the map, it's an IncomingSMS.
Full Changelog: https://github.com/Vonage/vonage-php-sdk-core/compare/4.0.4...4.0.5
This release fixes both a composer InstalledVersions bug and a bug in the new AuthHandler interfaces.
This release fixes both a composer InstalledVersions bug and a bug in the new AuthHandler interfaces.
Full Changelog: https://github.com/Vonage/vonage-php-sdk-core/compare/4.0.3...4.0.4
Your coding agent can read these notes before it upgrades. Set up the MCP server →
This release moves the isGsm7() method into a static one so that developers can make use of it.
This release moves the isGsm7() method into a static one so that developers can make use of it.
Full Changelog: https://github.com/Vonage/vonage-php-sdk-core/compare/4.0.2...4.0.3
This patch removes the requirement for the deprecated Composer Versions package as the Composer Runtime Environment is now used. Also a community shou…
This patch removes the requirement for the deprecated Composer Versions package as the Composer Runtime Environment is now used. Also a community shout out to @ankurk91 for removing the need for the php json ext in PHP8 as it's become default to include it.
Full Changelog: https://github.com/Vonage/vonage-php-sdk-core/compare/4.0.0...4.0.2
The `message` client (which uses the Vonage SMS API) has been marked as deprecated since 2.6.0. It has been removed. Please use the SMS client instead…
This is the next major release, that contains these major points of note:
message client (which uses the Vonage SMS API) has been marked as deprecated since 2.6.0. It has been removed. Please use the SMS client instead.text i.e. GSM-7 is now the default encoding type.Full Changelog: https://github.com/Vonage/vonage-php-sdk-core/compare/3.1.6...4.0.0
…to fix Laravel builds of PHP8.2 by suppressing deprecations within PHPUnit.
This release contains a number of minor bug fixes and enhancements, with its main purpose to fix Laravel builds of PHP8.2 by suppressing deprecations within PHPUnit.
Full Changelog: https://github.com/Vonage/vonage-php-sdk-core/compare/3.1.5...3.1.6
This release corrects documentation in several places to make it more accurate.
This release corrects documentation in several places to make it more accurate.
/check endpoint is really the check() method by @derickr in https://github.com/Vonage/vonage-php-sdk-core/pull/335Thanks Derick! Support the PHP Foundation, you can fund their work here: https://opencollective.com/phpfoundation
Full Changelog: https://github.com/Vonage/vonage-php-sdk-core/compare/3.1.4...3.1.5
Add Pay NCCO by @SecondeJK in https://github.com/Vonage/vonage-php-sdk-core/pull/330
You can now use the pay action as documented in the NCCO Pay Voice Documentation
Full Changelog: https://github.com/Vonage/vonage-php-sdk-core/compare/3.1.3...3.1.4
This release adds better support for developers needing to extract information back from the Verify API in a more explicit way. When getting an error
This release adds better support for developers needing to extract information back from the Verify API in a more explicit way. When getting an error back from Verify, you can now use getNetworkId() and getRequestId() if they are present.
Please note that while this fixes runtime on PHP8.1, Serialization in the Verification Client is still marked as deprecated, to be removed by v4 of th…
** Please note that while this fixes runtime on PHP8.1, Serialization in the Verification Client is still marked as deprecated, to be removed by v4 of the library.
Full Changelog: https://github.com/Vonage/vonage-php-sdk-core/compare/3.1.1...3.1.2
This minor release fixes a bug in Messages v1.
This minor release fixes a bug in Messages v1.
Full Changelog: https://github.com/Vonage/vonage-php-sdk-core/compare/3.1.0...3.1.1
This minor release adds the Messages v1 API functionality to the SDK. You can now send text/image/video/custom messages via WhatsApp, Facebook Messeng
This minor release adds the Messages v1 API functionality to the SDK. You can now send text/image/video/custom messages via WhatsApp, Facebook Messenger, Viber, SMS and MMS. Contains 2 minor bugfixes.
New namespace: messages. To send a message, create a new object that you want to send within this namespace i.e. Vonage\Messages\Channel\Viber\ViberText()
#318 Incorrect use of Cedilla for encoding #317 Version bump for dependencies
Thanks to @SoftCreatR + @Starfox64 for contributions
This release fixes a minor bug with the number status callback key reported in #271.
This release fixes a minor bug with the number status callback key reported in #271.
The previous release, triggered by #313 was actually a backwards-breaking change mistakenly released while cleaning up other old broken imports.
This is a hotfix release that fixes Laravel's usage of the deprecated message() client.
The previous release, triggered by #313 was actually a backwards-breaking change mistakenly released while cleaning up other old broken imports.
PLEASE NOTE: This was accidentally a backwards-breaking change not in line with Semver. Please update to 3.0.4, especially if you are using the messag…
This release is a housekeeping release that removes some old, dead imports relating to v3.0.0 removed API endpoints that were either not implemented or not supported.
PLEASE NOTE: This was accidentally a backwards-breaking change not in line with Semver. Please update to 3.0.4, especially if you are using the message() client.
This release adds PSR/log support for v3 and higher, in line with both Symfony and Laravel codebases for compatibility.
This release adds PSR/log support for v3 and higher, in line with both Symfony and Laravel codebases for compatibility.
This minor release is a composer dependency change to allow either v1.0 or 2.0 of psr/container.
This minor release is a composer dependency change to allow either v1.0 or 2.0 of psr/container.
This is to allow upstream packages (such as nexmo-laravel) to resolve successfully.
This release represents a major milestone, with several thousand lines of code marked deprecated being removed. It also contains some minor dependency…
This release represents a major milestone, with several thousand lines of code marked deprecated being removed. It also contains some minor dependency changes and a bugfix. As deprecated code is being removed, please take careful note where you might be affected by any of the signatures that are no longer present.
As always, I will be on hand for support where implementations need workarounds - the most common will probably be using the toArray() methods on entities for backward compatibility.
#302 getCountryPrefix on an an Insights object is now returned as a string
getCountryPrefix() string return typeArrayAccessThis release adds the necessary ReturnTypeWillChange attributes for PHP8.1 to the old v2 of the library.
This release adds the necessary ReturnTypeWillChange attributes for PHP8.1 to the old v2 of the library.
This minor release fixes the depreciated messages coming from PHPUnit and Prophesize.
This minor release fixes the depreciated messages coming from PHPUnit and Prophesize.
prophesize() depreciation noticesVonageTestCase class that implements the ProphesizeTrait## Fixed * #295 Removed automatic unicode detection when sending SMS. Default SMS type is now set to unicode, developers now have the option to set to
type is now set to unicode, developers now have the option to set to text if they wish by using the setType() method on the SMS or OutboundMessage class.# 2.9.2 ### Fixed * #276 - JWTs with sub should now generate properly under newer PHP versions
sub should now generate properly under newer PHP versions# 2.9.1 ### Fixed * #282 - SMS Throttling response is now handled as milliseconds instead of seconds * #282 - Fixed regex to not consume API rate limi
Nexmo/nexmo-laravel#62 - Landline Toll Free numbers can be searched for
# 2.8.1 ### Fixed * #278 - Fixed issue retrieving Conversations and Users clients where the service locator didn't know what to do ### Changed * #283
## Added - #272 - Added support for PSR-3 compatible logging solutions and a new debug feature to log requests/responses - #274 - Added support for th
detail field on some new Voice API incoming events (https://developer.nexmo.com/voice/voice-api/webhook-reference#event-webhook)content-id and entity-id fields to support regional SMS requirements, and a shortcut for enabling DLT on Indian-based SMS### Changed * #270 - Use the actual Guzzle package version to determine of 6 or 7 is in the project
### Added * #269 - Added PHP 8 Support
Don't be scared off by this large release! Most of it is under-the-hood syntax cleanup. Thank you to everyone during Hacktoberfest for the cleanup and
Don't be scared off by this large release! Most of it is under-the-hood syntax cleanup. Thank you to everyone during Hacktoberfest for the cleanup and help with the SDK!
The big addition was we added support for VAPI Language and Style (https://developer.nexmo.com/voice/voice-api/guides/text-to-speech), and fixed a bug when manually setting the Verify code length.
examples/ directory as the code snippets repo is much more up-to-date### Changed - #260 - Swapped out ocramius/package-versions for composer/package-versions-deprecated to work with Composer 2
ocramius/package-versions for composer/package-versions-deprecated to work with Composer 2# 2.4.1 ### Changed - #256 - Added support for PHPUnit 8 ### Fixed - #253, #254 - Fixed some typos in the README - #255 - \Vonage\Numbers\Client::sear
\Vonage\Numbers\Client::searchAvailable() now correctly handles filters using FilterInterfaceThis release includes a minimum version bump to PHP 7.2, as 7.1 is nearing full EOL. This also better allows us to support Guzzle 7 out of the box.
This release includes a minimum version bump to PHP 7.2, as 7.1 is nearing full EOL. This also better allows us to support Guzzle 7 out of the box.
### Fixed * #252 - Connect action's eventUrl was being set as a string, changed to single element array of strings
eventUrl was being set as a string, changed to single element array of strings### Added * #248 - Added \Vonage\Client\MapFactory::make() to always instantiate new objects ### Fixed * #248 - Fixed type in URL for Account Client F
\Vonage\Client\MapFactory::make() to always instantiate new objects\Vonage\Client\MapFactory::make() to always instatiate new objects### Added * #247 - Fixed missing fields on Standard/Advanced number insight getters ### Fixed * #246 - Fixed badge URLs in README
This release contains a major milestone where all the code is now under the \Vonage namespace! Do not worry though, any existing code using the \Nexmo
This release contains a major milestone where all the code is now under the \Vonage namespace! Do not worry though, any existing code using the \Nexmo namespace will still continue to work thanks to a new vonage/nexmo-bridge package which will translate between the two namespaces. The next time you update your Nexmo client to this or any subsequent 2.x releases, your code will continue to work with no changes.
It is recommended to start using the \Vonage namespace in any new code you create, but even new features added (like our PSD2 feature in this release) will work under either namespace. Developers will be able to update at their own pace.
vonage/nexmo-bridge as a dependency so \Nexmo namespaced code works with the new \Vonage namespace\Vonage\Client\APIResource can now specify headers for individual requests\Nexmo to \Vonage for all classes, interfaces, and traitsAdded country as a search option for Nexmo\Numbers\Client::searchOwned()
country as a search option for Nexmo\Numbers\Client::searchOwned()## Fixed * #235 - Adds a fix for calling the calls() API client
calls() API clientMinor bugfix release based on feedback:
Minor bugfix release based on feedback:
There were no known security vulnerabilities reported
This release focuses on deprecation of dead and old code, and preps many internal changes in regards to v3.0.0. Where possible upcoming v3.0.0 changes were backported where backward-compatibility could be maintained.
$client->voice() and $client->sms(), respectivelyNexmo\Client "show_deprecations" config option. This can help devs update in preparation in v3.0.0, and will be utilized in the future as things are deprecated.toArray() serialization method, to discourage direct use of jsonSerialize()fromArray() hydration methodNexmo\Client\APIResource and Nexmo\Entity\IterableAPICollectionNexmo\Client\Factory\MapFactory is now PSR-11 compliant, and can use factoriesNexmo\Verify\Request for starting new Verification requestsFor a detailed list of things that may impact an application, enable the show_deprecations Nexmo\Client option to see deprecation notices for specific code flows.
$client->messages($filter) to search has been deprecated in favor of bespoke search methodsNexmo\Verify\Verification objects full functionality has been deprecated, and will be used only as a value object for search requests in the futureNexmo\Conversations and Nexmo\User have been deprecated and will be removed in the future as the feature is in Beta status and has diverged from this implementationNexmo\Voice\Call and Nexmo\Voice\Message have been deprecated and will be removed in the future as the TTS API is deprecatedNexmo\Client\Exception\ThrottleException and has been implemented in SMS and the Numbers APINexmo\SMS\Client::send() as it now returns a fully hydrated collection object as a response, however this needs to be updated in Laravel itself via an update to nexmo/laravel and laravel/nexmo-notification-channel Nexmo\SMS\Client::send() as it now returns a fully hydrated collection object that is much more up-front it is not a single objectNexmo\SMS\Webhook\InboundSMSNothing published for this version
Nothing published for this version
No new security fixes were added
This release contains a few quality of life changes for the SDK. We have added support for sending a Workflow ID to our Verify API, as well as the ability to search your existing numbers for ones that are attached to an application or not, or for all the numbers attached to a specific application.
has_application and application_idNo new security fixes were added
This release contains a few under-the-hood changes. The largest is the bump to PHP 7.1, which may affect some customers. If you are on an older version of PHP, you will be limited to SDK v1.8.1 or lower.
We have also renamed this package into nexmo/client-core and added a new wrapper package to replace nexmo/client. For most customers this process should be seamless, and composer should automatically handle the change. This change is made to remove a collision between our package and others that may supply Guzzle themselves.
If you use the SDK to search for numbers, please be advised that we did change the response for when no numbers are found. It will now return an empty array instead of throwing an exception. Other searches are not affected and will continue to throw their original exceptions.
Exceptions will now support an additional getEntity() method that returns additional information about what happened. In many cases this is the response from the server, to make it easier to understand the API error message. Exceptions continue to return error codes and messages like before, but the getEntity() method can be used for better context during error handling.
Please check the rest of the changelog for a full list of changes.
getEntity() method to get more information during errorsnexmo/client-corenexmo/clientIncrease minimum version of Diactoros to 1.8.4 due to security issues
Add support for Applications API v2
Add support for Applications API v2
Add support for supplying an NCCO inline when placing a call
$call = new Call();
$call->setTo('TO_NUMBER')
->setFrom('FROM_NUMBER')
->setNcco([
[
'action' => 'talk',
'text' => 'This is a text to speech call from Nexmo'
]
]);
$client->calls()->create($call);
Add support for account configuration
Add support for account configuration
Nothing published for this version
Bugfix for message signature checking
Bugfix for message signature checking
Customisable base URL for testing purposes
Improved unicode character detection for automatically setting the SMS type
Adds support for message signing with the SMS API
Adds support for message signing with the SMS API
Add support for the Secret Management API, allowing you to rotate your API secrets for better API security.
Add support for the Redact API, which allows you to redact information about your SMS, Voice, Verify (and more!) requests on the Nexmo platform
Fix date_start and date_end when fetching a call collection with a filter. The date must be in UTC
date_start and date_end when fetching a call collection with a filter. The date must be in UTCAllow searching for available toll-free numbers
Partial Nexmo Stitch support (Conversations, Users)
Number objectgetFinalStatus() method for SMS messagesFix POST /conversation response parsing
POST /conversation response parsingAllow Container type credentials to generate JWTs as well as Keypair only
Container type credentials to generate JWTs as well as Keypair onlyOne column per quarter.