Weave Code
Mailtrap Php Laravel Package
railsware/mailtrap-php
Official Mailtrap PHP SDK for Laravel and plain PHP apps. Send transactional email, manage templates and contacts, and integrate Mailtrap’s testing sandbox and email API workflows through a lightweight, framework-agnostic client.
The official mailtrap.io PHP client
Frequently asked questions about Mailtrap Php
- How do I install railsware/mailtrap-php in a Laravel application?
- Install it with Composer using composer require railsware/mailtrap-php, then configure a Mailtrap API token in your environment. Because the SDK is framework-agnostic, you can instantiate its client directly or bind it in Laravel's service container. The supplied context does not mention a first-party Laravel service provider or facade, so verify the package docs for the recommended Laravel wiring.
- Is railsware/mailtrap-php a Laravel-native package or a framework-agnostic SDK?
- It is the official Mailtrap PHP client and is framework-agnostic rather than a Laravel-native first-party package. Laravel apps can consume it through Composer and the service container, but basic notifications may still be simpler with Laravel's native SMTP mail transport. Use the SDK when you need API-level control over transactional email, templates, inbound rules, or thread search.
- What is new in Mailtrap PHP SDK 3.16.0?
- Version 3.16.0 is a minor, additive release that adds a Template API for paginated /api/templates endpoints, inbound forward rules, and thread search. No breaking changes or deprecations are called out in the release context. The release mainly expands the SDK into template administration and inbound email operations.
- Does upgrading from railsware/mailtrap-php 3.15.0 to 3.16.0 require code or data migrations?
- The release is described as additive, so existing sending code should remain unaffected and no data migration is indicated. You may still need account permissions, API token scopes, or plan-level enablement before using the new template and inbound features. Validate the upgrade with tests and a Mailtrap sandbox before production rollout.
- Which PHP and Laravel versions does railsware/mailtrap-php 3.16.0 support?
- The supplied release context does not list exact PHP or Laravel version constraints for 3.16.0. Check the package composer.json on Packagist and the repository documentation before upgrading. Your Laravel application must satisfy the SDK's Composer requirements, so test on your current PHP version first.
- Should I use railsware/mailtrap-php or Laravel's native mailer for transactional email?
- Laravel's native SMTP mail transport may remain simpler for basic notifications and one-off sends. The Mailtrap SDK is more valuable when the product needs API-level template pagination, inbound forward-rule management, or searchable email threads. You can let both coexist, but avoid maintaining duplicate send paths unless the product clearly needs both approaches.
- How does railsware/mailtrap-php handle pagination and rate limits for templates?
- Version 3.16.0 adds a Template API for paginated /api/templates endpoints, but the supplied notes do not define page-size limits, cursor semantics, or iterator support. Check the SDK documentation and tests to see whether responses are raw or iterable. Also confirm rate-limit and retry behavior before relying on it in admin tooling.
- Do the new Mailtrap template endpoints support create, update, and delete operations?
- The release context only confirms a Template API for paginated /api/templates endpoints; it does not state whether create, update, or delete operations are included. Verify the endpoint documentation and SDK methods rather than assuming full CRUD support. If you only need template discovery, the paginated read path may be sufficient.
- What Mailtrap permissions or plan settings are required for inbound forward rules and thread search?
- The SDK upgrade alone is probably not enough; new capabilities likely require the right API token scope, Mailtrap account permissions, and possibly plan-level enablement for inbound features. Confirm these settings in the Mailtrap account before implementation. Test the configuration in a sandbox because misconfigured forward rules can affect mail routing.
- How should I test inbound forward rules and thread search before production?
- Use Mailtrap's sandbox and suitable test credentials to validate permissions, routing behavior, reversibility, and audit expectations before enabling production rules. Confirm data-handling, retention, and access-control requirements because inbound routing and thread search may expose or redirect message content. Roll out changes with limited scope and verify that rule changes can be safely reverted.
Weaver
How can I help you explore Laravel packages today?