Sending MMS messages using HTTP
The MX Telecom MMS Server allows MMS messages to be sent over HTTP. This page details the format of the HTTP requests that may be made.
Sending an MMS using HTTP GET or Multipart POST
To send an MMS through the MXTelecom MMS gateway, an HTTP GET or Multipart POST may be made using the structure detailed below to one of the following endpoints:
| HTTP | HTTPS (SSL) |
http://mms.mxtelecom.com/SendMMS | https://mms.mxtelecom.com/SendMMS |
Parameters for all requests
| Name | Description |
| user | Username of the account to use |
| pass | Password |
| to | To recipient, this should be in international format e.g. 447700900999 |
| from | From field, this should be a valid MSISDN in international format e.g. 447700900999 |
| *subject | Subject field of MMS |
| *note | Note that will be stored in the billing record (maximum 160 characters) |
| *subaccount | Sub account that will be stored in the billing record (maximum 10 characters) |
| *deliveryreport | Set to true if delivery reports should be delivered to a url |
| *readreport | Set to true if read reports should be delivered to a url |
* these parameters are optional
Parameters for GET requests
| Name | Description |
| url | URLEncoded URL to zipped MMS contents |
The following is an example of the common structure of all HTTP GET requests made to send MMSes:
http://mms.mxtelecom.com/SendMMS?user=myUsername&pass=myPass&to=447700900999&from=447700900999&subject=mySubject&url=http%3A%2F%2Fwww.mycompany.com%2Fmyzip.zip
Note that the url paramter above was url encoded, e.g. http://www.mycompany.com/myzip.zip becomes http%3A%2F%2Fwww.myCompany.com%2Fmyzip.zip
Parameters for Multipart POST requests
| Name | Description |
| mms.zip | Zipped MMS contents |
Note that the url parameter may also be used in a multipart post instead of the mms.zip parameter.
Response to requests
On receipt of a successful request, a 200 result code will be returned with the contents being the id of the sent mms.
If a request is unsuccesful because it has been rejected by our gateway, a 403 response will be returned. The first line of the response will be a plain text reason for this, the second will be a numeric id that corresponds to the error. The meanings of these codes is outlined below:
| Code | Description |
| 1 | An configuration error has occurred - please report to support@mxtelecom.com |
| 2 | An error occurred while processing your request - please try again |
| 3 | Could not contact MX Telecom Server |
| 4 | A parameter is missing from the request |
| 5 | Error in request parameters |
| 6 | A SQLException has occurred - please report to support@mxtelecom.com |
| 8 | Username/Password incorrect |
| 9 | Maximum requests per day for that user hit |
| 10 | Maximum requests per month hit |
| 11 | MMS not allowed for user |
| 12 | IP not allowed |
| 13 | An internal error has occurred - please report to support@mxtelecom.com |
| 14 | Destination fields contain duplicates |
| 15 | Prepay Credit limit exceeded |
| 18 | From field has invalid format |
Internet Explorer users
Unfortunately, due to Internet Explorer's handling of error pages, it is likely that
Internet Explorer will replace the error message the server returns with its own 403 error
message. To see the page that our server returns, you will need to turn off these 'Friendly error messages'.
To do this, click on the Tools Menu, Internet Options, Advanced Tab, Uncheck Show Friendly HTTP error messages.
![]() |
About MX TelecomMX Telecom is a leader in wireless technology. MX Telecom offers an easily accessible gateway to data, voice and video messaging services including 2-way and premium SMS, multimedia messaging, interactive voice response, location-based services, video short codes, Internet and TV related solutions. For more information, MX Telecom can be reached on 0845 666 7778, or via email at sales@mxtelecom.com. |


