SMTP
Send email with SMTP
Use Parcel Wing SMTP when a framework or vendor expects traditional SMTP credentials instead of an HTTP API.
When to use SMTP
Prefer a Parcel Wing SDK or the HTTP API when you own the application code. Use SMTP for hosted products, legacy apps, CMS plugins, and authentication providers that only accept SMTP credentials.
SMTP settings
Copy the exact values from your in-app Settings page. Most accounts use these defaults.
smtp.parcelwing.com587STARTTLSparcelwingAny active Parcel Wing API keySecurity
- Use STARTTLS on port
587. - Use an active Parcel Wing API key as the SMTP password.
- Rotate the API key if it is pasted into a third-party system you no longer use.
- Keep SMTP credentials in server-side configuration or vendor secret fields.
Test the connection
You can verify the SMTP server accepts STARTTLS before configuring a vendor.
Terminal
openssl s_client -starttls smtp -connect smtp.parcelwing.com:587
Integration guides
Auth0
Configure Auth0 to send email through Parcel Wing SMTP.
Supabase
Configure Supabase to send email through Parcel Wing SMTP.
WordPress
Configure WordPress to send email through Parcel Wing SMTP.
Nodemailer
Configure Nodemailer to send email through Parcel Wing SMTP.
Laravel
Configure Laravel to send email through Parcel Wing SMTP.
Rails
Configure Rails to send email through Parcel Wing SMTP.
Django
Configure Django to send email through Parcel Wing SMTP.
Ghost
Configure Ghost to send email through Parcel Wing SMTP.
Strapi
Configure Strapi to send email through Parcel Wing SMTP.
Troubleshooting
- Use port
587with STARTTLS, not implicit TLS on port 465. - Use
parcelwingas the username and an active Parcel Wing API key as the password. - Make sure the sender address uses a verified sending domain.
- If a vendor has a test email button, send a test before enabling production email.