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

Last Updated: Friday, January 26, 2018



The Message Bundle Services provide mechanisms to submit multiple messages and message lists for delivery, as well as to query the status of previously submitted bundles. The submitMessageBundle is a convenience method used to submit a small number of related messages together in a single Application Program Interface (API) call, rather than making individual API calls. All of the messages will also be tagged with the bundleId for later identification of the messages that were grouped together.

Topics in this Section



Note: The submitMessageBundle is a convenience method to associate a small number of related messages together. It is not intended to serve as a bulk message submission, or to replace individual API calls to submitMessage. The messageBundles are capped at a maximum of 100 messages. In most optimized cases, API consumers will see better throughput and performance by submitting messages individually rather than incurring the transactional cost of submitting the messages via a bundle.

 

Service

URI

HTTP Parameters

Comments

submitMessageBundle

/MessageApi/mt/messageBundles

POST:

Submits a new Mobile Terminated (MT) Message Bundle for delivery.

getMessageBundle

/MessageApi/mt/messageBundles/<messageBundleId>

GET:

Retrieve the details on a message bundle.

  • No labels