- How do I install and configure overtrue/laravel-sendcloud?
- Install it with composer require overtrue/laravel-sendcloud. The service provider and the sendcloud facade alias are auto-discovered, so no manual registration is needed on supported Laravel versions. Publish the package config and fill in the services.sendcloud credentials before making any API calls.
- Is overtrue/laravel-sendcloud a Laravel Mail transport?
- No. Version 2.0 is a service-provider wrapper around the overtrue/sendcloud PHP SDK and does not register a Mail or Notification transport. Mail::to() and notification channels will not route through SendCloud with this package alone. You call SDK methods directly through the injected client or the sendcloud facade.
- What PHP and Laravel versions does version 2.0 support?
- Version 2.0.0 requires PHP ^8.3 and Laravel ^13.30. Laravel 9, 10, 11, 12 and any release below 13.30 are unsupported by this release. If your services are on Laravel 12 or earlier, treat adoption as a framework upgrade project rather than a dependency bump.
- How do I actually send an email with this package?
- Resolve the SendCloud client from the container or via the sendcloud facade, then call the SDK methods for the SendCloud API endpoints you need. The package handles wiring only; request payloads, templates and error handling come from overtrue/sendcloud. There is no Laravel Mailable integration, so build a thin wrapper yourself if you want that ergonomics.
- Does this package work with Laravel Octane, RoadRunner or Swoole?
- Octane compatibility is explicitly not claimed by the package or its evaluation. The facade caches its client until facade state is reset, and configuration is effectively frozen at first resolution, which is the classic failure shape in long-running workers. If you deploy under Octane, RoadRunner or Swoole, test config changes, tenant switching and facade resets in a resident-worker setup before relying on it.
- What breaking changes should I expect moving to version 2.0?
- Most behavioral risk comes from the SDK major, not the Laravel wrapper: HTTPS is the default, redirects are disabled, and cross-origin or HTTPS-downgrade redirects hard-fail at runtime. Configured credentials now take precedence, and leading-slash paths preserve /apiv2/. Upgrade overtrue/sendcloud to ^2.0 and Guzzle to 7.15.2+ in the same commit as this package, and review any custom middleware or redirect handling.
- How do I handle attachments or multipart uploads with the 2.x SDK?
- Prebuilt multipart bodies are no longer safe on the 2.x SDK path. Use the SDK upload() helper or its multipart options so the client builds the body correctly. Audit any code that assembled multipart payloads by hand before upgrading.
- How is the package tested, and is it safe for production?
- CI runs 13 Testbench integration tests with 36 assertions against a mocked transport on PHP 8.3, 8.4 and 8.5, plus a lowest-secure-deps job, strict Composer validation and an audit. That verifies container wiring and provider registration but proves nothing about the live SendCloud API contract. Run a sandbox smoke test with real credentials before production rollout.
- Can I use it in multi-tenant apps or test suites that boot multiple app instances?
- Yes, that is one of the improvements in 2.0: the client is resolved from the container, which fixes application and container isolation across multiple booted app instances. The caveat is that the facade caches its client until facade state is reset, and client construction stays transient. Reset facade state between tenants or test cases if configuration differs.
- Is there a supported upgrade path from 1.x, and what should I upgrade together?
- Treat it as two projects: first upgrade the platform to Laravel 13.30+ and PHP 8.3+, then co-upgrade overtrue/laravel-sendcloud ^2.0, overtrue/sendcloud ^2.0 and Guzzle 7.15.2+ in one commit. Never mix a 1.x wrapper with the 2.x SDK. Inventory composer show output across repos first to build the blocked-services list, and confirm 1.x security-fix status and your rollback window with the maintainers before committing.