Weave Code
Mailgun Php Laravel Package
mailgun/mailgun-php
Official Mailgun PHP SDK (PSR-18/PSR-7 compatible) for sending email and managing Mailgun API features like domains, IPs/pools, analytics, and subaccounts. Works with your chosen HTTP client; supports US/EU endpoints.
The Mailgun SDK provides methods for all API functions.
Frequently asked questions about Mailgun Php
- How do I install the Mailgun PHP SDK in a Laravel application?
- Install it with Composer using composer require mailgun/mailgun-php symfony/http-client nyholm/psr7. The SDK needs a PSR-18 HTTP client and a PSR-7/PSR-17 implementation, and Laravel's default Symfony HTTP client can satisfy the PSR-18 side. Then bind Mailgun::create() in a service provider or config file so your API key comes from .env.
- Is mailgun/mailgun-php compatible with Laravel?
- Yes, although the SDK is framework-agnostic, its PSR-18 and PSR-7 design fits Laravel's dependency injection and service-layer patterns. You can register it as a singleton, inject it into services, and wrap SDK calls with Laravel events for logging or auditing. Laravel's native Mailgun driver also suggests deep compatibility, but test against your target Laravel version.
- What PHP and Laravel versions does the Mailgun PHP SDK support?
- The SDK requires PHP 7.4 or higher and is not tied to a specific Laravel release. For Laravel 10 or 11, verify that your chosen PSR-18 client version matches Laravel's vendor constraints, and use Composer overrides if needed. Older LTS applications should be tested because dependency conflicts are more likely than SDK API incompatibilities.
- How do I send an email through Mailgun in Laravel using this SDK?
- Create the client with Mailgun::create('your-api-key'), optionally passing the EU endpoint as the second argument. Then call $mg->messages()->send('example.com', [...]) with from, to, subject, and text or html fields. In Laravel, keep the API key in config or .env, resolve the client from the container, and make sure the domain matches one configured in Mailgun.
- Do I need Guzzle to use mailgun/mailgun-php?
- No, the SDK is not coupled to Guzzle. You can use symfony/http-client, guzzlehttp/guzzle, or another PSR-18 client, plus a PSR-7/PSR-17 implementation such as nyholm/psr7. The README's installation example uses symfony/http-client and nyholm/psr7 with Composer.
- How do I configure the Mailgun EU endpoint in a Laravel app?
- Pass https://api.eu.mailgun.net as the second argument to Mailgun::create() when your Mailgun domain is in the EU region. The default is the US endpoint, so store the region or endpoint in Laravel config and select it based on environment. Keep the API key and endpoint separate from application code.
- How should Laravel handle Mailgun API errors and rate limits?
- The SDK throws exceptions for API failures, so catch them in your service layer and either log via Laravel's Log facade or convert them to custom exceptions. For transient failures such as 429 Too Many Requests, use Laravel queues with retries and backoff rather than blocking web requests. Monitor rate limits and bursty sends because Mailgun enforces API limits.
- Can I test Mailgun integration in Laravel without sending real email?
- Yes, mock the PSR-18 HTTP client or use Laravel's HTTP mocking, Mockery, or a VCR-style recorder so tests never hit the real Mailgun API. Cover edge cases such as malformed responses and rate-limit errors, not just successful sends. This keeps tests fast and avoids consuming your Mailgun quota.
- Does mailgun/mailgun-php support subaccounts, IP pools, and analytics?
- Yes, the SDK exposes domain-specific modules for messages, IPs, dynamic IP pools, analytics, and subaccounts. In Laravel you can wrap these modules in services or a facade, cache analytics results in Redis, and use queues for bulk IP assignments. Subaccount support may require dynamic API key switching, so design that authentication path carefully.
- Is mailgun/mailgun-php production-ready and what are Laravel alternatives?
- It is Mailgun's official PHP SDK with PSR-18/PSR-7 compatibility, so it is suitable for production when you handle rate limits, retries, and monitoring. For basic email sending, Laravel's built-in Mailgun mail driver or Symfony Mailer may be simpler; use this SDK when you need domains, IP management, analytics, or subaccounts. Check the repository releases and license before adopting it.
Weaver
How can I help you explore Laravel packages today?