Weave Code
Sendinblue Notifier Laravel Package
symfony/sendinblue-notifier
Symfony Notifier transport for Sendinblue SMS. Configure via DSN (sendinblue://API_KEY@default?sender=PHONE) to send transactional texts using your Sendinblue API key and sender number. Links to Symfony docs, issues, and PRs.
Symfony Sendinblue Notifier Bridge
Frequently asked questions about Sendinblue Notifier
- Can I use symfony/sendinblue-notifier directly in a Laravel app without extra setup?
- No, this package is designed for Symfony’s Notifier component and requires custom integration for Laravel. You’d need to wrap it in a Laravel service, use a queue worker, or call it via HTTP from a microservice. Laravel’s native `spatie/laravel-sendinblue` is more idiomatic for direct use.
- How do I configure symfony/sendinblue-notifier for Laravel?
- Configure via a DSN in your `.env` like `SENDINBLUE_DSN=sendinblue://YOUR_API_KEY@default?sender=+1234567890`. For Laravel, you’ll need to create a custom notification channel or service that bridges Symfony’s Notifier to Laravel’s notification system, likely using a queue or HTTP client.
- What Laravel versions support symfony/sendinblue-notifier?
- The package itself doesn’t enforce Laravel versions, but it depends on Symfony Notifier (v6.x), which requires PHP 8.1+. Laravel 9+ (PHP 8.1+) is compatible, but you’ll need to handle the integration layer yourself. Test thoroughly, as Symfony’s dependencies may conflict with Laravel’s ecosystem.
- Does symfony/sendinblue-notifier support Sendinblue’s transactional SMS templates?
- No, this package only sends raw SMS via Sendinblue’s Transactional SMS API. For templates or advanced features like webhooks, consider Sendinblue’s official PHP SDK or `spatie/laravel-sendinblue`, which may offer broader functionality for Laravel.
- How do I test symfony/sendinblue-notifier in a Laravel app?
- Mock the Symfony Notifier transport in your tests by overriding the DSN or using a test double for the Sendinblue API. For Laravel-specific testing, verify your custom integration layer (e.g., queue jobs or HTTP calls) behaves as expected. Use Sendinblue’s sandbox environment for API testing.
- What are the performance implications of using this package in Laravel?
- If integrated via a microservice or queue worker, latency may increase due to inter-service calls. Direct use in Laravel isn’t supported, so performance depends on your custom setup. Benchmark your specific architecture, as Symfony’s Notifier adds overhead compared to lightweight Laravel SDKs.
- Are there alternatives to symfony/sendinblue-notifier for Laravel?
- Yes, `spatie/laravel-sendinblue` is a more Laravel-native option with built-in support for notifications, queues, and templates. Sendinblue’s official PHP SDK is another alternative if you need low-level control. Choose based on whether you need Symfony’s Notifier features or prefer Laravel’s ecosystem.
- How do I handle errors or retries with symfony/sendinblue-notifier in Laravel?
- Symfony Notifier includes retry logic for transports, but you’ll need to expose this in your Laravel integration. For queues, use Laravel’s retry mechanisms. For direct HTTP calls, implement retry logic in your service layer. Check Sendinblue’s API rate limits and adjust accordingly.
- Can I use this package for Sendinblue’s marketing campaigns, not just transactional SMS?
- No, this package only supports Sendinblue’s Transactional SMS API. For marketing campaigns (e.g., bulk emails or SMS), use Sendinblue’s dedicated APIs or SDKs. Laravel’s `spatie/laravel-sendinblue` may also cover broader use cases if integrated properly.
- How do I contribute or report issues for symfony/sendinblue-notifier?
- Issues and pull requests are handled in the main Symfony repository (github.com/symfony/symfony). Check the [Symfony contributing guide](https://symfony.com/doc/current/contributing/index.html) for details. For Laravel-specific questions, consider opening an issue in this package’s GitHub repo or the Symfony Notifier repo.
Weaver
How can I help you explore Laravel packages today?