- What is laravel-notification-channels/jusibe used for?
- It is a Laravel notification channel that sends SMS messages through Jusibe, a Nigerian bulk SMS platform. It plugs into Laravel's native notification system, so you dispatch texts with $user->notify() the same way you send mail or database notifications. The package provides a JusibeChannel, a fluent JusibeMessage value object, and a thin HTTP client wrapping Jusibe's API.
- Which Laravel versions support the Jusibe notification channel?
- The package targets Laravel 5.3, the release where notification channels were introduced, and its last release was in April 2020. Its illuminate/support and Guzzle constraints almost certainly block installation on Laravel 8 and newer. Check composer.json and run composer require in a scratch project before assuming it resolves on your version.
- How do I install laravel-notification-channels/jusibe?
- Require it with Composer using composer require laravel-notification-channels/jusibe. Installation only succeeds if your PHP, Laravel, and Guzzle versions satisfy the package's constraints, which are pinned to the Laravel 5.3 era. On a modern Laravel app expect a dependency conflict, so plan to vendor or fork the code instead.
- How do I configure Jusibe API credentials in Laravel?
- Add your Jusibe key and token to config/services.php, typically under a jusibe entry, and keep the actual values in your .env file rather than in source control. The channel's service provider reads those config values when it builds the API client. In a fork, point that config at your secret manager instead.
- How do I send an SMS notification with Jusibe in Laravel?
- Add a toJusibe() method to your notification class that returns a JusibeMessage describing the recipient and content, and implement routeNotificationForJusibe() on the notifiable model to supply the phone number. Then dispatch it normally with $user->notify(new YourNotification()). No Jusibe-specific code is needed in your controllers or services.
- Is laravel-notification-channels/jusibe still maintained?
- No. The last release was 2020-04-26, there have been no commits since, and the package has roughly 8 stars and zero dependents. There is no upstream to deliver security or compatibility patches, so ownership of the code effectively transfers to you on day one. Treat it as reference source code rather than a dependency.
- Can I use this Jusibe channel on Laravel 9, 10, 11, or 12?
- Not as a straight Composer install. The package's Illuminate and Guzzle constraints, plus changes to the Notification contract method signature, mean it will almost certainly fail to resolve or run on current Laravel releases. The practical route is to copy JusibeChannel, JusibeMessage, and the API client into your app under app/Notifications/Channels and swap the raw Guzzle calls for Laravel's Http facade.
- How do I test Jusibe SMS notifications without calling the real API?
- The package ships no verified test suite, so plan to write your own. After vendoring the channel, use Http::fake() to stub Jusibe's endpoints and assert the outgoing request payload, then add a feature test that fires the notification and checks the recipient and message body. Also cover failure paths such as timeouts and non-200 responses.
- Does the Jusibe channel support delivery receipts, webhooks, retries, or unicode messages?
- No. Expect no delivery-receipt or webhook handling, no idempotency keys, no retry semantics, and no multipart or unicode message-length accounting. These capabilities are what make SMS auditable in production, and you will have to build them yourself on top of the thin client. Budget for that work before adopting the package.
- What are the alternatives to using this Jusibe package?
- You can use another laravel-notification-channels SMS driver, such as Twilio or Vonage, if Jusibe is not a fixed vendor requirement. A more durable option is to define an internal SmsSender contract in your app and make the Jusibe implementation one adapter behind it, which lets you add failover or switch gateways without touching notification classes. Given the package's age, most teams vendor the code and wrap it that way regardless.