Weave Code
Jet Sms Laravel Package
laravel-notification-channels/jet-sms
Jet SMS notification channel for Laravel. Send SMS messages through the Jet SMS API using Laravel’s notification system, with a simple channel integration for direct or queued notifications.
Sends SMS using JetSms API
Frequently asked questions about Jet Sms
- How do I install laravel-notification-channels/jet-sms?
- Install it with Composer using composer require laravel-notification-channels/jet-sms. The package uses Laravel package auto-discovery, so the JetSms service provider and channel register without manual edits on supported versions. Be aware that its 2020 Composer constraints target Laravel 5.5 through 7 and PHP 7.x, so installation on a modern stack may fail until you adjust constraints. After install, check config/jet-sms.php for the credentials and sender settings.
- Does this package support Laravel 10 or 11?
- No. The package's 2020-era composer.json targets Laravel 5.5 to 7 and PHP 7.x, so it is not natively compatible with Laravel 10 or 11 or PHP 8.2+. You can sometimes install it by forking and bumping constraints, but expect deprecation fixes and possibly HTTP client changes. Treat official support as legacy-only until new tags are published.
- How do I send an SMS with a Laravel notification using JetSMS?
- Add a toJetSms() method to your notification class and include JetSmsChannel in the notification's via() array. The method returns the SMS payload that the channel sends through the JetSMS API. Then send the notification normally with Notification::send() or the notifiable's notify() method. The package is additive if your application already uses Laravel Notifications.
- How do I configure JetSMS credentials?
- Credentials are read from the package's config/jet-sms.php file, typically including the JetSMS username, password or API key, and sender information. Confirm the exact keys against the installed package source because the vendor authentication scheme may have changed since the last 2020 release. Keep secrets in environment variables and never commit the config values.
- Does the JetSMS channel support queued notifications?
- Queued notifications should work through Laravel's standard queue integration because the channel is invoked as part of notification delivery. However, the channel implementation may call Guzzle synchronously inside the request cycle, so verify with a queued notification and a real test send. If synchronous behavior is a concern, wrap SMS sending in a job or fork the channel to use Laravel's HTTP client with timeouts.
- Can I test JetSMS notifications with Notification::fake() and Http::fake()?
- There is no documented test suite in the evaluation, and 2020-era channels often call Guzzle directly rather than Laravel's Http client. That means Http::fake() may not intercept requests unless you refactor the channel to use Http. Notification::fake() can still assert that the notification was sent, but it will not validate the actual JetSMS HTTP payload. For reliable tests, fork the channel and add PHPUnit coverage with Http::fake().
- Is this package maintained and safe for production?
- Treat it as unmaintained: the last release was 2020-03-07, with 9 stars and no dependents noted. It is MIT licensed and small, but you own any security, compatibility, and bug fixes. For production on modern Laravel, fork and modernize it or reimplement the channel behind your own interface.
- What are the alternatives if I need SMS in Laravel on PHP 8.2?
- If you are on Laravel 10 or 11 with PHP 8.2+, the realistic options are fork-and-modernize or reimplement in-house. A fork is roughly 2 to 5 days to bump constraints, replace Guzzle with Http, and add tests. An in-house abstraction is about 150 lines and 2 to 3 days, and makes swapping Turkish or global SMS providers easier. Installing as-is only works on a matching legacy Laravel 5.5 to 7 stack.
- Does it support delivery receipts, webhooks, or templated and Unicode SMS?
- Delivery receipts, webhooks, and templated or Unicode messaging are likely out of scope for this single-purpose channel. The package overview only describes sending SMS through the JetSMS API via Laravel notifications. If you need delivery confirmation or silent-failure detection, plan to build that around the vendor's API or choose a provider with those features. Confirm vendor capabilities before assuming the package exposes them.
- How do I route notifications to a phone number with routeNotificationForJetSms()?
- Add a routeNotificationForJetSms() method on your notifiable model that returns the destination phone number. Laravel calls this hook when the JetSmsChannel is in the notification's via() array. This keeps phone routing explicit and lets you store numbers per user or per model. Verify the expected return format, such as E.164, against the package source and JetSMS requirements.
Weaver
How can I help you explore Laravel packages today?