WE'RE MOVING! Check out our new Vibes Developer Hub for Aggregation. Please note that this page will no longer be available starting January 13, 2023.
Skip to end of metadata
Go to start of metadata

API Overview

Vibes Multimedia Message Service (MMS) Application Program Interfaces (APIs) are currently offered via an implementation of the MM7 protocol with some additional customer header extensions to accommodate features and optimizations beyond the basic protocol.

Topics in this Section


MM7 is the standard protocol used by the carriers to send and receive MMS messages. It is a SOAP-based protocol sent over HTTP. The basic tenants of the protocol are the SubmitReq action, used to send a Mobile Terminated (MT) Message to a device, and the DeliverReq to receive an Mobile Originated (MO) message from the device.

The Vibes MMSC implements this standard and extends it with some custom headers. One of the largest variations is the utilization of Authentication, which is outlined in detail in the following section.


The standard MM7 specification has the user credentials Value Added Service Provider Identifier (VASPID) specified within the body of the XML document, which is not ideal from an implementation nor security perspective. This requires unmarshalling the XML body prior to authentication as well as includes credentials in the message body, risking it being accessed or exposed inadvertently.

Instead, Vibes utilizes the HTTP Basic Authorization header to authenticate submitting messages. Details are specified in the specific SubmitReq call.


Below are the MM7 Versions the Vibes Multimedia Message Service Center (MMSC) supports. Since its an XML-based protocol, we have also provided links to the schema files used for each version.


More details regarding the many versions of MM7 can be found in Specification 23.140. Identified limitations can be found on our Known Issues page.

Throughout the Vibes MMSC documentation, specifications and sample code will be provided for each supported MM7 version.
You don't have to support every version, you just have to pick one and then use that schema to format and parse your interactions with the Vibes MMSC.

Supported Requests

MM7 is comprised of a suite of requests and responses.
The following table lists the requests supported by the Vibes MMSC. 

SubmitReq (MT Messages)Customer submits a MT MMS message to Vibes for delivery to the carrier.https://messageapi-mms.vibesapps.com/mms/mm7/submit
DeliverReq (MO Messages)Customer receives a MO MMS message from Vibes (device).Provided by the client.
DeliveryReportReq (Delivery Receipts)Customer receives a Delivery report for a previously submitted MT MMS Message.Provided by the client.

  • No labels