Sending email

Parcel Wing accepts email from the dashboard, API, SDKs, and SMTP, then records each message and delivery event so you can debug real delivery instead of guessing.

Send with the API Try the dashboard test sender

Ways to send

Most production applications should send through the API or an official SDK. SMTP is best when you are connecting a system that already expects SMTP settings, such as an auth provider, CMS, ecommerce plugin, or legacy application.

Send Test page

Send a real delivery check from the dashboard before wiring production traffic.

HTTP API

Send raw transactional messages or render saved templates from your app backend.

SMTP

Connect tools that already know how to speak SMTP, including auth systems and CMSs.

Lifecycle events

Trace messages through accepted, queued, processing, sent, failed, and later delivery events.

Before you send

Every production send needs a verified and active sending domain. Parcel Wing uses the sender domain in the from address to find the tenant domain, confirm it is verified, choose an available mail node, and apply reputation guardrails before delivery.

Verify your sending domain and publish the required DNS records.
Create an API key for server-side API or SDK usage.
Use a realistic sender name, subject, and body for test messages.
Keep API keys, SMTP passwords, and mailbox app passwords on trusted servers only.

What happens next

After Parcel Wing accepts a send request, it creates a message record, emits a queued event, selects a mail node, attempts delivery, and records the SMTP result. Later events such as delivery, bounce, complaint, open, click, or suppression can enrich the same message trail.

Screenshot placeholder

Email detail timeline in the dashboard

Capture a sent transactional email detail page showing the message metadata, current status, and event timeline with queued and sent events visible.

Replace this placeholder with a product screenshot during the follow-up screenshot pass.

Next steps

Start with the Send Test page to confirm your domain and mailbox placement, then move to the API or SDK for production application traffic. Use SMTP only when the sending product cannot call the API directly.