
Send email with PHP.
Use the official Parcel Wing SDK to send product and campaign email from PHP with a lightweight integration that scales past the first demo.
Start with one send, then grow into verified domains, deliverability tooling, and inbox visibility on the same platform.
Start with one send.
Install with Composer, create a client, and send the same clean payload your app can keep using in production.
Package
parcelwing/parcelwing-php
Install
composer require parcelwing/parcelwing-php
1<?php23require __DIR__ . "/vendor/autoload.php";45use ParcelWing\ParcelWing;67$parcelwing = new ParcelWing($_ENV["PARCELWING_API_KEY"]);89$emails = $parcelwing->emails->send([10"from" => "Acme <[email protected]>",11"to" => "[email protected]",12"subject" => "Hello World",13"html" => "<strong>It works!</strong>",14]);1516print_r($emails[0]);
Resources
Everything nearby while you integrate.
parcelwing-php
Browse the official SDK source, releases, and package history.
Example repo
Start from a small working app instead of assembling the first send by hand.
Quickstart docs
Wire up your API key, domain, and first message with the shortest path to green.
API reference
Keep the object model, method signatures, and send options close while you build.
Why this SDK
A PHP SDK built for app email that outgrows the demo phase.
Simple first send
Get from install to live email quickly without building around a throwaway demo integration.
Framework-agnostic shape
Keep the SDK close to Laravel, Symfony, Slim, or plain PHP without wrapping your send path around framework-specific glue.
Production-friendly path
Use the same platform for password resets, invites, receipts, alerts, and lifecycle messaging.
Deliverability built in
Layer in domains, routing, and deeper delivery visibility when the stakes rise.
Workflow
Move from install to live sends fast.
Step 1
Install with Composer
Add `parcelwing/parcelwing-php`, load your API key, and keep the client setup alongside the rest of your application services.
Step 2
Send your first email
Post one email payload, then inspect the queued email array you get back for logs, UI feedback, or job chaining.
Step 3
Scale on the same integration
Add domain setup, routing, and deliverability tooling later without replacing the send contract your app already uses.
