> ## Documentation Index
> Fetch the complete documentation index at: https://docs.basaltic.sh/llms.txt
> Use this file to discover all available pages before exploring further.

# Email

> Verify sender identities, send email, configure receiving, and inspect message outcomes.

Email manages verified sender identities, outgoing messages, templates,
configuration sets, suppressions, IP pools, and incoming mail. Receiving
rules route accepted mail to Notifications topics.

The service is regional. The endpoint for São Paulo is
`https://email.sa-saopaulo-1.basaltic.sh`. Authenticated calls use a bearer
token and the account handle in `X-Account-Id`; see
[Authentication](/authentication).

## Sender identities

An identity starts pending and returns the DNS records needed to verify
ownership and configure DKIM. Publish those records at your DNS provider,
then request verification. Only verified identities may send. Verification
belongs to the region where you created the identity.

## Sending and receiving

The send APIs accept message content directly or render a stored template.
Message records, rejection records, and Telemetry metrics expose different parts
of the sending lifecycle. An accepted send request does not establish that
the recipient's mailbox received the message.

For incoming mail, enable receiving on the identity and configure recipient
rules. Saving a rule requires `email:CreateRecipientRule` on the identity and
`notifications:Publish` on the destination topic. Reading received-message
metadata is separate from reading its content or downloading attachments.
See [Email permissions](/email/permissions).

## Resource references

Request selectors such as `identity`, `template`, `configuration_set`, and
`ip_pool` accept a UUID, an account-scoped name, or the matching resource CRN.
Names are immutable. Resource paths for identities, messages, templates,
configuration sets, IP pools, dedicated IPs, and suppressions use UUIDs.

Dedicated IPs belong to the account and can be unassigned or moved between
pools. Their nullable `ip_pool` field is a resource reference with `id`, `crn`,
and `name`. Manage membership in an IP pool's **Member IPs** tab; detaching an
IP keeps it allocated to the account. Configuration sets expose their pool
binding as an optional `ip_pool` resource reference.

<CardGroup cols={2}>
  <Card title="Sender identities" href="/email/identities">Verify a domain, publish its DNS records, rotate DKIM keys, and configure sender authentication.</Card>
  <Card title="Sending email" href="/email/sending">Send messages, handle acceptance and partial bulk results, and inspect delivery outcomes.</Card>
  <Card title="Email templates" href="/email/templates">Create text and HTML templates and send personalized messages to one or many destinations.</Card>
  <Card title="Configuration sets and suppressions" href="/email/configuration-sets">Control sending, engagement tracking, dedicated IP selection, and suppression exceptions.</Card>
  <Card title="Receiving email" href="/email/receiving">Route recipient addresses to Notifications topics and retrieve accepted email safely.</Card>
  <Card title="Dedicated IPs and pools" href="/email/dedicated-ips">Allocate sending addresses, manage movable pool membership, and warm up traffic.</Card>
  <Card title="Email metrics" href="/email/metrics">Read sending, feedback, engagement, backlog, and latency through Telemetry.</Card>
  <Card title="Permissions" href="/email/permissions">IAM actions and cross-service grants.</Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.