> ## 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 Qubrics uses to deliver email.

Every team can send as soon as it is created. Qubrics 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 | Free | Pro |
| - | - | - |
| Hourly sending limit | 2 accepted recipients | No Qubrics speed cap |
| Starting daily limit | 50 accepted recipients | 1,000 accepted recipients |
| Daily reset | 00:00 UTC | 00:00 UTC |
| Setup | None | None |
| Editable credentials | No | No |
| Delivery groups | Not supported | Not supported |

> [!WARNING]
>
> Managed Amazon SES is for transactional email only. Use your own provider for
> marketing, newsletters, or bulk promotional sends.

Pro managed sending has no per-second, per-minute or per-hour Qubrics speed cap, and your team's current daily allowance still applies, including approved increases. Managed sends share Amazon SES account and regional sending limits.

Free managed-sending limits are fixed. Upgrade to Pro for more capacity. On Pro, **Request increase** appears on **Accounts** at 80% of the managed Amazon SES daily limit. You can also call `POST /providers/shared-amazon-ses-limit-request` from the Management API. Submit the request once; Qubrics reviews it and emails the outcome.

> [!WARNING]
>
> 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.

Your own providers on Pro and Enterprise have no Qubrics sending caps. Provider limits and any quotas you configure still apply.

**1. Open Accounts**

Open **Accounts** and select **Add Account**.

**2. Choose the provider type**

Choose **Custom SMTP**, **Gmail**, or **Outlook / Microsoft 365**. **HTTP
API** is visible as a coming-soon option.

**3. Complete setup**

SMTP accounts need server address, port, protocol, username, password, and
optional sender defaults. Connected accounts send you through the provider's
sign-in flow. See [Google and Microsoft
setup](https://sendmux.ai/docs/sending/accounts/google-microsoft.md) for administrator preparation,
permissions, and large account pools.

**4. Test the provider**

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 Qubrics JSON
configuration file to transfer supported non-secret values without spreadsheet
formatting.

**1. Open the importer**

Open **Accounts**, select **Accounts**, then choose **Import Accounts**.

**2. Choose the file format**

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.

**3. Review the rows**

Upload the CSV or JSON file. Qubrics shows the accepted rows before it
starts. CSV files also show any invalid rows, which are not imported.

**4. Start the import**

Select **Import**. You can close the tab while the import continues, then
return to **Accounts** > **Import Progress** to check the result.

> [!NOTE]
>
> 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.

> [!WARNING]
>
> 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, or import its account
> record and select **Authorise** from the pending account row.

> [accordion] CSV column reference
>
> 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. Qubrics 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 | Sender address applied to every message sent through this account, and the display name used when a message has none. `from_email` applies only to SMTP accounts; connected accounts use `oauth_user_email`. |
> | `reply_to_email`, `reply_to_name` | No | Reply-To address applied to every message sent through this account, and the display name used when a message's Reply-To has none. |
> | `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.

> [accordion] How updates are matched
>
> Qubrics 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. Select the visible page, every
  matching account, or all accounts, then activate, deactivate, update quotas,
  update tracking, change groups, update variables, or delete the selection.
  Use the **Accounts** menu to export all custom accounts. Large changes
  continue in the background and show completed and failed account counts.

## 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](https://sendmux.ai/docs/api/introduction.md#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 Qubrics app. After connection, the API can read, activate, deactivate, delete, and update safe account metadata.

> [!WARNING]
>
> The shared Amazon SES account is managed by the platform. API clients can
> read it, activate or deactivate it, and request a daily limit review for an
> eligible Pro team. They cannot edit its credentials, quotas,
> routing weight, or sender defaults, and cannot delete it. You can edit its
> template variables. Free limits are fixed.

## Advanced settings

Advanced settings let you tune the provider without changing every send request.

| Setting | Use it for |
| - | - |
| **From email** | Replace the sender address on every message sent through this SMTP provider. |
| **From name** | Set the sender display name used when a message has none. |
| **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. |

## Template variables

Edit an account's **Variables** to store values such as `signature_url`. Insert `[DP_VAR_SIGNATURE_URL]` into a subject or body to use the value from the provider selected for that message.

To edit several accounts, select them and open **Update Variables**. Choose
**Add or update** to add supplied keys and overwrite matching keys, **Replace
all** to replace each map, or **Remove** to delete named keys. Select **Apply
changes** to start the update. Each resulting map must satisfy the limits.
Review any reported failures after applying the edit.

See [Template variables](https://sendmux.ai/docs/sending/template-variables.md) for the key rule, value limits, built-in tags, raw insertion behaviour, and Management API examples.

## Account limits

| Plan | Your own sending accounts | More capacity |
| - | - | - |
| Free | 1; the managed account does not count | Delete an account or upgrade to Pro |
| Pro | Unlimited\*, subject to fair usage. The app shows your current allowance. | Request an increase at 80% usage for Qubrics admin approval. |

## Related guides

> [card] [Google and Microsoft setup](https://sendmux.ai/docs/sending/accounts/google-microsoft.md)
>
> Prepare administrator access and authorise connected accounts at scale.

> [card] [Delivery groups](https://sendmux.ai/docs/sending/accounts/delivery-groups.md)
>
> Group providers and route selected keys or mailboxes through them.

> [card] [HTTP provider](https://sendmux.ai/docs/sending/accounts/http-provider.md)
>
> See what the coming-soon provider type means.

> [card] [Domains](https://sendmux.ai/docs/domains.md)
>
> Verify custom domains before using them for branded sending.

> [card] [Deliverability](https://sendmux.ai/docs/monitoring/deliverability.md)
>
> Watch bounce, complaint, and provider health signals.

> [card] [Cold email outreach](https://sendmux.ai/docs/use-cases/cold-email-outreach.md)
>
> Set up a pool of your own inboxes for outreach and GTM.


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