Transactional email delivery for Laravel applications.

1. Check runtime and sender requirements

Use Laravel 10, 11, or 12 with PHP 8.1 or newer and the PHP cURL extension. In EmailDesk, create an active customer API credential and allow the intended From address or domain.

Publish the SPF, DKIM, and DMARC records required for the selected sending gateway. Sender authentication supports provider evaluation but does not guarantee inbox placement.

2. Download the package

Download the current versioned package from EmailDesk:

https://app.emaildesk.bd/api/downloads/laravel-plugin

3. Install with Composer

mkdir -p packages/emaildesk
unzip emaildesk-laravel-api-sender-1.0.0.zip -d packages/emaildesk
composer config repositories.emaildesk-laravel-api-sender path packages/emaildesk/emaildesk-laravel-api-sender
composer require emaildesk/laravel-api-sender:*
php artisan vendor:publish --provider="EmailDesk\\LaravelApiSender\\EmailDeskApiSenderServiceProvider" --tag=emaildesk-api-sender-config

The package registers an emaildesktransport through the Laravel service provider. Review the published configuration before changing the application's default mailer.

4. Configure environment values

MAIL_MAILER=emaildesk
EMAILDESK_API_ENDPOINT=https://app.emaildesk.bd/api/v1/send
EMAILDESK_API_KEY=YOUR_EMAILDESK_API_KEY
EMAILDESK_FROM_EMAIL=info@example.com
EMAILDESK_FROM_NAME=Example Laravel app
EMAILDESK_MESSAGE_TYPE=transactional
EMAILDESK_PROFILE_NAME=MailChannels
EMAILDESK_TIMEOUT=20

Keep the API key in server-side secret management. Do not put it in browser code, source control, screenshots, logs, analytics, or support messages. The configured timeout is clamped between 5 and 60 seconds.

5. Clear configuration and test synchronously

php artisan config:clear
php artisan tinker

Mail::raw('Test email from Laravel through EmailDesk', function ($message) {
    $message->to('recipient@example.net')->subject('EmailDesk transport test');
});

Confirm the application receives a successful result, then review EmailDesk Outbound History for source laravel, the sender, policy result, message ID, queue state, and provider response.

6. Roll out queue workers deliberately

Rebuild cached configuration as required by the deployment and run php artisan queue:restartso long-running workers load the new transport settings. Start with a narrow queue or controlled job type.

A worker retry can make another API attempt. If a worker loses the response after EmailDesk accepted the request, the package has no application idempotency key to prove the retry is the same send. Keep a stable business event or job record and review failed-job plus EmailDesk evidence before a manual replay.

7. Understand the payload and attachment limit

{
  "fromEmail": "info@example.com",
  "fromName": "Example Laravel app",
  "to": ["customer@example.net"],
  "cc": [],
  "bcc": [],
  "subject": "Welcome",
  "body": "Plain-text body",
  "html": "<p>Optional HTML body</p>",
  "messageType": "transactional",
  "profileName": "MailChannels",
  "originSource": "laravel"
}

The current transport does not serialize mailable attachments. For attachment workflows, use a reviewed direct EmailDesk API integration and follow the documented request and attachment limits.

8. Handle errors without leaking secrets

The transport throws TransportException for missing API configuration, unsupported raw messages, missing recipients or From identity, unavailable cURL, network failures, invalid JSON, non-success HTTP responses, and unsuccessful EmailDesk results.

Log the job or business-event identifier, exception category, HTTP status when available, and returned EmailDesk message ID. Do not log the Authorization header, API key, complete message body, or recipient list.