Weave Code
Sipgate Laravel Package
laravel-notification-channels/sipgate
A Laravel notification channel for sending SMS messages through sipgate.io. Integrate sipgate into your app’s notification flow and deliver text messages using Laravel’s familiar notification system, with simple configuration for credentials and recipient phone numbers.
Laravel notifications driver for sipgate.de
Frequently asked questions about Sipgate
- How do I install the sipgate notification channel for Laravel?
- Install it with Composer using composer require laravel-notification-channels/sipgate. Laravel's package discovery registers the service provider automatically, so no manual registration is needed on supported versions. After installing, publish or create the package configuration and supply your sipgate.io credentials and sender number. Pin the version you have validated, such as 1.4.0, before using it in production.
- Which Laravel versions does laravel-notification-channels/sipgate support?
- Release 1.4.0 adds Laravel 8.x and 9.x support on top of the previous 5.5, 6.x and 7.x range, so the stated envelope is Laravel 5.5 through 9.x. Laravel 10, 11 and 12 are not claimed by the package. Because Laravel 9 requires PHP 8.0 or newer, the release implicitly signals PHP 8 compatibility around the 8.0 and 8.1 era. Always confirm the actual composer.json constraints against your own framework and PHP matrix.
- Does this package work with Laravel 10 or PHP 8.2?
- No, Laravel 10 and newer support is not claimed; the latest release targets Laravel 5.5 through 9.x. There is also no stated PHP upper bound, so resolution on PHP 8.2 or 8.3 is unverified. For Laravel 10+ applications, treat the package as a reference implementation and build a first-party notification channel backed by a maintained HTTP client for the current sipgate API. Reassess if upstream ships another compatibility release.
- How do I configure sipgate.io credentials for this channel?
- You provide your sipgate.io API credentials and the sender number messages should come from through the package configuration, keeping the values in environment variables rather than in version control. Confirm the sipgate account is provisioned and, if available, test against a sandbox before pointing notifications at real recipients. If you send through queues, make sure the configuration is available to your queue workers as well.
- How do I send an SMS with this channel in a Laravel notification?
- Create a notification class as usual, add the sipgate channel to its via method, and return an SMS message from the matching message-building method. The channel performs the API call to sipgate.io, so you keep using Laravel's notification flow, queueing and on-demand notifications. The recipient number is normally taken from the message or from the notifiable model's routing method. Check the package source for the exact message class and method names on your installed version.
- Can sipgate SMS notifications be queued in Laravel?
- Yes, a notification using this channel can implement ShouldQueue like any other Laravel notification. Queueing is advisable for SMS because API latency and rate limits should not block a web request. Add retries and logging around the job, and confirm credentials and configuration are available in the worker environment. The package does not add idempotency itself, so guard against duplicate sends in your own code.
- Is laravel-notification-channels/sipgate safe to use in production?
- Adoption is very low, with around three stars and no dependents, and there is no formal security or maintenance commitment from the channel organisation. Release 1.4.0 shows renewed activity but is mainly a Laravel constraint and StyleCI formatting change rather than a feature or test-coverage release. For Laravel 8 or 9 applications already committed to Sipgate it is workable with version pinning, monitoring and a fallback provider. For Laravel 10+ or current PHP versions, plan to own a fork or a first-party channel instead.
- How do I route an SMS to a phone number stored on my User model?
- Implement the channel's routeNotificationFor method on the notifiable model and return the phone number, and Laravel will use it when sending. This keeps numbers out of the notification class and lets them change per user. Normalise and validate the format before sending, since the Sipgate API expects a valid recipient number. Fall back to a default or skip the notification when no number is available.
- Does the package support delivery receipts, inbound SMS or webhooks?
- The channel is scoped to sending SMS through sipgate.io inside Laravel's notification flow. Delivery receipts, inbound messages and webhooks are not part of what is documented here and should be treated as out of scope. If you need them, build against Sipgate's current API directly and keep that logic separate from the notification channel. Check the upstream Sipgate documentation for the endpoints your account and product expose.
- What should I check before upgrading from 1.3.0 to 1.4.0?
- The 1.4.0 release is primarily a compatibility bump adding Laravel 8.x and 9.x plus StyleCI formatting changes, so behaviour should be unchanged, but verify rather than assume. Re-resolve Composer constraints for laravel/framework and php, then run your full notification test suite including queue serialization and package discovery. Check whether your PHP version sits inside the effective, if unstated, support window. Pin 1.4.0 once validated and track upstream releases before committing to the package long term.
Weaver
How can I help you explore Laravel packages today?