Weave Code
Turbosms Laravel Package
laravel-notification-channels/turbosms
A Laravel notification channel for sending SMS messages through TurboSMS. Integrate TurboSMS with Laravel notifications and deliver SMS using a simple, familiar channel API.
Turbosms notification channel for Laravel
Frequently asked questions about Turbosms
- How do I install and configure the TurboSMS notification channel in Laravel？
- Install with composer require laravel-notification-channels/turbosms, then publish the package config file and set your TurboSMS credentials in .env. The service provider is auto-discovered, so no manual registration is required. Add the channel to a notification's via() array and implement toTurboSms() to start sending.
- Which Laravel and PHP versions does laravel-notification-channels/turbosms support？
- Version 1.1.1 adds Laravel 11 and Laravel 12 support through community pull requests, while Laravel 9 and 10 are presumed supported from the 1.1.0 line, so verify the constraints in composer.json before relying on them. The tested PHP range is not clearly documented, and Laravel 12 generally implies PHP 8.2+, so confirm in composer.json or CI. Expect Laravel 13 support to lag by months rather than arrive on release day.
- How do I send an SMS from a Laravel notification using the TurboSmsChannel？
- Add TurboSmsChannel::class to the notification's via() array and implement a toTurboSms() method that returns a TurboSmsMessage value object with the recipient and message content. Laravel then routes the notification through the channel's send() method, which translates it into a TurboSMS HTTP request. This is the same mental model you already use for mail, push, or Slack channels.
- Does the TurboSMS channel work with queued notifications (ShouldQueue)？
- Yes. The channel is a thin translation layer between Laravel's Notification dispatch and the TurboSMS HTTP API, so it composes with ShouldQueue like any other channel. SMS should be queued rather than sent inline in a request cycle, so implement ShouldQueue on the notification and let a queue worker handle delivery.
- How are TurboSMS API errors handled, and does it retry on 429 rate limits？
- There is no documented handling of TurboSMS provider error codes, and version 1.1.1 is a dependency-constraint update only, so the error surface is unchanged. Whether error codes become Laravel-retryable exceptions and whether 429/backoff is respected is unconfirmed. Treat it as unknown, wrap sends in your own handling, and verify behavior in staging.
- Which TurboSMS API version does the package target, and does it support Viber？
- The target TurboSMS API version, v1 versus v2 endpoints, and whether the package covers SMS only or also Viber are not documented. Inspect the channel source to confirm endpoint URLs and payload shape before committing. If you specifically need Viber or a particular API version, validate it first.
- Can I set per-message sender IDs or schedule SMS sends with TurboSmsMessage？
- Per-message sender IDs, alpha-numeric sender registration workflows, and scheduled sends are not confirmed features and remain open questions. Check the TurboSmsMessage value object and the channel's send() implementation to see which fields are actually supported. If you need scheduling, a common fallback is to delay the queued notification instead.
- Does the package support TurboSMS delivery status callbacks or webhooks？
- Delivery-status callbacks and webhooks are not documented, and the channel appears to be fire-and-forget. If you need delivery receipts, plan to build your own webhook endpoint on the TurboSMS side and correlate incoming statuses with your own message IDs. Do not assume the package tracks delivery status for you.
- How does the channel handle long or Cyrillic SMS segmentation and encoding？
- Long and Cyrillic message segmentation is not addressed by the package, so the responsibility appears to sit with the caller. Segment long messages yourself or confirm TurboSMS handles it, and test Cyrillic encoding in staging. Part counts and costs depend on correct segmentation, so validate before scaling volume.
- Is the package actively maintained, tested in CI, and safe for production use？
- The package is maintained: 1.1.1 tracks Laravel 11 and 12, with two external contributors merged alongside the maintainer, which is evidence against abandonment. However, it still has about 5 stars and near-zero dependents, there is no stated SLA or succession plan, and a CI version matrix or mocked HTTP client is not confirmed. Treat it as viable for a thin integration after a discovery spike, pin exact versions, and keep a direct Http facade call as a fallback alternative.
Weaver
How can I help you explore Laravel packages today?