---
title: "Send MIME email"
method: POST
path: "/email/4/mime"
tags: ["channels", "email", "email-message-sending"]
---

# Send MIME email

`POST /email/4/mime`

## Request

- Base URL: `https://api.infobip.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.infobip.com/email/4/mime`
- Auth: one of:
  - OAuth 2
    - Client credentials
    - Token URL: `https://api.infobip.com/auth/1/oauth2/token`
  - API key in header `Authorization`
  - API key in header `Authorization`
  - HTTP basic

Send an email where you can specify the content as MIME message.

## Request body

- 34438aa163eb13a2a06ad96ae98170e41cc2ee8902e8b7655aba73ceb0bb23f1SendMimeRequestSchema
  - `messageId` string: The ID that uniquely identifies the message sent to a recipient.
  - `bulkId` string: The ID that uniquely identifies the sent bulk. This filter will enable you to query delivery reports for all the messages using just one request. You will receive a `bulkId` in the response after sending an email request. If you don't set your own `bulkId`, unique ID will be generated by our system and returned in the API response. (Optional Field)")
  - `from` string: The email address specified in this field takes precedence over the From header in the MIME message. If you leave this field empty, the From address in the MIME message will be used instead. If you provide both values and they are different, their domains must match at the organizational level; otherwise, the request will be rejected.
  - `destinations` string[]: A list of recipient email addresses. <br/> The email addresses specified in this field takes precedence over the To, CC, and BCC headers in the MIME message. Only the addresses in this list will receive the final email. If you leave this field empty, To, CC, and BCC headers in the MIME message will be used instead. <br/> Note: Maximum number of recipients per request is 1000 overall including to, cc and bcc field.
  - `mimeMessage` string, required: This field accepts a complete email message serialized in the MIME format, conforming to RFC 5322 and MIME-related standards (RFCs 2045–2047, RFC 2183). The MIME message must be correctly constructed per the following requirements as if it were being sent via traditional SMTP. The entire MIME message (including headers and body) must be `base64-encoded` before being sent. <br/><br/> When using this field, these are the requirements: <br/> **-** The message must consist of a set of header fields, followed by a blank line (CRLF), and then the message body <br/> **-** All required and optional fields must be properly formatted with header-name, colon, and header-value <br/> **-** If any MIME part contains non-7-bit-ASCII data (e.g., UTF-8 text, binaries), that part must be encoded <br/> **-** If your message uses multipart content (attachments, alternative bodies, etc.), each MIME part must contain `Content-Type` header. For encoded parts, include `Content-Transfer-Encoding`. For attachments, include a valid `Content-Disposition`. <br/><br/> We also support specifying additional headers in your MIME message, such as `List-Unsubscribe`, `List-Unsubscribe-Post`, `In-Reply-To`, `References` and `Message-ID`.
  - `intermediateReport` boolean: The real-time Intermediate delivery report that will be sent on your callback server.
  - `notifyUrl` string: The URL on your callback server on which the Delivery report will be sent.
  - `notifyContentType` string: Preferred Delivery report content type. Can be `application/json` or `application/xml`.
  - `callbackData` string: Additional client data that will be sent on the notifyUrl.
  - `trackingUrl` string: The URL on your callback server on which the open and click notifications will be sent. See [Tracking Notifications](https://www.infobip.com/docs/email/email-over-api/tracking-notifications) for details.
  - `clientPriority` string: Adds a priority rating to this email message. Allowed values are `HIGH`, `STANDARD` and `LOW`. Messages with a higher priority value sent by your account are prioritized over messages with a lower priority value sent by your account. If no priority value is provided, messages will be treated with `STANDARD` priority by default.
  - `applicationId` string: Required for application use in a send request for outbound traffic. Returned in notification events.
  - `entityId` string: Required for entity use in a send request for outbound traffic. Returned in notification events.

## Response `200`

Successful Request

- 34438aa163eb13a2a06ad96ae98170e41cc2ee8902e8b7655aba73ceb0bb23f1SendResponse
  - `bulkId` string: The ID that uniquely identifies a list of message responses.
  - `messages` 34438aa163eb13a2a06ad96ae98170e41cc2ee8902e8b7655aba73ceb0bb23f1ResponseDetails[], required: List of message response details.
    - `to` string, required: The destination address of the message.
    - `messageId` string, required: The ID that uniquely identifies a message response.
    - `status` 34438aa163eb13a2a06ad96ae98170e41cc2ee8902e8b7655aba73ceb0bb23f1SingleMessageStatus, required: Indicates the message status.
      - `groupId` integer, required: Status group ID.
      - `groupName` string, required: Status group name.
      - `id` integer, required: Status ID.
      - `name` string, required: Status name.
      - `description` string, required: Status description.

## Other responses

- `400`: Bad Request
- `401`: Unauthorized
- `403`: Forbidden
- `429`: Too Many Requests
- `500`: Internal Server Error

---

[API](https://skmtc.dev/infobip/apis/infobip-openapi-specification.md) - [All operations](https://skmtc.dev/infobip/apis/infobip-openapi-specification/llms.txt) - [OpenAPI document](https://skmtc.dev/infobip/apis/infobip-openapi-specification/revisions/9dcbbaf902de?raw)