- How do I install kkedzierski/sms-api-manager-bundle?
- Install it with Composer using composer require kkedzierski/sms-api-manager-bundle, then enable the bundle in your Symfony application and add its configuration. It is a Symfony bundle, not a Laravel package, so normal Laravel package discovery does not apply. Follow the repository README for the exact bundle registration class and config file name.
- Is this package compatible with Laravel?
- No, it is built as a Symfony bundle and integrates through Symfony's service container and YAML configuration. Laravel uses service providers and its own config system, so you would need to instantiate the underlying SMSAPI client manually or write a small Laravel wrapper. If you need a drop-in Laravel SMS package, evaluate one that ships a Laravel service provider instead.
- How do I configure SMSAPI credentials in Symfony?
- Configure the bundle in YAML with your SMSAPI credentials and default sending options, then let Symfony autowire the SMS service. Keep secrets in environment variables rather than committing them to config files. The exact config keys are defined by the bundle and should be checked against the repository README.
- How do I send an SMS from a Symfony controller or command?
- Inject the autowired SMS service into your controller or command handler and call the sending methods exposed by the underlying SMS API Manager library. Because the service is managed by the container, you do not need to manually construct the client or pass credentials. Keep domain code behind a small internal interface if you want to avoid tight coupling.
- Does the bundle support bulk SMS sending?
- Yes, the package description lists support for both single and bulk message sending. Bulk sending is handled through the underlying SMSAPI client methods, so check that library's documentation for payload limits and batching behavior. Test bulk paths in staging before using them for production campaigns.
- How can I check SMS delivery status or reports?
- The bundle supports delivery status and report lookups through the same configured SMS service. Inject the service and call the report or status methods provided by the underlying SMS API Manager library. Confirm the exact method names and response format in the library documentation, since the bundle focuses on container integration.
- How do I test SMS sending without calling the real API?
- Replace the autowired SMS service with a test double in the Symfony test container, or mock the Symfony HTTP client used by the underlying library. That lets you assert that your code triggers the expected send or report call without spending credits. There are no Laravel facades or fakes here because this is a Symfony bundle.
- What Laravel and PHP versions does this package support?
- Laravel version support does not apply directly because this is a Symfony bundle, not a Laravel package. Check the package's composer.json for its PHP and Symfony framework constraints before adopting it. If you plan to use it from Laravel, you own the compatibility work for both Laravel and Symfony components.
- What are the production risks of adopting this bundle?
- The main risks are maintenance continuity, version coupling to Symfony releases, and abstraction leakage if you call package classes directly from domain code. Review commit cadence, release history, and license terms before committing it to a roadmap. Wrap it behind an internal adapter so a future replacement is a single-file change rather than a rewrite.
- Can I remove the bundle later or use multiple SMS providers?
- Yes, removal is straightforward if you isolate it behind your own interface and do not let domain code depend on its classes or config keys. For multiple providers, define a common internal SMS interface and bind this bundle's service as one implementation. That keeps provider-specific credentials and transport details out of your application logic.