Weave Code
Smsapi Laravel Package
laravel-notification-channels/smsapi
A Laravel notification channel for SMSAPI that lets your application send SMS notifications through the SMSAPI gateway using Laravel’s familiar notification API. Simple to install, configure, and integrate into existing apps.
Smsapi Notifications Channel for Laravel
Frequently asked questions about Smsapi
- How do I install laravel-notification-channels/smsapi in a Laravel app?
- Install it with Composer using composer require laravel-notification-channels/smsapi. Then publish the package config so you can set your SMSAPI token and default sender name, and add the credentials to your .env file. Laravel's package auto-discovery should register the service provider, so no manual wiring is normally needed. After that you only need to add the channel to a notification's via() method and implement toSmsapi().
- Which Laravel and PHP versions does this SMSAPI notification channel support?
- The README does not spell out a support matrix, so check the illuminate/support constraint in the package's composer.json before committing. Notification channel packages are sensitive to Laravel major version changes such as via() signature updates and PHP version bumps. The release dated 2026-04-07 suggests recent activity, but confirm the tagged version matches your target Laravel release. If it only supports the previous major, treat that as a scheduling risk rather than assuming it will work.
- How do I send an SMS with a Laravel notification using SMSAPI?
- Return the package's channel class from your notification's via() method and add a toSmsapi($notifiable) method that returns an SmsapiMessage with the text and recipient. Laravel's native notification dispatcher then hands the message to the channel, which calls the SMSAPI gateway. You can fan out to mail, database, and SMS in the same notification without extra plumbing. The package is a thin adapter, so the usual notification routing and on-demand notifications apply.
- What credentials and configuration does the SMSAPI channel need?
- You need an SMSAPI API token and a default sender name, both supplied through the published config and your environment variables. The config also exposes an optional test-mode flag in most versions, which is worth verifying in the source. Credentials belong in .env, never in committed config. Sender names must satisfy SMSAPI's registration rules, which are weighted toward Poland and the EU.
- Should I send SMSAPI notifications through a queue in Laravel?
- Yes. SMS delivery is blocking I/O against an external API and should never sit in a request path, so implement ShouldQueue on the notification. Queueing also gives you retries and failed-job visibility, which matters because each retry hits a paid API. Be aware that provider exceptions typically surface as failed jobs, so configure retry limits and backoff deliberately. Monitor failed jobs for invalid numbers or insufficient funds rather than letting them retry blindly.
- Does this package throw exceptions when the SMSAPI API call fails?
- Notification channels generally let provider exceptions propagate into the queue worker, and this package follows that shape, but the README does not document the exact exception class. Inspect the channel source to see whether non-2xx responses are surfaced or swallowed and whether the raw response body is preserved for logging. Per-message errors such as an invalid number, blocked sender, or insufficient funds may arrive as provider-level errors rather than transport failures. Wrap sends in try/catch or use failed-job handling if you need custom reconciliation.
- Does this channel support SMSAPI delivery reports, inbound SMS, or MFA?
- No. This package is a delivery adapter only: it supplies a channel class and a message value object for outbound texts. It does not model inbound messages, delivery reports, sender-name registration, or SMSAPI's MFA/2FA product surface. Any workflow needing confirmation of delivery or two-way messaging requires additional integration work against the SMSAPI REST API directly.
- Can I override the sender name per notification or schedule an SMS?
- The config provides a default sender name, and per-notification overrides depend on what the message object exposes; check the SmsapiMessage class before relying on it. Scheduled send and bulk or fast send modes are not documented, so assume you would call the API directly for those. Sender names must be registered and approved at SMSAPI, and validation typically happens at the provider rather than in the package. Test your sender name in the target country before shipping.
- Is there a sandbox or test mode so my test suite does not hit SMSAPI?
- The config includes an optional test-mode flag, but confirm in the source that it short-circuits without network calls before trusting it in CI. If it does not, fake the channel or mock the HTTP client in your tests instead. Never let feature tests send real SMS, because each message is billable and rate-limited. A small contract test around your toSmsapi() payload is usually enough.
- Is laravel-notification-channels/smsapi maintained, and what are the alternatives?
- Adoption signal is thin at roughly 24 stars and no known dependents, but the code surface is small enough to vendor or fork and maintain yourself. Verify the latest tagged release and its Laravel constraint before committing, and budget for upstream unresponsiveness. Alternatives include calling the SMSAPI REST API through Laravel's HTTP client directly, or using a notification channel for a provider with a stronger regional fit. If your users are outside Poland and the EU, the integration cost is low but the business case may be weak.
Weaver
How can I help you explore Laravel packages today?