---
title: "Send an MMS"
method: GET
path: "/mms/"
tags: ["SMS"]
---

# Send an MMS

`GET /mms/`

## Request

- Base URL: `http://api.smsfusion.com.au`
- URL: `http://api.smsfusion.com.au/mms/`
- Auth: one of:
  - API key in query parameter `key`
  - HTTP basic

Send a single MMS to a single number. Subject, message and attachments combined must be non-empty and at most 300,000 bytes. Attachments are hashes of images already uploaded through the account's MMS attachment upload flow. Unlike /sms/, validity is in hours (default 24) and the failure key in the response is an object, not an array

## Query parameters

- `key` string, required
- `num` string, required
- `msg` string
- `subject` string
- `attachment0` string
- `from` string
- `cc` string, string
- `deliverby` string
- `dlrcb` string
- `replycb` string
- `replyemail` string
- `validity` integer
- `messagepos` integer

## Response `200`

Queued. {id, success, cost, count}; on partial failure adds failure as an OBJECT keyed by stringified index

## Other responses

- `401`: FIELD_EMPTY (num missing), OVER_LIMIT (more than one number), FROM ERROR, ATTACHMENT ERROR, or SIZE ERROR
- `429`: OVER_LIMIT - insufficient funds (same reason phrase as the 401 multi-number case; distinguish by status code)

---

[API](https://skmtc.dev/smsfusion/apis/sms-fusion-api.md) · [All operations](https://skmtc.dev/smsfusion/apis/sms-fusion-api/llms.txt) · [OpenAPI document](https://skmtc.dev/smsfusion/apis/sms-fusion-api/revisions/a88b2793a6e9?raw)