Weave Code
Simple Sms Laravel Package
simplesoftwareio/simple-sms
Simple SMS is a Laravel package for sending text messages through multiple SMS gateways. It offers a clean, driver-based API, configurable providers, and straightforward integration for notifications, alerts, and verification codes.
Send and receive SMS messages with Laravel
Frequently asked questions about Simple Sms
- How do I install simplesoftwareio/simple-sms in a Laravel app?
- Install it with Composer, pinning a constraint such as ^3.1.1 rather than a floating version so future patches are deliberate. On Laravel 5.5 and later the service provider is normally registered through package auto-discovery, while older releases may need the provider and facade added to config/app.php manually. After installing, publish the package config so you can set your default driver and gateway credentials. Review the lock file diff after updating so data-only patch releases do not arrive in production unannounced.
- Which Laravel and PHP versions does simple-sms support?
- The 3.1.1 release notes include a Laravel 5.4 compatibility fix, which suggests the package is aimed at the Laravel 5.4 through 5.x/6.x era. The available release evidence does not confirm support for Laravel 9, 10, 11, or 12, so treat modern framework compatibility as unverified. Check the require block in the tagged composer.json and run a short spike on your target Laravel version before committing to it.
- Which SMS gateways does simple-sms support?
- Simple SMS uses a driver-based design where each gateway is a driver selected through the package configuration, so the available providers depend on the drivers bundled in the installed version. You set a default driver and supply that provider's credentials in the config file. For a gateway that is not included, you would need to implement a driver against the package's driver contract, or wrap the provider's own SDK in your application code.
- How do I configure the default SMS driver and credentials in simple-sms?
- Publish the package config file, set the default driver, and fill in the credential block for that gateway. Keep secrets out of version control by reading them from environment variables inside the config file. Because Laravel caches configuration in production, re-run php artisan config:cache after changing the driver or credentials.
- How do I send an SMS message from Laravel using simple-sms?
- Resolve the package's facade or inject its service into a class, then pass the recipient number and message body, leaving the configured driver to handle delivery. Typical uses are alerts, notifications, and verification codes inside a controller, job, or dedicated notifier class. Wrap sends in your own error handling or push them onto a queue so a slow gateway does not block the request path.
- Can simple-sms receive inbound SMS messages?
- The package overview describes both sending and receiving SMS, but inbound messages normally arrive as a webhook callback from your gateway rather than through polling. You would expose a route, verify the provider's request signature, and hand the verified payload to the package. Check the source for your specific driver, since the release notes do not document the inbound API surface.
- Does simple-sms support Laravel package auto-discovery?
- The 3.1.1 patch includes a Laravel 5.4 compatibility fix, and 5.4 is the release that introduced package auto-discovery, so the change most likely concerns service provider registration or config publishing. On Laravel 5.5 and later, discovery should register the provider automatically. On older releases, or if discovery is disabled, add the provider and alias to config/app.php yourself.
- How do I test SMS sending in Laravel without hitting a real gateway?
- Because gateways are resolved as drivers from configuration, the cleanest approach is to bind a fake driver or mock the driver contract in the test container so no HTTP calls leave your suite. Assert on the recipient and message body passed to the driver rather than on real delivery. Avoid asserting on any bundled reference data values, since those can change in patch releases.
- Are there breaking changes in simple-sms 3.1.1 and is it safe to upgrade?
- 3.1.1 is a patch release containing a Laravel 5.4 compatibility fix and an added carrier in the lookup dataset, with no breaking changes signalled by the version bump. Pin ^3.1.1 instead of a floating constraint so future data-only patches are intentional. Upgrade in a branch with composer update simplesoftwareio/simple-sms --with-dependencies and inspect the lock diff for transitive changes before merging.
- Is simple-sms actively maintained, and what are the alternatives?
- The evidence available covers a 3.1.x line shipping slowly, with no CI status, test coverage, or issue tracker data supplied, so maintenance activity cannot be confirmed from the release notes alone. For Laravel 9 and later, verify compatibility with an explicit spike first, because a framework upgrade would likely force a package swap or a maintained fork. Alternatives include gateway-specific official SDKs wrapped in your own service class, or Laravel notification channels hidden behind a small internal SMS abstraction.
Weaver
How can I help you explore Laravel packages today?