- How do I install lab404/laravel-mailjet-sms in a Laravel application?
- Install it with Composer using composer require lab404/laravel-mailjet-sms, then publish the package configuration if the package provides a config file. Add your Mailjet API credentials and approved SMS sender ID to the environment, and verify the Composer constraints against your Laravel and PHP versions before adopting it.
- Which Laravel and PHP versions does laravel-mailjet-sms support?
- The package's current release dates from February 2023, so its Composer constraints may not cover Laravel 10, Laravel 11, or PHP 8.2 and newer. Check the composer.json constraints and run a compatibility spike on your target Laravel and PHP matrix before using it in production. Do not assume support just because the package follows standard Laravel conventions.
- How do I send an SMS with laravel-mailjet-sms?
- The package is a thin Laravel wrapper around Mailjet's SMS API and exposes a facade or service for direct sends. Configure Mailjet credentials and a registered sender ID, then call the wrapper from your application code. Centralize calls behind an internal adapter so the provider can be replaced later.
- Can I send SMS notifications through Laravel's notification system with this package?
- Yes, the package is intended to provide a Laravel notification channel for SMS delivery via Mailjet. You define a notification and route it to the package's channel after configuring the Mailjet credentials. Test channel behavior, queued notifications, and config caching in your environment.
- Does lab404/laravel-mailjet-sms support queued notifications and retries?
- Queued SMS notifications depend partly on Laravel's notification queueing and partly on how the package's channel is implemented. Retry and rate-limiting behavior is not clearly documented in the overview, so audit the source and test queue workers before relying on it. Add application-level retries and logging where needed.
- What Mailjet setup is required before using this SMS package?
- You need a Mailjet account with SMS enabled, valid API credentials, and an approved sender ID for the destination countries. Country-specific SMS regulations and consent or opt-out requirements also apply. Confirm sender-ID registration and DPA requirements before going live.
- Is lab404/laravel-mailjet-sms safe to use in production?
- Treat it as a convenience wrapper that needs code review rather than a mature, widely validated dependency. It has very few GitHub stars and dependents, a single maintainer, and its last release was in February 2023, so maintenance and API drift are real concerns. Pin the version, review the license and source, and be prepared to vendor or fork it.
- How are Mailjet SMS API errors and delivery failures handled by this package?
- The overview does not document specific error, timeout, or delivery-failure handling, so inspect the package source and test failure paths. The wrapper likely surfaces Mailjet API errors through exceptions or standard Laravel error handling, but confirm that behavior. Add logging and fallback handling for critical SMS flows.
- Can I set different sender IDs per SMS message with laravel-mailjet-sms?
- Per-message sender IDs are not confirmed by the package overview, and Mailjet requires approved sender IDs for the countries you send to. Inspect the configuration and send methods to see whether a sender can be overridden per message. If not, keep sender selection in your internal adapter.
- How do I avoid vendor lock-in when using laravel-mailjet-sms?
- Wrap the package behind a small internal SmsSender interface and keep all direct calls in one adapter. Because the package is small, you can later replace it with a direct Mailjet HTTP client or another SMS provider without changing call sites. Run a time-boxed spike first and feature-flag the first low-risk notification.