Weave Code
Kudisms Notification Laravel Package
toneflix/kudisms-notification
A Laravel notification channel for sending SMS through KudiSMS. Plug it into your existing notification system, configure your sender ID and credentials, then deliver transactional or alert messages to Nigerian phone numbers using Laravel's familiar notification API.
KUDI SMS Notifications Driver for Laravel.
Frequently asked questions about Kudisms Notification
- How do I install toneflix/kudisms-notification?
- Install it with Composer using composer require toneflix/kudisms-notification:^2.0. Then publish the package configuration and set your KudiSMS API credentials and sender ID. The package requires Laravel 12/13 and PHP 8.3/8.4, so confirm your runtime first. After publishing, clear config caches before using the channel in a notification.
- What Laravel and PHP versions does toneflix/kudisms-notification support?
- Version 2.0.0 supports PHP 8.3 and 8.4 and Illuminate/Laravel 12 and 13. It is not installable on Laravel 11 or earlier or PHP 8.2 or earlier. Applications on older runtimes must upgrade the platform or stay on the 1.x package with its old vendor name. Confirm CI and production images match these constraints.
- How do I configure KudiSMS API credentials and sender ID?
- Publish the package config file and add your KudiSMS API credentials and sender ID to the relevant environment or config values. The channel uses that configuration when sending SMS through Laravel notifications. If you customized a previously published config, update it during migration so it does not reference the old namespace or vendor path. Clear config and application caches after changes.
- How do I send an SMS with KudiSMS in a Laravel notification?
- Add the KudiSMS channel to your notification's via() method and define the message content in a toKudiSms() method. Create or trigger the notification for a recipient phone number as you would any Laravel notification. The package handles delivery through KudiSMS using your configured credentials and sender ID. Test with a staging recipient before enabling it in production.
- Does toneflix/kudisms-notification support queued notifications?
- It is a standard Laravel notification channel, so it can be used from notifications that implement ShouldQueue or are queued by Laravel. The package overview describes clean integration with queues, but it does not document a separate queue driver or retry mechanism. Use Laravel's queue retries, backoff, and failed-job handling around the notification. Verify actual sends and failure behavior in staging.
- How do I migrate from toneflix-code/kudisms-notification to toneflix/kudisms-notification?
- Treat 2.0.0 as a breaking dependency migration: remove toneflix-code/kudisms-notification, require toneflix/kudisms-notification:^2.0, and replace imports from ToneflixCode\KudiSmsNotification with Toneflix\KudiSmsNotification. Re-publish or manually update the KudiSMS config so it no longer references the old vendor or namespace. Clear config and application caches, run the test suite, and do a staging SMS send. Do not install both package names at the same time because autoloading and config merging can conflict.
- Can I use toneflix/kudisms-notification on Laravel 11 or PHP 8.2?
- No, version 2.0.0 requires Laravel 12/13 and PHP 8.3/8.4. On Laravel 11 or PHP 8.2, Composer will not resolve 2.0.0 unless you upgrade the platform. You can remain on the 1.x package with the old vendor and namespace while planning an upgrade. Alternatively, defer adoption or sequence the package migration after the Laravel/PHP upgrade.
- How do I test KudiSMS notifications without sending real SMS?
- Use Laravel's Notification::fake() to assert that the notification was sent via the KudiSMS channel without calling the provider. For integration testing, mock the HTTP calls the channel makes or use test credentials and a staging phone number. Avoid production API credentials in automated tests. Also test queued and failed notification paths if you rely on queues.
- Does the KudiSMS channel support delivery receipts, retries, or rate limiting?
- The package is scoped as a Laravel notification channel; the provided overview does not document built-in delivery receipts, rate limiting, or retry logic. Use Laravel queues for retries and backoff, and add your own throttling or rate limiter where needed. For delivery receipts, confirm the available KudiSMS API features and vendor documentation. Validate these behaviors in staging before relying on them in production.
- Is toneflix/kudisms-notification maintained, and what alternatives exist?
- Version 2.0.0 is a vendor and namespace relocation release, so check the repository for recent commits, releases, and security advisories before adopting it. Alternatives include other Laravel SMS notification channels or calling the KudiSMS API directly; the overview does not name specific competing packages. If you are already on Laravel 12/13 and PHP 8.3/8.4, the package is narrowly scoped and straightforward to evaluate. Consider your maintenance and vendor-allowlist requirements during the migration.
Weaver
How can I help you explore Laravel packages today?