Weave Code
Mailjet Api Php Laravel Package
knplabs/mailjet-api-php
A lightweight PHP wrapper for the Mailjet API from KNP Labs, offering straightforward access to Mailjet endpoints for sending email and managing contacts, lists, and campaigns. It suits PHP projects that need a simple, direct Mailjet integration without a large framework dependency.
KNPLabs Mailjet API PHP is a lightweight PHP client for the Mailjet email API. It wraps Mailjet's REST endpoints in a simple object-oriented interface, so you can send transactional and marketing emails, manage contacts and lists, and query delivery statistics without hand-writing HTTP requests.
- Fluent wrappers for core Mailjet REST resources (messages, contacts, lists)
- Built-in API key authentication and request handling
- Composer-installable with an extensible, PSR-friendly structure
- Suitable for both transactional and campaign email workflows
Frequently asked questions about Mailjet Api Php
- Is knplabs/mailjet-api-php still maintained?
- No. The package is archived and has had no releases since 2015. Treat it as a legacy adapter and do not expect security patches, PHP compatibility fixes, or updates for current Mailjet API behavior.
- Does knplabs/mailjet-api-php work with Laravel 10 or 11?
- It is not Laravel-native and is unlikely to resolve cleanly with modern Laravel and PHP 8.x because of outdated transitive dependencies. Run a dependency-resolution spike in a disposable branch before committing. For new projects, prefer Mailjet's current official SDK or a thin adapter built on Laravel's HTTP client.
- How do I install knplabs/mailjet-api-php with Composer?
- You would normally run composer require knplabs/mailjet-api-php, but the archived package may conflict with current PHP, Guzzle, or PSR constraints. Validate Composer resolution against your exact Laravel and PHP versions first. If resolution fails or requires broad dependency pinning, do not force it into a modern application.
- What is knplabs/mailjet-api-php used for?
- It is a standalone object-oriented PHP wrapper for the Mailjet API, aimed at sending transactional email and managing Mailjet resources. It may still map to a simple send use case, but its API assumptions are stale. It does not provide a modern Laravel mail transport or Laravel-specific integration.
- Does it provide a Laravel service provider, facade, or config publishing?
- No. It does not provide a maintained Laravel service provider, facade, configuration publishing, queue integration, or current HTTP client abstractions. Any Laravel wiring, configuration, error handling, and isolation would be application-owned.
- Should I use knplabs/mailjet-api-php for a new Laravel project?
- No, it is not recommended for greenfield Laravel work. Technical risk is high because the upstream is abandoned, dependencies are stale, and there is no security patching. Use Mailjet's current official SDK or a small adapter against the current Mailjet API instead.
- What are the alternatives to knplabs/mailjet-api-php for Laravel?
- Use Mailjet's current official SDK, direct Mailjet API calls through Laravel's HTTP client, or a small custom mail transport. Keep the integration behind an application-owned interface such as EmailSender or MailjetTransport. That keeps controllers and jobs independent of the package and makes future replacement easier.
- How do I migrate an existing Laravel app off knplabs/mailjet-api-php?
- Inventory call sites and classify them by capability: transactional send, templates, batch sends, webhooks, and error handling. Wrap the legacy client behind an application-owned interface, add contract tests, and replace internals incrementally with the official SDK or direct API calls. Remove the package only after low-risk flows have migrated and tests cover provider failures.
- What production risks come with knplabs/mailjet-api-php?
- Key risks include abandoned upstream maintenance, stale Mailjet API assumptions, incompatible dependency constraints, absent security patching, and weak PHP 8 compatibility. You may also encounter mismatches with current endpoints, TLS requirements, or authentication expectations. Community validation is low, so assume internal ownership if the package must remain in production.
- How should I test a legacy Mailjet integration in Laravel?
- Start with a dependency-resolution spike against the target Laravel and PHP versions, then test through an application-owned interface rather than the package directly. Add contract tests for successful sends, throttling, invalid recipients, template errors, and provider outages using Mailjet sandbox behavior or fakes. This gives you a safe migration path and clear failure expectations.
Weaver
How can I help you explore Laravel packages today?