Weave Code
Client Laravel Package
nexmo/client
Nexmo Client is the legacy PHP SDK for sending SMS, making voice calls, and managing Nexmo/Vonage APIs. It provides simple authentication and request helpers for PHP apps, though new projects should use the maintained Vonage client.
Wrapper package to bring in the nexmo/client-core code and an HTTP client
Frequently asked questions about Client
- How do I install nexmo/client in a Laravel application?
- Install it with composer require nexmo/client. It is a Composer metapackage, so the actual client code comes from nexmo/client-core and it also selects a PSR-18 HTTP client for you. There is no Laravel service provider or config file to publish, so you instantiate Nexmo\Client manually with your credentials.
- How do I configure Nexmo credentials in Laravel?
- There is no Laravel-specific configuration because the package ships no service provider, facade, or config file. Put your credentials in environment variables such as NEXMO_KEY and NEXMO_SECRET, then pass them to a Basic credentials object when constructing Nexmo\Client. You can resolve that client from a Laravel service provider or container binding that you write yourself.
- Does nexmo/client support Laravel 10 and Laravel 11?
- nexmo/client has no official Laravel version matrix; it is a plain PHP library that Laravel can use if its PHP and Guzzle constraints fit your application. The 2.4.0 release declares PHP 7.2+ and Guzzle 7, so a modern Laravel 10 or 11 app may install it, but that does not mean the package is tested against those framework versions. For new Laravel work, prefer the maintained vonage/client package.
- What PHP version does nexmo/client 2.4.0 require?
- Version 2.4.0 requires PHP 7.2 or newer and Guzzle 7. That declared minimum does not prove PHP 8.1 or 8.2 is tested; check the repository CI if that matters to you. Older releases used older Guzzle versions and may have different PHP floors.
- How do I send an SMS with nexmo/client?
- Create a Nexmo\Client with your API key and secret, then call the message endpoint with to, from, and text values. The legacy SDK handles authentication and response parsing for you. Delivery receipts and inbound message handling are part of the API surface, but you should confirm the specific endpoints you need are still supported by Vonage.
- How do I verify a phone number with nexmo/client?
- Use the client's verify API to start a verification request with the number and brand, then check the code the user received against the returned request ID. The legacy SDK wraps the older Nexmo Verify endpoints, so confirm they are still enabled for your Vonage account. New implementations should use the maintained Vonage SDK and its current verification API.
- How can I test nexmo/client code without sending real SMS?
- nexmo/client does not provide a Laravel fake or a built-in test transport. Mock or stub the Nexmo\Client in your application code, or inject a fake PSR-18 HTTP client if you are testing at the HTTP boundary. Keep real credentials out of tests and avoid hitting live SMS or verification endpoints.
- Is nexmo/client deprecated, and what should I use instead?
- nexmo/client is the legacy Nexmo SDK and has been superseded by vonage/client and vonage/client-core after the Nexmo-to-Vonage rebrand. The 2.4.0 release is a dependency-hygiene bump after a long gap, not evidence of a renewed maintenance cadence or a security-response commitment. Use vonage/client for new projects and treat nexmo/client as transitional code.
- Does nexmo/client 2.4.0 work with Guzzle 6?
- Version 2.4.0 requires Guzzle 7, while earlier nexmo/client releases used Guzzle 6. A routine composer update can therefore pull Guzzle 7 and conflict with packages pinned to Guzzle 6, or fail on a PHP 7.0/7.1 host. If you cannot move your HTTP client, stay on an older release only as a short-term stopgap and plan the migration.
- Is nexmo/client safe for production use?
- Treat it as medium-high risk for production: the vendor has rebranded to Vonage, the SDK is frozen at a 2020-era API surface, and there is no clear security-response commitment. The 2.4.0 release reduces some Guzzle 6 audit noise but does not resolve vendor drift or abandoned-endpoint risk. It can serve as a stopgap, but any capability built on it should be planned for rewrite on vonage/client.
Weaver
How can I help you explore Laravel packages today?