> For the complete documentation index, see [llms.txt](https://kasplo.gitbook.io/kasplo-doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kasplo.gitbook.io/kasplo-doc/product-docs/overview/email-api/introduction.md).

# Introduction

Kasplo's Email API lets you send transactional emails, such as order confirmations, OTPs, password resets, and notifications, programmatically via API or SMTP, with full visibility into delivery at every stage.

### How it fits together

Every client operates under a Parent **Account**, which can create multiple **Sending Profiles** underneath it — for different teams, domains, or use cases (e.g. `marketing.yourdomain.com`, `support.yourdomain.com`). Each Parent Account and Sending Profile has its own domain, DNS, and API/SMTP credentials, but billing and credits are shared at the Parent level.

This means you can scale sending across departments or products without raising a request with Kasplo each time — Sending Profiles are created and managed entirely from your dashboard.

### The typical flow

1. **Set up an Sending Profile** — use the Parent Account directly, or create a Sending Profile for a specific domain/use case.
2. **Configure it** — add your sending domain, verify DNS, and retrieve API/SMTP credentials.
3. **Send emails** — via the API or SMTP using those credentials, optionally tagging sends with a **Campaign ID** to group related emails.
4. **Track delivery** — monitor sends in real time via Live Feed, or review trends in Statistics and Delivery Attempt Statuses.
5. **Monitor usage** — the Parent Account can track credit consumption and activity across itself and all Sending Profiles.

### Where to go next

* New to accounts? Start with **Accounts** to create and configure one — including usage, credits, and roles/access.
* Sending in batches or grouped campaigns? See **Campaign ID & Tracking** under the Campaigns section.