Weave Code
Sinch Notifier Laravel Package
symfony/sinch-notifier
Symfony Notifier integration for Sinch. Send SMS via Sinch using a simple DSN like sinch://SERVICE_PLAN_ID:AUTH_TOKEN@default?from=FROM, where FROM is your sender. Configure with your service plan ID and auth token.
Symfony Sinch Notifier Bridge
Frequently asked questions about Sinch Notifier
- Can I use this package directly in Laravel without Symfony’s Notifier?
- No, this package is Symfony-first and requires wrapping Symfony’s Notifier and DI container in Laravel. You’d need to create a Service Provider to bridge the gap, which adds complexity. For a native Laravel solution, consider laravel-notification-channels/sinch instead.
- What Laravel versions does this package support?
- Indirectly, it depends on Symfony’s requirements. Symfony 8+ needs PHP 8.4+, which may conflict with Laravel’s supported PHP versions (8.0–8.2). Test thoroughly if using newer Symfony versions with Laravel.
- How do I configure Sinch in Laravel using this package?
- Set the DSN in your `.env` as `SINCH_DSN=sinch://SERVICE_PLAN_ID:AUTH_TOKEN@default?from=FROM`. Then, register the Symfony Notifier and Sinch transport in a Laravel Service Provider, binding them to Laravel’s container manually.
- Does this package support Laravel’s queue system for SMS delivery?
- No, it relies on Symfony’s Notifier for delivery. To use Laravel Queues, you’d need to extend the package or create a custom adapter that dispatches Sinch calls as Laravel queue jobs.
- Are there Laravel-specific examples or tests for this package?
- No, the package is Symfony-focused with no Laravel integration tests. You’ll need to write your own tests for the adapter layer or rely on community contributions.
- Can I use this for Sinch voice calls, not just SMS?
- Yes, if Sinch’s API supports voice calls via the same DSN. However, Laravel’s Notifications may already cover SMS, so evaluate whether voice features justify the Symfony integration overhead.
- What’s the performance impact of using Symfony Notifier in Laravel?
- Moderate to high due to DI container and event system mismatches. Benchmark against raw Sinch API calls or Laravel HTTP clients (e.g., Guzzle) to compare latency and resource usage.
- Are there alternatives for Sinch in Laravel without Symfony?
- Yes, consider `laravel-notification-channels/sinch`, which is Laravel-native and integrates directly with Laravel’s Notification system. It’s simpler for SMS-only use cases.
- How do I handle Sinch webhooks in Laravel with this package?
- Webhooks aren’t natively supported. You’d need to create a Laravel route and manually validate Sinch’s signature, then dispatch Laravel events or update models accordingly.
- What maintenance effort is required for this integration?
- High. You’ll need to maintain custom adapters for Symfony-Laravel compatibility, handle version conflicts (e.g., PHP/Symfony), and stay updated on Sinch API changes. Assign a maintainer for long-term stability.
Weaver
How can I help you explore Laravel packages today?