1. Create a scoped key
In Helios Post, open Settings → API keys. Create one key for this integration. Select only the scopes it needs. Keys are returned once; store the value in your server’s secret manager immediately.
2. Read a page of messages
curl --fail-with-body \
-H "Authorization: Bearer ${LUCION_MAIL_API_KEY}" \
-H "Accept: application/json" \
"https://lucionmail.com/api/v1/mail/messages?folder=inbox&limit=25&offset=0"This requires `mail.read`. A successful response contains a bounded page and may include private message text. Do not send it to analytics or a public log sink.
3. Send safely
curl --fail-with-body -X POST \
-H "Authorization: Bearer ${LUCION_MAIL_API_KEY}" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: order-4821-confirmation" \
--data '{"to":["recipient@example.com"],"subject":"Order confirmed","text":"Your order is confirmed."}' \
"https://lucionmail.com/api/v1/mail/messages"This requires `mail.send`. Use a unique idempotency value for each logical message and reuse that same value only for identical retries.
4. Interpret the result
A `202 Accepted` means the configured provider accepted the send request for processing. It is not proof of delivery or inbox placement. Read the response, retain its provider message identifier where useful, and consult the delivery guide.
All API responses include `X-Lucion-API-Version: 1`; responses are marked `Cache-Control: no-store`.