Weave Code
Sms.to Laravel Lumen Laravel Package
intergo/sms.to-laravel-lumen
A lightweight Laravel and Lumen integration for the sms.to SMS gateway. It provides a service provider and configuration for sending text messages from your application, keeping API credentials and settings in Laravel's config instead of hard-coded values.
Laravel and Lumen package for sending SMS via SMS.to REST API
Frequently asked questions about Sms.to Laravel Lumen
- How do I install intergo/sms.to-laravel-lumen?
- Install it with Composer using composer require intergo/sms.to-laravel-lumen, then publish the package config so your credentials live in Laravel's config layer rather than in code. In full Laravel the service provider is auto-discovered; in Lumen you register the provider and config file manually in bootstrap/app.php. Because the repository does not advertise a release cadence, pin an exact version such as 1.2.0 instead of a floating caret constraint.
- Which Laravel versions does this package support?
- Release 1.2.0 is the version that added Laravel 10 support, and the changelog describes it as a single compatibility change over 1.1.0 with no API or behavioral differences. There is no published support for Laravel 11 or 12, so treat Laravel 10 as the current ceiling until you check the illuminate/* constraints in the package's composer.json yourself. If your roadmap includes newer Laravel releases, plan for either a fork or a replacement.
- How do I configure the SMS.to API key and sender ID?
- Publish the package config file and supply your SMS_TO_API_KEY plus your sender or originator ID through environment variables. Keep those values out of version control, confirm they are redacted in logs, and verify the config still resolves correctly when you run php artisan config:cache in production. Hard-coding credentials in a service or controller defeats the main benefit of the package.
- How do I send an SMS from a Laravel notification?
- Add the SMS.to channel to the via() array on an existing Notification class, define the routing method the package expects on your notifiable model so it returns an E.164 phone number, and return the message content from the notification. This keeps SMS logic inside Laravel's notification pipeline rather than in controllers, and it sits alongside mail and database channels without conflict. Check the package source for the exact method names in your installed version before wiring it up.
- Does this package work with Lumen?
- The package is branded laravel-lumen, so Lumen support is intended, but Lumen has no package auto-discovery, which means you must register the service provider and load the config manually in bootstrap/app.php. Confirm which service providers actually ship in 1.2.0 and whether Lumen-specific code paths are maintained, since the naming is broader than the documented feature set.
- How are gateway errors and retries handled?
- The documentation does not state whether non-2xx responses from SMS.to throw exceptions or return a boolean or response object that callers must inspect. Thin wrappers frequently swallow gateway errors, so read the source before relying on it and wrap sends in try/catch with logging at minimum. Retry, backoff, timeout, and rate-limit handling should be assumed to be your responsibility unless you can verify otherwise.
- Can I queue SMS notifications?
- Because the package plugs into Laravel's notification system as a channel, implementing ShouldQueue on the notification queues the SMS the same way it queues mail. That gives you asynchronous delivery and Laravel's standard queue retry behaviour for the job itself. What the package does with a failed gateway call after the job runs is a separate question and is not documented.
- How do I test SMS sending without calling the real SMS.to API?
- The repository does not advertise a test suite or CI, so assume you need to write your own coverage. If the package uses Laravel's HTTP client you can fake it with Http::fake(), but if it uses raw Guzzle or cURL you will need to bind a mock in the container instead. Defining your own SmsSender interface and implementing it with this package makes that swap trivial and is the single most valuable testing decision you can make.
- Is intergo/sms.to-laravel-lumen still maintained?
- It is a small third-party package backed by a single commercial SMS API with what appears to be one maintainer and infrequent releases, and the Laravel 10 bump arrived after Laravel 10 shipped. That pattern suggests reactive rather than proactive maintenance, so expect similar lag for future Laravel versions. Pin an exact version, watch the repository for a stated support window, and keep a migration path open.
- What are alternatives if I need more than this package offers?
- Because the package is a thin wrapper, you can call the SMS.to REST API directly with Laravel's HTTP client and get testability, retries, and typed exceptions on your own terms. Provider-agnostic notification channel packages or your own SmsSender abstraction are better fits if you need failover across gateways, delivery receipts, or inbound webhook handling. Whichever you choose, keep the vendor behind an interface so switching later is a one-file change.
Weaver
How can I help you explore Laravel packages today?