Mail · Customer documentation

What you prepare

Only a destination webhook URL; you do not need a domain or MX record. PicoSvc Hooks can provide a destination.

Steps in the workspace

1. 01Create a Hooks destination or use an existing webhook.
2. 02Create a Mail route and copy its address.
3. 03Send a test email and check event and delivery status.

Example request / integration

Create a Hooks inbox, use its URL for a Mail route, send a test email to the issued address, then inspect the JSON in Hooks.

# 1. Create a Hooks inbox and copy its receiving URL.
# 2. Create a Mail route, using the Hooks URL as webhookUrl.
# 3. Copy the issued address: [email protected]
# 4. Send a test email from your mail client.
# 5. Check Mail delivery history AND the Hooks event body.

Examples use placeholders: replace $BASE_URL, $SESSION_TOKEN and issued URLs with real values. Never publish session tokens or API keys in a webpage or repository.

Mail does not require you to configure email DNS. Send mail to the address issued by PicoSvc. Do not consider mail receiving production-ready until the operator has configured incoming mail and verified end-to-end delivery.

Management API entry point

POST /api/picosvc/mail/routes

Route name and a destination webhook URL.

An [email protected] receiving address, delivery history, and JSON sent to your webhook.

What it does not do

Not an inbox UI or sending API. Receiving remains unverified until operator setup and an end-to-end delivery test pass.

Feature comparison and sources

Receiving address and mail processing：Issue a distinct address per route and relay to a webhook with history.

Resend Receiving：Documents inbound mail on provided or custom domains, with content and attachment APIs.