Weave Code
Client Core Laravel Package
nexmo/client-core
Core PHP library for Nexmo/Vonage REST APIs, providing shared client infrastructure, request handling, and exception classes used by the Nexmo PHP SDK. Helps integrate SMS, voice, verification, and related communication services.
nexmo/client-core is the shared PHP foundation for Nexmo API clients, providing a unified Client with credential handling, request signing, and consistent error and response behavior across services such as SMS, Voice, Verify, and Number Insight. It lets applications integrate Nexmo APIs without duplicating transport and authentication logic.
- Unified entry point for multiple Nexmo APIs
- Credential and request-signature management
- Configurable HTTP transport and middleware
- Consistent exceptions and response handling
- Extensible resource architecture for custom APIs
Frequently asked questions about Client Core
- What is nexmo/client-core and is it still maintained?
- nexmo/client-core is the shared PHP SDK foundation for Nexmo/Vonage API clients, handling requests, authentication, and responses for SMS, Voice, Verify, and related APIs. It is deprecated and archived, with the last release in 2021, and the repository directs users to vonage/client-core. Treat it as legacy-only and do not standardize new Laravel work on it.
- Can I use nexmo/client-core in a Laravel application?
- Yes, you can install it with Composer because it is a plain PHP library, but Laravel integration is not native. You would own configuration, dependency injection bindings, credential management, HTTP client behavior, webhook handling, and error mapping. Use a thin application-owned adapter if you must retain it.
- Which Laravel and PHP versions work with nexmo/client-core?
- There is no guaranteed Laravel or PHP version support because the package is archived and old. You must validate PHP compatibility, Guzzle and PSR-7 constraints, autoloading, and dependency conflicts before installing. Expect compatibility work even if Composer resolution succeeds.
- How do I install nexmo/client-core with Composer?
- You can run composer require nexmo/client-core, but that should only happen for an existing legacy integration with a defined migration window. Run a Composer dependency audit and static analysis first, because stale HTTP dependency constraints can conflict with a modern Laravel application. For new code, install vonage/client-core instead.
- What is the migration path from nexmo/client-core to vonage/client-core?
- Inventory all Nexmo/Vonage API calls, credentials, webhook routes, queued jobs, and stored response payloads first. Put an internal gateway or adapter around the current SDK, add contract tests for outbound requests and webhook parsing, then migrate to vonage/client-core behind that same interface. Canary the change, monitor it, and remove nexmo/client-core and old credentials once stable.
- Is nexmo/client-core safe for production use?
- It carries high technical risk because it is archived, last released in 2021, and has no upstream security patch stream. Risks include unpatched issues, stale Guzzle/PSR-7 constraints, PHP/Laravel incompatibility, and vendor API drift. Retain it only as a short-lived compatibility layer with pinned versions, an assigned owner, and a migration deadline.
- Does nexmo/client-core support SMS, Voice, Verify, and Numbers APIs?
- The library is described as providing PHP API support for SMS, Voice, Text-to-Speech, Numbers, Verify (2FA), and more. However, because the package is archived, its methods and response objects may not match current Vonage API behavior. Verify each endpoint against current vendor documentation and cover critical calls with contract tests.
- Should I use nexmo/client-core or direct HTTP calls in Laravel?
- If your integration is narrow, direct signed HTTP calls behind a small internal gateway can be simpler and reduce SDK lock-in. If you already have working Nexmo SDK code, isolate it behind an adapter before deciding. In either case, new development should target vonage/client-core or direct API calls, not nexmo/client-core.
- How do I handle webhooks and authentication with nexmo/client-core in Laravel?
- The application must own webhook routes, signature verification, credential management, retries, idempotency, and error mapping because the SDK does not provide Laravel conventions. Keep credentials out of logs and test webhook parsing against stored payloads. Use an adapter so authentication and webhook behavior can move to vonage/client-core without changing controllers or jobs.
- What are the best alternatives to nexmo/client-core for Laravel?
- The official successor is vonage/client-core, which should be evaluated behind the same adapter interface. For simple integrations, direct signed HTTP calls may be preferable to reduce dependency risk. Laravel-native notification channels or community packages can also be considered, but validate their Laravel version support, maintenance status, and API coverage before adopting them.
Weaver
How can I help you explore Laravel packages today?