NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Packagist
Packagist, #4261 most downloaded on Packagist
Deprecated PHP Client for using Vonage's API - please use vonage/client-core
Latest stable
2.9.2
Last release 6 years ago
no release in 18 months
Ships fairly regularly
a new release about every 3 weeks
Most releases are documented
notes for 36 of 41 stable releases
Nothing withdrawn
no release was ever pulled
11 years old
54 releases · first in 2016
Drag across the ruler to compare, or tap a release to open it.
Vonage#276 - JWTs with sub should now generate properly under newer PHP versions
sub should now generate properly under newer PHP versionsVonage#282 - SMS Throttling response is now handled as milliseconds instead of seconds
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Nexmo/nexmo-laravel#62 - Landline Toll Free numbers can be searched for
Vonage#278 - Fixed issue retrieving Conversations and Users clients where the service locator didn't know what to do
Vonage#272 - Added support for PSR-3 compatible logging solutions and a new debug feature to log requests/responses
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 SMSUse the actual Guzzle package version to determine of 6 or 7 is in the project
2.7.0 Added Added PHP 8 Support
Added Roave Security Advisories as dev-requirement to prevent usage of packages with known security vulnerabilities
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.
As a reminder, this library has entered maintenance support, so please begin your migration to vonage/client or vonage/client-core as soon as possible.
examples/ directory as the code snippets repo is much more up-to-dateexamples/ directory as the code snippets repo is much more up-to-dateSwapped 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 2ocramius/package-versions for composer/package-versions-deprecated to work with Composer 2Vonage#256 - Added support for PHPUnit 8
\Vonage\Numbers\Client::searchAvailable() now correctly handles filters using FilterInterface\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.
For the next 12 months, nexmo/client and nexmo/client-core will be only receiving bug or security fixes. The good news is that this release can allow…
Nothing related to async, sorry.
This release contains two major milestones!
The first is 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.
The second is that we have complete parity between this repository and the Vonage repo, and this repo and package is now going into bug/security-fix-only mode. For the next 12 months, nexmo/client and nexmo/client-core will be only receiving bug or security fixes. The good news is that this release can allow you, today, to use the \Vonage and \Nexmo namespaces at the same time. Your old code will continue to function without any changes, and you can work the namespace change right away with new code. Upgrading should be as easy as replacing \Vonage with \Nexmo (your mileage may vary).
We recommend that developers switch to vonage/client or vonage/client-core as soon as they can, but any bugs or security fixes will still be ported to the Nexmo packages.
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\Vonage\Client\MapFactory::make() to always instatiate new objects\Nexmo to \Vonage for all classes, interfaces, and traitseventUrl was being set as a string, changed to single element array of stringsAdded 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 onlyExpose JWT generation to be used with our Javascript SDKs
Add support for listing all conversations for a single user
Nothing published for this version
Add getCost() support to Number objects - thanks @arubacao!
getCost() support to Number objects - thanks @arubacao!Add support for submitting SMS/Voice conversions to Nexmo
Fix User-Agent header to use Title-Case
VERSION constant in Client.phpAdd ability to specify additional parameters when searching numbers that you own
Fix issue with PUT /call where the endpoint may return a 204 response with no body payload
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.