# Sinch Messaging and Content APIs | Sinch

Send and receive MMS messages using the JSON API.

Version: 2.0
License: MIT

## Servers

```
https://api.ci.mblox.com/ep/v2
```

## Security

### ApiKey

Type: apiKey
In: header
Name: x-api-key

## Download OpenAPI description

[Sinch Messaging and Content APIs | Sinch](https://developers.sinch.com/_bundle/docs/mms/api-reference/mms.yaml)

## MMS

This API sends, saves, or sends a saved MMS defined in the JSON to a single mobile number. The sent or saved MMS may contain slides embedded with text, images, videos, audios, and/or other objects. Calls to the API are made in the form of HTTP requests using the POST request method with UTF-8 encoded JSON data passed inside the request body. All requests are expected to include a content-type HTTP header (for example, `Content-Type: application/json; charset=utf-8`).

**Important:**

Sinch will send an HTTP GET request to the server that is specified in the JSON slide of the embedded images, videos, audios, and/or other object URIs to retrieve the contents of the media file. The HTTP response header Sinch receives from the server MUST contain the `Content-Length` field indicating the size of the resource. Otherwise, the API request will fail. Customers using CDNs that employ chunked transfer encoding may run into problems in which the server returns a `Transfer-Encoding` field with a value of "chunked" specified in the HTTP GET response, rather than the server returning `Content-Length`. If a `Transfer-Encoding` field with a value of "chunked" is specified in an HTTP, the API request will be rejected.

**Important:**

All media files are expected to serve a valid content-type header (for example, text/plain, image/gif, audio/mp3, video/mp4, etc.). If a file server serves a file using the application/octet-stream content-type header instead, it may be rejected if the MIME type cannot be determined by other means.

### Send, save, or send a saved MMS

 - [POST /](https://developers.sinch.com/docs/mms/api-reference/mms/mms/mms.md): This request is used to send, save, or send a saved MMS message.