> ## Documentation Index
> Fetch the complete documentation index at: https://sendmux.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Sending accounts
> Add, import, route, and monitor the accounts Sendmux uses to deliver email.
Every team can send as soon as it is created. Sendmux includes a managed Amazon SES sending account, and you can add your own accounts when you need more control.
The app calls these **sending accounts**. The Management API calls the same resources **providers**.
## Default managed account
The managed account is active by default. It is best for first sends and low-volume traffic.
| Setting | Value |
| -------------------- | ----------------- |
| Starting limit | 50 emails per day |
| Limit reset | 00:00 UTC |
| Setup | None |
| Editable credentials | No |
| Delivery groups | Not supported |
Managed Amazon SES is for transactional email only. Use your own provider for
marketing, newsletters, or bulk promotional sends.
When usage reaches 80% of the daily limit, **Request increase** appears on **Accounts**. You can also call `POST /providers/shared-amazon-ses-limit-request` from the Management API. Submit the request once. Sendmux reviews it and emails the outcome.
If the managed account is inactive and no other active provider exists, sends
fail with `no_active_providers`.
## Add your own account
Use your own provider when you need higher volume, a specific sender policy, or direct control of account credentials.
Open **Accounts** and select **Add Account**.
Choose **Custom SMTP**, **Gmail**, or **Outlook / Microsoft 365**. **HTTP
API** is visible as a coming-soon option.
SMTP accounts need server address, port, protocol, username, password, and
optional sender defaults. Connected accounts send you through the provider's
sign-in flow.
For SMTP accounts, use **Test Connection** after saving. Fix any credential
or network error before routing production mail through the account.
## Import accounts from a file
Use CSV to create or update custom accounts in bulk. Use a Sendmux JSON
configuration file to transfer supported non-secret values without spreadsheet
formatting.
Open **Accounts**, select **Accounts**, then choose **Import Accounts**.
For CSV, select **Download template**, keep the header row unchanged, and
add one account per row. For JSON, export a configuration file from the
source team.
Upload the CSV or JSON file. Sendmux shows the accepted rows before it
starts. CSV files also show any invalid rows, which are not imported.
Select **Import**. You can close the tab while the import continues, then
return to **Accounts** > **Import Progress** to check the result.
New accounts count towards your team's sending account limit. Updating an
existing account does not. Only one import can run for a team at a time.
JSON configuration files never contain or accept passwords or connected-account
credentials. Use them to update matched accounts. To create a new SMTP account,
use **Add Account** or a CSV with its password. Use **Add Account** to authorise
a new Gmail or Outlook account.
The downloaded template uses these headers:
```csv theme={null}
name,type,group_name,host,port,protocol,username,password,status,oauth_user_email,from_email,from_name,reply_to_name,reply_to_email,tracking_domain,quota_second,quota_minute,quota_hour,quota_day,percentage
```
| Header | Required | Accepted value |
| --------------------------------------------------------- | ---------------------------- | -------------------------------------------------------------------------------------------- |
| `name` | Every row | Account name. |
| `type` | No | `smtp` (default), `gmail_api`, or `outlook_api`. |
| `group_name` | No | Delivery group name. Sendmux creates the group if it does not exist, then adds the account. |
| `host` or `smtp_host` | New SMTP account | Public SMTP hostname. |
| `port` or `smtp_port` | New SMTP account | `25`, `465`, `587`, or `2525`. |
| `protocol` or `smtp_protocol` | New SMTP account | `plain`, `none`, `ssl`, `tls`, or `starttls`. |
| `username` or `smtp_username` | New SMTP account | SMTP username. |
| `password` or `smtp_password` | New SMTP account | SMTP password. Exports leave this blank. A blank value on update keeps the current password. |
| `status` | No | `active` or `inactive`. New SMTP accounts default to `active`. |
| `oauth_user_email` | New Gmail or Outlook account | Email address used to match the account. A new imported account remains pending. |
| `from_email`, `from_name` | No | Default sender address and display name. |
| `reply_to_email`, `reply_to_name` | No | Default reply-to address and display name. |
| `tracking_domain` | No | Custom tracking hostname. |
| `quota_second`, `quota_minute`, `quota_hour`, `quota_day` | No | `0` for unlimited, one number, or a range such as `5-10`, up to `100000000`. |
| `percentage` | No | Routing weight from `0` to `100`. Defaults to `100`. |
Header names are case-insensitive. The shorter SMTP headers in the template
and their `smtp_`-prefixed alternatives are both accepted.
Sendmux checks Gmail and Outlook accounts by type and `oauth_user_email`,
SMTP accounts by host and username, then a unique account name with the
same type. Blank optional cells do not clear existing values.
An import is not all-or-nothing. Review the created, updated, and failed
totals, correct any failed rows, then import those rows again.
## Export or change accounts in bulk
* Select **Accounts** > **Export accounts as CSV** for a spreadsheet-safe copy.
Formula-like values are written as text, so a leading apostrophe may appear.
* Select **Accounts** > **Export accounts as JSON** to preserve supported
non-secret values exactly in a versioned configuration file. Version `1` is
currently supported. Files with another version or unknown fields are rejected.
* Passwords and connected-account credentials are never included in either
export. CSV keeps its password column blank. JSON omits credential fields.
* Search or filter by status, group, or type, then select accounts to activate, deactivate, update quotas, update tracking, or delete them.
## Monitor account health
Search by account details or filter by status, group, and type. Each row shows
throughput, recent delivery health, status, and last use. Status can be active,
inactive, pending, or error. When available, the error reason appears below the
account name. Open an SMTP account's menu and select **Test connection** before
routing production mail through it.
## Get sending credentials
Select **Setup** to generate a sending key and copy the current SMTP and HTTP
connection details.
## Manage accounts by API
Use the [Management API](/docs/api/introduction#sending-account-management) when you need to automate account operations.
| Task | Endpoint |
| --------------------------------------------- | ---------------------------------------------------------------------------------- |
| List accounts | `GET /providers` |
| Add a custom SMTP account | `POST /providers` |
| Update account metadata or SMTP settings | `PATCH /providers/{public_id}` |
| Activate or deactivate an account | `POST /providers/{public_id}/activate` or `POST /providers/{public_id}/deactivate` |
| Test a custom SMTP account | `POST /providers/{public_id}/test` |
| Read usage and limits | `GET /providers/usage`, `GET /providers/limits` |
| Request more custom-account capacity | `POST /providers/limits/sending-accounts/request-increase` |
| Request shared Amazon SES daily limit review | `POST /providers/shared-amazon-ses-limit-request` |
| Cancel a pending shared-account limit request | `DELETE /providers/shared-amazon-ses-limit-request/{request_id}` |
Connected account setup still starts in the Sendmux app. After connection, the API can read, activate, deactivate, delete, and update safe account metadata.
The shared Amazon SES account is platform-managed. API clients can read it,
activate or deactivate it, and request a daily limit increase. They cannot
edit its credentials, quotas, routing weight, sender defaults, or delete it.
## Advanced settings
Advanced settings let you tune the provider without changing every send request.
| Setting | Use it for |
| --------------------------- | ------------------------------------------------------------------------------ |
| **From email** | Set a default sender address for this provider. |
| **From name** | Set a default sender display name. |
| **Reply-To** | Send replies to a different mailbox. |
| **Tracking domain** | Rewrite eligible links through a custom tracking hostname. |
| **Quotas** | Set per-second, per-minute, per-hour, or per-day caps on custom SMTP accounts. |
| **Distribution percentage** | Weight traffic when several providers are eligible. |
| **Delivery group** | Add the provider to a routing group. |
## Account limits
Each team starts with **200 sending accounts** that you add yourself. The managed account does not count towards this limit. When usage reaches 80%, **Request increase** appears on **Accounts**, and API clients can call `POST /providers/limits/sending-accounts/request-increase`.
## Related guides
Group providers and route selected keys or mailboxes through them.
See what the coming-soon provider type means.
Verify custom domains before using them for branded sending.
Watch bounce, complaint, and provider health signals.