Skip to main content
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

Send Email

Send plain-text or HTML email with attachments and campaign identifiers.

Authentication

Use Consumer credentials and understand session-only exceptions.

Suppressions

Filter, import, export, and remove suppressed addresses.

Analytics

Retrieve message records, export CSV, and configure tracking.

Email Validation

Validate an address or upload, start, and retrieve a batch validation.

Sub-Accounts

Manage sub-accounts, limits, account status, and white-label settings.

Alerts

Receive an email when daily credit usage reaches a threshold.

Consumer Keys

Create, list, update, and revoke application credentials.

Hosts and authentication

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 explains these exceptions and the current limitation of legacy /authorize login.
Read analytics
See base URLs and SMTP settings 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 for available libraries and release status. The OpenAPI specification describes the public v2 contract. The endpoint pages include additional supported operations and compatibility details.