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

# Introduction

> Send receipts, confirmations, and campaigns by email from the dashboard or API, with verified domain and delivery tracking.

<Tip>
  Email is **registered mail, digital edition**: long text, HTML, trackable links, ideal for receipts, password resets, and order confirmations.
</Tip>

## What is Email on Notifique?

It's the channel for **transactional messages and campaigns** from **your domain** as sender. You send from the **dashboard or API**; the platform handles queue, delivery, and status for each message.

You can:

* **Send** receipts, confirmations, newsletters, and alerts with HTML and links
* **Schedule** sends for a future date and time
* **Query** history and status for each email
* **Track** delivery, opens, and clicks via webhook
* **Cancel** scheduled sends before they hit the queue

Think of it as certified mail: it lands in the inbox, and you know if it was delivered and opened.

<Note>
  Unlike WhatsApp, email **does not use an instance**. You only need a **VERIFIED** domain, an API Key with the right scopes, and valid recipients.
</Note>

## When to use it?

Works great for **receipts**, **password resets**, **order confirmations**, and **long text with links**. For urgent phone alerts in seconds, prefer [SMS](/en/sms-api/como-funciona/introducao) or push. For real-time conversation, use [WhatsApp](/en/whatsapp-api/como-funciona/introducao).

## How it works in practice

1. **Register and verify a domain** in DNS (proves you control `@yourdomain.com`)
2. **Send** with a verified sender, recipients, subject, and body (`text` and/or `html`)
3. The platform **queues, sends, and updates status**; your backend gets alerts if you configured [webhooks](/en/emails-api/como-funciona/eventos-do-webhooks)

<Info>
  Each **API Key** belongs to **one** workspace. On v1 **do not send** `x-workspace-id`.
</Info>

## Verified domain

Before the first send, the **`from`** domain must be **VERIFIED**. Register in the dashboard or API, add the DNS records Notifique shows, and call verify until confirmed.

* **PENDING**, domain registered, DNS not validated yet
* **VERIFIED**, ready to use as sender
* **FAILED**, verification failed; check TXT/CNAME at your DNS provider

Without a verified domain, send returns **400** with `DOMAIN_NOT_VERIFIED`. Verify codes: [Error responses](/en/guides/conceitos/resposta-de-erros#email-verify-domain-post-v1emaildomainsidverify).

## Message lifecycle

After `POST`, the email moves through `QUEUED` or `SCHEDULED`, then `SENT`, `DELIVERED`, `OPENED`, or `CLICKED` as engagement happens. Failures become `FAILED`; spam complaints become `COMPLAINED`; cancelled schedules become `CANCELLED`.

API cancellation only works while status is **`SCHEDULED`**.

## What you can do

* **Send** to 1 to 100 recipients per call
* **Schedule** with `schedule.sendAt`
* **Query** history or one send by id
* **Cancel** scheduled sends before queue
* **Idempotency** with `Idempotency-Key` header to avoid duplicates
* **One-click unsubscribe** (RFC 8058) on campaigns, guide: [One-click unsubscribe](/en/emails-api/como-funciona/one-click-unsubscribe-rfc-8058)

Each email typically consumes **1 credit** (plan) or balance on **Pay as you go**. See [Billing](/en/guides/introducao/cobranca-e-pague-pelo-uso).

Field and error details: **API reference** on the Email tab.

## After your first send

* **Track** delivery, opens, and clicks via [webhooks](/en/emails-api/como-funciona/eventos-do-webhooks) (`email.sent`, `email.delivered`, `email.opened`, …)
* **Suppress** addresses that complained when you receive `email.complained`
* **Test** in [Sandbox](/en/guides/sandbox/index) with `sk_test_...` before production

## Next steps

* [Quick Start](/en/emails-api/como-funciona/quick-start): domain, first send, and query
* [API Key scopes](/en/emails-api/como-funciona/escopos-da-api-key): permissions
* [Webhook events](/en/emails-api/como-funciona/eventos-do-webhooks): what hits your URL
* [Get started](/en/guides/introducao/comece-aqui): general platform integration