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

# Connect your turboSMTP account

> Connect your sending provider and create separate Spitzli Cloud Mail API keys.

turboSMTP bills your own account and applies its own sending limits. Spitzli Cloud manages the enabled workspace connection, sender domains and Mail API access.

> [!NOTE]
>
> Turbo BYOK requires separate operator activation, provider configuration and a ready sending path. Native activation remains separate release work. A connection form or verified provider key alone does not establish production sending availability.

## Prepare the credentials

| Credential | Where to use it |
| - | - |
| turboSMTP Consumer Key and Consumer Secret | Protected provider connection form |
| Spitzli Cloud Mail API key | Your server-side application |
| Webhook signing secret | Your event receiver |

Provider credentials cannot be used as Spitzli Cloud Mail bearer keys. Use a dedicated customer account because its sender-domain inventory is visible through the connection. Create a Consumer key with `SEND_API` and `APIS` permissions.

**1. Confirm access**

Ask your operator to confirm own-account sending, the sender-domain allowance and production dispatch availability.

**2. Connect the account**

Where activated, open **Mail settings → Mail API → Connect your turboSMTP account**. Enter the provider credentials and select **Verify and save account**. Credentials are stored encrypted.

**3. Verify the sender**

Add or select the intended sender domain. Publish the exact DNS records shown and refresh verification.

**4. Create an application key**

Choose the ready Mail connection and create a Spitzli Cloud sending key restricted to the needed domain. Follow the [Mail quickstart](https://docs.spitzli.cloud/developers/mail-quickstart.md).

The older **Own sending connection** form manages the provider account and sender-domain inventory. It does not by itself create a selectable Mail API connection.

## Pause, recover and disconnect

Pausing blocks new sends while retaining history and accepted work. If domain registration times out, refresh the existing registration before trying again. An uncertain registration or changed account identity can require operator review.

Disconnecting through own-account setup removes its stored credential. Separately retained Mail connection credentials and history can remain. Your turboSMTP account and domains are not deleted. Revoke the provider key at turboSMTP when all use of that key must end.

## Incoming Mail is separate

Sending-only does not require a mailbox server. Incoming mailboxes or forwarding require explicit activation. Workspaces with native incoming Mail need a compatible native sending path; do not assume the expanded Mail API sends through the mailbox server.

Check dispatch and callback readiness for the selected connection. Provider acceptance is not delivery. EU sending endpoints do not establish that every provider control-plane service is EU-only.


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