---
title: "Send email message"
method: POST
path: "/mail/send"
tags: ["mail"]
---

# Send email message

`POST /mail/send`

Send email message

###### Servers

| Host | Region |
|---|---|
| `https://api.turbo-smtp.com/api/v2` | Global (default) |
| `https://api.eu.turbo-smtp.com/api/v2` | European infrastructure — use for EU data residency |

###### **Notes:**
**- ConsumerKey / ConsumerSecret headers should be used. This endpoint does not support Authorization header**

**- Switch between samples to learn about advanced features such as using attachments, custom headers like reply-to address, tracking, embeded images and others.**

###### Limitations:
    
* The total size of your email, including attachments, must be less than 24MB.

## Request body

- Email2
  - `from` string, required — Sender information using either: - Email only format (user@example.com) - Display name with email (Name <user@example.com>)
  - `to` string, required — comma-separated recipients emails list
  - `subject` string, nullable — email subject
  - `cc` string, nullable — comma-separated copy emails list
  - `bcc` string, nullable — comma-separated hidden copy emails list
  - `content` string, nullable — text content of the email
  - `html_content` string, nullable — html content of the email
  - `custom_headers` object, nullable — email additional headers, use any additional header like standard ones List-Unsubscribe (to allow users to easily unsubscribe), X-Entity-Ref-ID (to handle how gmail and other clients group threads), and your own ones.
  - `reference_id` string, nullable — custom argument included within an email to be added to the Event Webhook response.
  - `X-campaign-ID` string, nullable — custom argument included within an email identify the campaign the email belongs to.
  - `mime_raw` string, nullable — mime message which replaces content and hmtl content
  - `attachments` Attachment[] — array of attachment objects
    - `content` string — Base64 encoded content of the attachment
    - `content_id` string — Content ID for referencing embedded images via CID in HTML content. Valid formats include: - UUID (e.g. "550e8400-e29b-41d4-a716-446655440000") - Timestamp + suffix (e.g. "20231012-abc123") - Simple incremental ID (e.g. "1") - Base64 encoded string (e.g. "c29tZV91bmlxdWUfaWQ=") - Custom format (e.g. "img_001_2023")
    - `name` string — filename of the attachment
    - `type` string — mime type of the content you are attaching

## Response `200`

Sucess

Turbo-SMTP successfully received your message.

- SendSucessResponsetBody
  - `message` string
  - `mid` integer — message ID

## Other responses

- `400` — Bad Request There was a problem processing the request due to an invalid/missing parameter for the request.
- `401` — Unauthorized Missing or Invalid Turbo-SMTP credentials provided.

---

[API](https://skmtc.net/serversmtp/apis/turbosmtp-public-apis.md) · [All operations](https://skmtc.net/serversmtp/apis/turbosmtp-public-apis/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/serversmtp/turbosmtp-public-apis/versions/8503e099b215/schema)