Helios PostDeveloper docs
DocumentationCore concepts

LUCION MAIL DEVELOPER GUIDE · v0.4.17

Core concepts

Understand the identity, address, mailbox, and authorization boundaries behind the API.

Updated October 14, 2026Official product documentation

Mail account and Identity subject

A personal Mail account is bound server-side to the stable Lucion Identity subject. A caller cannot provide another subject or account ID to select a mailbox. Sign-in email is used for account communication and key alerts; it is not the authorization key for mailbox data.

Addresses and sender ownership

Mail addresses belong to a Mail account. Send requests may omit `from` and use the configured default, or specify an address already owned by the same mailbox bound to the key. Address ownership is enforced on the server for each request.

Mailbox scope

Each key is bound to exactly one personal or organization shared mailbox. Organization API keys are created and revoked by administrators and cannot read employee inboxes, change aliases, or access a different mailbox. API callers cannot choose a mailbox in the request.

Scopes

  • `mail.read` allows reading message information and message text.
  • `mail.send` allows sending mail from owned addresses.
  • Neither scope grants message mutation, organization administration, or access to the other capability.

Idempotency

An idempotency key identifies one logical send operation. It prevents retries after timeouts from producing duplicate mail and binds the key to a request fingerprint. Reusing it with changed content is rejected.

Documentation for Helios Post 0.4.17. Check release history when upgrading.