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

# turboSMTP REST API v2 Reference

> Send email, retrieve delivery analytics, manage suppressions and sub-accounts, and validate email lists through turboSMTP's REST API v2.

Use the turboSMTP REST API to send messages and manage your email integration. Start by creating a Consumer Key / Secret pair with the permissions your application needs, then use the host for the operation you want to call.

## API reference

> [card] [Send Email](/docs/api-reference/send-email.md)
>
> Send plain-text or HTML email with attachments and campaign identifiers.

> [card] [Authentication](/docs/api-reference/authentication.md)
>
> Use Consumer credentials and understand session-only exceptions.

> [card] [Suppressions](/docs/api-reference/suppressions.md)
>
> Filter, import, export, and remove suppressed addresses.

> [card] [Analytics](/docs/api-reference/analytics.md)
>
> Retrieve message records, export CSV, and configure tracking.

> [card] [Email Validation](/docs/api-reference/email-validation.md)
>
> Validate an address or upload, start, and retrieve a batch validation.

> [card] [Sub-Accounts](/docs/api-reference/subaccounts.md)
>
> Manage sub-accounts, limits, account status, and white-label settings.

> [card] [Alerts](/docs/api-reference/alerts.md)
>
> Receive an email when daily credit usage reaches a threshold.

> [card] [Consumer Keys](/docs/api-reference/consumer-keys.md)
>
> Create, list, update, and revoke application credentials.

## Hosts and authentication

| Base URL | Operations |
| - | - |
| `https://pro.api.serversmtp.com/api/v2` | Management API |
| `https://api.turbo-smtp.com/api/v2` | `POST /mail/send`, global |
| `https://api.eu.turbo-smtp.com/api/v2` | `POST /mail/send`, EU |

Both Consumer headers are required for sending. Management operations generally accept the same pair with **Statistics & Management APIs** (`APIS`) enabled. Consumer-key management and password changes require a session API key instead. The [authentication guide](/docs/api-reference/authentication.md) explains these exceptions and the current limitation of legacy `/authorize` login.

```bash Read analytics theme={"system"}
curl --get 'https://pro.api.serversmtp.com/api/v2/analytics' \
  -H 'consumerKey: YOUR_CONSUMER_KEY' \
  -H 'consumerSecret: YOUR_CONSUMER_SECRET' \
  --data-urlencode 'from=2026-10-01' \
  --data-urlencode 'to=2026-10-27'
```

See [base URLs and SMTP settings](/docs/api-reference/base-urls.md) for global and EU hosts. turboSMTP is an Italian company with European sending infrastructure.

## Request and response formats

Use `Content-Type: application/json` when sending a JSON body. Some operations use multipart file uploads, and CSV exports return CSV rather than JSON. Check each endpoint's format before copying an example.

Analytics and suppressions use date filters in `YYYY-MM-DD` format. Send recipients as comma-separated strings in `to`, `cc`, and `bcc`; attachments are an array of objects. List endpoints commonly return an object containing `count` and `results`, rather than a bare array.

## SDKs and specification

See the [SDK guide](/docs/integrations/sdks.md) for available libraries and release status. The [OpenAPI specification](https://serversmtp.com/turbo-api/turbo-smtp.yaml) describes the public v2 contract. The endpoint pages include additional supported operations and compatibility details.


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