Weave Code
Notification Api Sms Notifier Bundle Laravel Package
fagforbundet/notification-api-sms-notifier-bundle
Symfony bundle for sending SMS notifications through the Notification API. Integrates with Symfony Notifier to dispatch text messages from your application, with configurable API credentials and delivery settings.
Notification API SMS transport for Symfony Notifier
Frequently asked questions about Notification Api Sms Notifier Bundle
- Can I use this Symfony bundle in a Laravel application?
- It is a Symfony bundle, not a Laravel package. It registers an SMS transport for symfony/notifier through a DI extension and a DSN, which Laravel's Illuminate\Notifications channel contract does not understand. To use it in Laravel you would either pull symfony/notifier and symfony/http-client into the app and bootstrap a container for the transport, or wrap the small transport class behind your own sender interface and expose it as a custom notification channel. The second, surgical approach is the recommended one.
- How do I install fagforbundet/notification-api-sms-notifier-bundle with Composer?
- Run composer require fagforbundet/notification-api-sms-notifier-bundle. In a Symfony app the bundle's DI extension registers the transport factory and services automatically once the bundle is enabled. In a Laravel app there is no bundle registration, so installation alone does nothing until you wire the transport yourself. Run composer require --dry-run against your real skeleton first to check version resolution.
- Does it work with Laravel 10, Laravel 11, and Symfony 7?
- There is no Laravel support in the package itself; it targets Symfony's Notifier component and DI container. Laravel 10 and 11 already ship Symfony components internally, so adding symfony/notifier and symfony/http-client can force pins or cause version-resolution conflicts. Symfony 7 support and the exact PHP and Symfony constraints in composer.json are unconfirmed in the assessment, so verify them before committing to the full-fidelity path.
- How do I configure the Notification API credentials and sender for the SMS transport?
- In Symfony you configure the transport through a DSN and the bundle's configuration keys, which the DI extension reads. In Laravel you would replicate that as a config block and bind the transport with a service provider. The configuration contract is effectively undocumented, so confirm the exact key names and DSN format with the vendor.
- How do I send an SMS from a Laravel notification channel?
- Build a custom channel class that implements Laravel's notification channel contract and delegates to a small sender adapter. The adapter wraps the bundle's transport send method, or a forked copy of it, so your application code never depends on Symfony Notifier types. Register the channel and sender in a service provider, then reference the channel in your notification's via method.
- Does the transport handle retries, timeouts, idempotency, and delivery receipts?
- The reusable surface is essentially one transport class with a send method and a request and response mapping. The evaluation notes no obvious story for retries, idempotency keys, rate limits, or delivery receipts. If you need those behaviors, implement them in your own adapter layer rather than expecting the transport to provide them.
- Are there tests in the package, and can I reuse them as a contract test?
- The assessment found no visible signal on tests, release cadence, or a security policy. If the repository does contain tests, check whether they mock the HTTP client in a way you can reuse as a contract test for your own adapter. Otherwise write your own contract tests against the vendor API before relying on the transport.
- Is this package actively maintained and safe for production?
- Project health is the dominant risk: zero stars, zero dependents, single-organization authorship, and no visible external consumers. Bus factor is effectively one team, and that team may not share your priorities. Treat it as a reference implementation rather than a dependency you can lean on in production.
- What license is the package under, and can I fork or vendor it?
- It is MIT licensed, so forking and vendoring are legally unencumbered. That is the main reason the package stays viable as a reference implementation despite its project-health concerns. Fork the one or two classes you actually need behind your own interface to decouple from the upstream lifecycle.
- What are the alternatives for sending SMS notifications in Laravel?
- If you are already contracted with Fagforbundet's Notification API, a thin Laravel HTTP client wrapper is simpler than adopting Symfony Notifier. If you are not, evaluate the vendor first, because that may invalidate the package question entirely. Otherwise, Laravel-native SMS channels for providers such as Twilio or Vonage avoid the framework-boundary friction.
Weaver
How can I help you explore Laravel packages today?