- What is gr8shivam/laravel-sms-api used for?
- It is a Laravel package that provides a unified interface for sending SMS through multiple gateways. Instead of wiring each provider's HTTP API into your application separately, you configure providers and send messages through one consistent API. It fits common use cases such as OTP delivery, alerts, and transactional notifications.
- How do I install gr8shivam/laravel-sms-api in a Laravel app?
- Install it with Composer using composer require gr8shivam/laravel-sms-api. Laravel package auto-discovery should register the service provider, but confirm in the README whether manual registration is required for your version. After that, publish the config file if the package ships one so you can set your default gateway and credentials.
- Which SMS gateways or providers does this Laravel SMS package support?
- The package is built as a multi-gateway abstraction, so the available drivers depend on what it ships and what you add yourself. Check the README and the published config file for the current provider list before committing to it. If your provider is not included, you can usually implement it behind the package's gateway contract.
- How do I switch SMS gateways at runtime in Laravel?
- Gateway selection is config-driven, so you can set the default in the published config file or override it per environment. That lets you use one provider in staging and another in production without changing application code. For per-message switching, check whether the package exposes a driver or gateway setter on its facade or client.
- Which Laravel and PHP versions does laravel-sms-api support?
- The 4.1.0 release added Laravel 13 compatibility, which is a positive maintenance signal. The full supported range and the PHP floor live in the package's composer.json, so read that file rather than relying only on the changelog. Confirm it still covers the Laravel and PHP versions you run before upgrading.
- How do I send an SMS or OTP with this package?
- Typical usage is a single call through the package's facade or an injected client, passing the recipient number and message body. OTPs are usually just a generated code sent as the message text, with your own expiry and verification logic kept in your application. Check the README for the exact method signatures in the version you install.
- Where do I put SMS gateway credentials and publish the config file?
- Credentials normally go into the package config file after running vendor:publish, and those values should be read from environment variables so secrets stay out of version control. Keep per-gateway credentials separate so switching providers is a config change rather than a code change. Remember to re-run config:cache after editing values in production.
- Can I send SMS through Laravel queues with this package?
- SMS sending is a network call, so wrapping it in a queued job is good practice for anything beyond low volume. Whether the package ships queue support itself or expects you to dispatch your own job depends on its API, so verify in the docs. Either way, add retries and idempotency on your side to avoid duplicate messages.
- How do I test SMS sending without hitting a real gateway?
- Keep gateway calls out of your test suite by faking the package client or binding a fake gateway implementation in the container. That lets your tests assert the correct recipient and message body were passed without making real HTTP requests. For integration tests, point the config at a provider sandbox instead of production credentials.
- Is gr8shivam/laravel-sms-api actively maintained, and what are the alternatives?
- Laravel 13 support landing in 4.1.0 suggests the package is still maintained, but check the repository for release cadence, open issues, and whether it is a single-maintainer project. If you only ever use one provider, calling that provider's SDK directly may be simpler; if you need to swap gateways, this abstraction earns its place. Review the license and issue activity before adopting it in production.