Send bulk email with SendPortal
Install SendPortal on Laravel, configure a workspace email service, run queue workers and the scheduler, and send campaigns with bearer-token API access.
Reviewed
SendPortal is a Laravel campaign manager with subscribers, tags, templates, workspaces, and providers including SES, Postmark, SendGrid, Mailgun, Mailjet, Postal, and SMTP. Choose it when your team already runs Laravel and either wants the standalone application or wants to add its core package to an existing application that already handles users.
This guide installs the standalone v4 application, configures a workspace sending service, and starts the queue and scheduler. The SendPortal v4 documentation is the primary reference.
Prerequisites
- PHP 8.3 or newer and Composer.
- MySQL 5.7 or newer, or PostgreSQL 10 or newer.
- A web server pointed at the
publicdirectory. - A provider account and verified sending domain: SES, Postmark, SendGrid, Mailgun, Mailjet, Postal, or SMTP.
- A queue driver decision:
sync,database, orredis. - A cron entry for Laravel’s scheduler.
SendPortal v4 is built on Laravel 13. The application and core package are MIT-licensed.
Install the application
Clone the release you intend to run rather than an unpinned branch:
git clone --depth 1 --branch v4.0.0 https://github.com/mettle/sendportal.git
cd sendportal
composer install
Copy .env.example to .env, set APP_URL to the public base URL, and configure the database connection. Generate the application key if it is empty:
php artisan key:generate
Run the setup command, which can create the schema, a default user, and a workspace:
php artisan sp:install
The command is safe to rerun. If you configure manually instead, run php artisan migrate and publish the vendor files as the configuration guide describes.
Point the web server at public, not the project root. An nginx root value must end in /public, or the application’s files and routes will not serve correctly.
Choose the queue before the audience
SendPortal sends through a queue, and the queue driver is global to the installation, not per workspace. The three options have different failure modes:
syncruns jobs during the request. It is simple and suitable only for small lists.databaseuses the primary database and needsphp artisan make:queue-tableplusphp artisan migrate. It avoids another service but competes with application queries under load.redisis the documented recommendation for medium and large lists. Set the Redis connection values and run Laravel Horizon or explicit workers.
If you run workers without Horizon, start both queues:
php artisan queue:work --queue=sendportal-message-dispatch
php artisan queue:work --queue=sendportal-webhook-process
Add the scheduler entry so Laravel runs scheduled tasks every minute:
* * * * * cd /path-to-your-project && php artisan schedule:run >> /dev/null 2>&1
A campaign that is queued but never processed usually has a worker problem, not a provider problem. Check worker logs and queue depth before resending.
Configure workspace email services
Each workspace configures its own email service. This is separate from the application’s user-management mail configuration, which handles invitations and password resets. Configure both if you use those features.
After connecting a provider, send a test message to your controlled mailbox. Confirm the verified From domain, SPF/DKIM alignment, and the unsubscribe link. A workspace service that accepts a campaign but sends from an unverified domain will fail at the provider.
Use the API with a workspace token
API tokens are per workspace and presented as a Bearer token. The API expects Accept: application/json and Content-Type: application/json, and defaults to 60 requests per minute. The API introduction documents the token flow and error format.
Verify connectivity before building a client:
curl https://campaigns.example.com/api/v1/ping
Then create or select subscribers, a template, and a campaign through the documented endpoints. Persist the campaign ID and inspect the campaign’s send state; an accepted API request is not a delivered audience. Keep the token server-side and scope each integration to the workspace it serves.
Operate campaigns and feedback
Monitor queue workers, the scheduler, provider webhooks, and bounce suppression. Incoming webhooks are processed on sendportal-webhook-process; a stopped worker leaves delivery state stale even when the provider is sending events correctly.
Back up the database and .env together. Rehearse upgrades on a restored copy, and check the upgrade guide before changing Laravel or SendPortal versions. If you use the package inside an existing Laravel app, keep the package boundary explicit: the host application owns users and authentication, while SendPortal owns campaigns and subscribers.
Where MailKite fits
MailKite, which we build, is a hosted sending and receiving API. It does not provide SendPortal’s workspace UI or Laravel campaign model. It supports broadcasts and personalized batches but prohibits unsolicited bulk or commercial mail, sending without consent, and sending after opt-out.
If you are already in Laravel and only need transport, the PHP bulk email guide shows the MailKite SDK path. Moving from SendPortal means exporting subscribers with consent evidence, rechecking suppressions, and recreating templates and workspaces; queue state does not transfer.
Next steps
- Read the bulk email guide for the application/transport split.
- Compare self-hosted campaign tools in the listmonk vs Keila guide.
- See every option in the open-source bulk email comparison.
Sources reviewed 2026-11-07: SendPortal installation, configuration and setup, API introduction, and the license.