Weave Code
Mailjet Bundle Laravel Package
snowcap/mailjet-bundle
Snowcap Mailjet Bundle provides Symfony integration for the Mailjet email service, including configuration and services for sending transactional messages and accessing Mailjet API features from PHP applications. It helps wire Mailjet credentials and clients into Symfony projects.
Bundle used to provide access to Mailjet API
Frequently asked questions about Mailjet Bundle
- Can I use snowcap/mailjet-bundle in a Laravel application?
- No. snowcap/mailjet-bundle is a Symfony2 bundle that is loaded through Symfony's AppKernel registration and DependencyInjection extension machinery, and Laravel has no equivalent bundle loading path. Composer requiring it will not register services, resolve configuration, or wire Mailjet into Laravel's Mail system. Use a Laravel-native Mailjet transport instead.
- What is the best way to send Mailjet email from Laravel?
- Configure Mailjet as a DSN in config/mail.php, for example mailjet+api://PUBLIC:SECRET@default, and send through Laravel's Mail facade using the symfony/mailjet-mailer transport available through the installed Symfony Mailer. This preserves queueing, Mailable classes, and mail event hooks. It is the preferred path for Laravel 10 and 11 applications.
- Does snowcap/mailjet-bundle support Laravel 10 or 11?
- No. The package is built for Symfony 2.x, which reached end of life in 2019, and it transitively pins PHP 5.x/7.0-era constraints plus old Symfony and Guzzle component ranges. Those constraints will conflict with the Symfony 6/7 components modern Laravel ships. There is no supported path to use it in Laravel 10 or 11.
- How should I configure Mailjet credentials in Laravel?
- Put the Mailjet public and secret keys in environment variables and reference them from the DSN in config/mail.php, rather than using bundle-style YAML parameters. This keeps credentials out of version control and matches Laravel's standard configuration approach. Verify the DSN format against your installed Symfony Mailer version during a short spike.
- Is snowcap/mailjet-bundle still maintained?
- The bundle targets Symfony 2.x, which has been end of life since 2019, and it has very low adoption with a single maintainer. There is no population of users to surface defects and no advisory coverage, so the maintenance risk is high. Treat the repository as reference material rather than a dependency.
- How do I send a templated Mailjet message with attachments from Laravel?
- Use a Laravel Mailable with the attach method and send it through the Mail facade with a Mailjet DSN transport. Confirm whether your Mailjet templates rely on API v3 or v3.1 semantics before going live. Run a half-day spike that sends one templated message and one attachment message, and check deliverability and domain authentication.
- Can I use mailjet/mailjet-apiv3-php with Laravel instead of the bundle?
- Yes. You can wrap Mailjet's official PHP SDK in a custom TransportInterface implementation and bind it with Mail::extend. The required work is roughly 150 lines covering transport construction, credential wiring, and payload mapping. Prefer symfony/mailjet-mailer when it is already available through your installed Mailer version.
- Does snowcap/mailjet-bundle handle Mailjet webhooks or inbound parsing?
- The bundle is primarily Symfony integration for configuration and Mailjet API clients, so do not assume it covers webhooks or inbound parsing in the way your application needs. Those features are where wrapper packages typically add value and where a thin in-house transport needs the most care. Verify the API surface before relying on it, and expect to implement custom handling.
- How do I migrate from a Symfony Mailjet bundle to Laravel?
- Treat the repository as documentation only: extract the Mailjet endpoint, authentication headers, payload mapping, and error handling, then discard the DependencyInjection directory, Resources/config, and the bundle class. Move credential handling to environment variables. Then send a test message through your chosen Laravel transport before removing the old integration.
- Is it safe to copy code from snowcap/mailjet-bundle into my Laravel app?
- Confirm that the bundle's license permits copying implementation patterns into a first-party transport before carrying any code across. In practice you would copy a handful of methods, not a dependency, so also check Guzzle major version alignment with the framework's HTTP client. If the license is unclear, implement the Mailjet transport directly from the API documentation.
Weaver
How can I help you explore Laravel packages today?