![\"Run](\"https://run.pstmn.io/button.svg\")
The Telstra Messaging API provides the features below.
| Feature | Description |
|---|---|
Dedicated Number | Provision a mobile number for your account to be used as from address in the API |
Send Messages | Sending SMS or MMS messages |
Receive Messages | Telstra will deliver messages sent to a dedicated number or to the notifyURL defined by you |
Broadcast Messages | Invoke a single API to send a message to a list of number provided in to |
Delivery Status | Query the delivery status of your messages |
Callbacks | Provide a notification URL and Telstra will notify your app when messages status changes |
Alphanumeric Identifier | Differentiate yourself by providing an alphanumeric string in from. This feature is only available on paid plans |
Concatenation | Send messages up to 1900 characters long and Telstra will automaticaly segment and reassemble them |
Reply Request | Create a chat session by associating messageId and to number to track responses received from a mobile number. We will store this association for 8 days |
Character set | Accepts all Unicode characters as part of UTF-8 |
Bounce-back response | See if your SMS hits an unreachable or unallocated number (Australia Only) |
Queuing | Messaging API will automatically queue and deliver each message at a compliant rate. |
Emoji Encoding | The API supports the encoding of the full range of emojis. Emojis in the reply messages will be in their UTF-8 format. |
Client key and Client secret as these will be needed to provision a number for your application and for authentication. Now head over to Getting Started where you can find a postman collection as well as some links to sample apps and SDKs to get you started.
Happy Messaging! # Getting Started
Below are the steps to get started with the Telstra Messaging API.
Client key and Client secret.
notifyURL, when the message has been delivered the API will make a call to this URL to advise of the message status. If this is not provided then you can make use the Get Replies API to poll for messages.GET /sms API get the latest replies to the message.{ to: '+61418123456' sentTimestamp: '2017-03-17T10:05:22+10:00' receivedTimestamp: '2017-03-17T10:05:23+10:00' messageId: /cccb284200035236000000000ee9d074019e0301/1261418123456 deliveryStatus: DELIVRD } | Field | Description |
|---|---|
to | The number the message was sent to. |
receivedTimestamp | Time the message was sent to the API. |
sentTimestamp | Time handling of the message ended. |
deliveryStatus | The final state of the message. |
messageId | The same reference that was returned when the original message was sent. |
receivedTimestamp | Time the message was sent to the API. |
{ \"status\": \"RECEIVED\" \"destinationAddress\": \"+61418123456\" \"senderAddress\": \"+61421987654\" \"message\": \"Foo\" \"sentTimestamp\": \"2018-03-23T12:10:06+10:00\" } | Field | Description |
|---|---|
status | The final state of the message. |
destinationAddress | The number the message was sent to. |
senderAddress | The number the message was sent from. |
message | The sontent of the SMS reply. |
sentTimestamp | Time handling of the message ended. |
{ \"status\": \"RECEIVED\", \"destinationAddress\": \"+61418123456\", \"senderAddress\": \"+61421987654\", \"subject\": \"Foo\", \"sentTimestamp\": \"2018-03-23T12:15:45+10:00\", \"envelope\": \"string\", \"MMSContent\": [ { \"type\": \"application/smil\", \"filename\": \"smil.xml\", \"payload\": \"string\" }, { \"type\": \"image/jpeg\", \"filename\": \"sample.jpeg\", \"payload\": \"string\" } ] } | Field | Description |
|---|---|
status | The final state of the message. |
destinationAddress | The number the message was sent to. |
senderAddress | The number the message was sent from. |
subject | The subject assigned to the message. |
sentTimestamp | Time handling of the message ended. |
envelope | Information about about terminal type and originating operator. |
MMSContent | An array of the actual content of the reply message. |
type | The content type of the message. |
filename | The filename for the message content. |
payload | The content of the message. |
The Telstra Messaging API provides the features below.
| Feature | Description |
|---|---|
Dedicated Number | Provision a mobile number for your account to be used as from address in the API |
Send Messages | Sending SMS or MMS messages |
Receive Messages | Telstra will deliver messages sent to a dedicated number or to the notifyURL defined by you |
Broadcast Messages | Invoke a single API to send a message to a list of number provided in to |
Delivery Status | Query the delivery status of your messages |
Callbacks | Provide a notification URL and Telstra will notify your app when messages status changes |
Alphanumeric Identifier | Differentiate yourself by providing an alphanumeric string in from. This feature is only available on paid plans |
Concatenation | Send messages up to 1900 characters long and Telstra will automaticaly segment and reassemble them |
Reply Request | Create a chat session by associating messageId and to number to track responses received from a mobile number. We will store this association for 8 days |
Character set | Accepts all Unicode characters as part of UTF-8 |
Bounce-back response | See if your SMS hits an unreachable or unallocated number (Australia Only) |
Queuing | Messaging API will automatically queue and deliver each message at a compliant rate. |
Emoji Encoding | The API supports the encoding of the full range of emojis. Emojis in the reply messages will be in their UTF-8 format. |
Client key and Client secret as these will be needed to provision a number for your application and for authentication. Now head over to Getting Started where you can find a postman collection as well as some links to sample apps and SDKs to get you started.
Happy Messaging! # Getting Started
Below are the steps to get started with the Telstra Messaging API.
Client key and Client secret.
notifyURL, when the message has been delivered the API will make a call to this URL to advise of the message status. If this is not provided then you can make use the Get Replies API to poll for messages.GET /sms API get the latest replies to the message.{ to: '+61418123456' sentTimestamp: '2017-03-17T10:05:22+10:00' receivedTimestamp: '2017-03-17T10:05:23+10:00' messageId: /cccb284200035236000000000ee9d074019e0301/1261418123456 deliveryStatus: DELIVRD } | Field | Description |
|---|---|
to | The number the message was sent to. |
receivedTimestamp | Time the message was sent to the API. |
sentTimestamp | Time handling of the message ended. |
deliveryStatus | The final state of the message. |
messageId | The same reference that was returned when the original message was sent. |
receivedTimestamp | Time the message was sent to the API. |
{ \"status\": \"RECEIVED\" \"destinationAddress\": \"+61418123456\" \"senderAddress\": \"+61421987654\" \"message\": \"Foo\" \"sentTimestamp\": \"2018-03-23T12:10:06+10:00\" } | Field | Description |
|---|---|
status | The final state of the message. |
destinationAddress | The number the message was sent to. |
senderAddress | The number the message was sent from. |
message | The sontent of the SMS reply. |
sentTimestamp | Time handling of the message ended. |
{ \"status\": \"RECEIVED\", \"destinationAddress\": \"+61418123456\", \"senderAddress\": \"+61421987654\", \"subject\": \"Foo\", \"sentTimestamp\": \"2018-03-23T12:15:45+10:00\", \"envelope\": \"string\", \"MMSContent\": [ { \"type\": \"application/smil\", \"filename\": \"smil.xml\", \"payload\": \"string\" }, { \"type\": \"image/jpeg\", \"filename\": \"sample.jpeg\", \"payload\": \"string\" } ] } | Field | Description |
|---|---|
status | The final state of the message. |
destinationAddress | The number the message was sent to. |
senderAddress | The number the message was sent from. |
subject | The subject assigned to the message. |
sentTimestamp | Time handling of the message ended. |
envelope | Information about about terminal type and originating operator. |
MMSContent | An array of the actual content of the reply message. |
type | The content type of the message. |
filename | The filename for the message content. |
payload | The content of the message. |
The Telstra Messaging API provides the features below.
| Feature | Description |
|---|---|
Dedicated Number | Provision a mobile number for your account to be used as from address in the API |
Send Messages | Sending SMS or MMS messages |
Receive Messages | Telstra will deliver messages sent to a dedicated number or to the notifyURL defined by you |
Broadcast Messages | Invoke a single API to send a message to a list of number provided in to |
Delivery Status | Query the delivery status of your messages |
Callbacks | Provide a notification URL and Telstra will notify your app when messages status changes |
Alphanumeric Identifier | Differentiate yourself by providing an alphanumeric string in from. This feature is only available on paid plans |
Concatenation | Send messages up to 1900 characters long and Telstra will automaticaly segment and reassemble them |
Reply Request | Create a chat session by associating messageId and to number to track responses received from a mobile number. We will store this association for 8 days |
Character set | Accepts all Unicode characters as part of UTF-8 |
Bounce-back response | See if your SMS hits an unreachable or unallocated number (Australia Only) |
Queuing | Messaging API will automatically queue and deliver each message at a compliant rate. |
Emoji Encoding | The API supports the encoding of the full range of emojis. Emojis in the reply messages will be in their UTF-8 format. |
Client key and Client secret as these will be needed to provision a number for your application and for authentication. Now head over to Getting Started where you can find a postman collection as well as some links to sample apps and SDKs to get you started.
Happy Messaging! # Getting Started
Below are the steps to get started with the Telstra Messaging API.
Client key and Client secret.
notifyURL, when the message has been delivered the API will make a call to this URL to advise of the message status. If this is not provided then you can make use the Get Replies API to poll for messages.GET /sms API get the latest replies to the message.{ to: '+61418123456' sentTimestamp: '2017-03-17T10:05:22+10:00' receivedTimestamp: '2017-03-17T10:05:23+10:00' messageId: /cccb284200035236000000000ee9d074019e0301/1261418123456 deliveryStatus: DELIVRD } | Field | Description |
|---|---|
to | The number the message was sent to. |
receivedTimestamp | Time the message was sent to the API. |
sentTimestamp | Time handling of the message ended. |
deliveryStatus | The final state of the message. |
messageId | The same reference that was returned when the original message was sent. |
receivedTimestamp | Time the message was sent to the API. |
{ \"status\": \"RECEIVED\" \"destinationAddress\": \"+61418123456\" \"senderAddress\": \"+61421987654\" \"message\": \"Foo\" \"sentTimestamp\": \"2018-03-23T12:10:06+10:00\" } | Field | Description |
|---|---|
status | The final state of the message. |
destinationAddress | The number the message was sent to. |
senderAddress | The number the message was sent from. |
message | The sontent of the SMS reply. |
sentTimestamp | Time handling of the message ended. |
{ \"status\": \"RECEIVED\", \"destinationAddress\": \"+61418123456\", \"senderAddress\": \"+61421987654\", \"subject\": \"Foo\", \"sentTimestamp\": \"2018-03-23T12:15:45+10:00\", \"envelope\": \"string\", \"MMSContent\": [ { \"type\": \"application/smil\", \"filename\": \"smil.xml\", \"payload\": \"string\" }, { \"type\": \"image/jpeg\", \"filename\": \"sample.jpeg\", \"payload\": \"string\" } ] } | Field | Description |
|---|---|
status | The final state of the message. |
destinationAddress | The number the message was sent to. |
senderAddress | The number the message was sent from. |
subject | The subject assigned to the message. |
sentTimestamp | Time handling of the message ended. |
envelope | Information about about terminal type and originating operator. |
MMSContent | An array of the actual content of the reply message. |
type | The content type of the message. |
filename | The filename for the message content. |
payload | The content of the message. |
The Telstra Messaging API provides the features below.
| Feature | Description |
|---|---|
Dedicated Number | Provision a mobile number for your account to be used as from address in the API |
Send Messages | Sending SMS or MMS messages |
Receive Messages | Telstra will deliver messages sent to a dedicated number or to the notifyURL defined by you |
Broadcast Messages | Invoke a single API to send a message to a list of number provided in to |
Delivery Status | Query the delivery status of your messages |
Callbacks | Provide a notification URL and Telstra will notify your app when messages status changes |
Alphanumeric Identifier | Differentiate yourself by providing an alphanumeric string in from. This feature is only available on paid plans |
Concatenation | Send messages up to 1900 characters long and Telstra will automaticaly segment and reassemble them |
Reply Request | Create a chat session by associating messageId and to number to track responses received from a mobile number. We will store this association for 8 days |
Character set | Accepts all Unicode characters as part of UTF-8 |
Bounce-back response | See if your SMS hits an unreachable or unallocated number (Australia Only) |
Queuing | Messaging API will automatically queue and deliver each message at a compliant rate. |
Emoji Encoding | The API supports the encoding of the full range of emojis. Emojis in the reply messages will be in their UTF-8 format. |
Client key and Client secret as these will be needed to provision a number for your application and for authentication. Now head over to Getting Started where you can find a postman collection as well as some links to sample apps and SDKs to get you started.
Happy Messaging! # Getting Started
Below are the steps to get started with the Telstra Messaging API.
Client key and Client secret.
notifyURL, when the message has been delivered the API will make a call to this URL to advise of the message status. If this is not provided then you can make use the Get Replies API to poll for messages.GET /sms API get the latest replies to the message.{ to: '+61418123456' sentTimestamp: '2017-03-17T10:05:22+10:00' receivedTimestamp: '2017-03-17T10:05:23+10:00' messageId: /cccb284200035236000000000ee9d074019e0301/1261418123456 deliveryStatus: DELIVRD } | Field | Description |
|---|---|
to | The number the message was sent to. |
receivedTimestamp | Time the message was sent to the API. |
sentTimestamp | Time handling of the message ended. |
deliveryStatus | The final state of the message. |
messageId | The same reference that was returned when the original message was sent. |
receivedTimestamp | Time the message was sent to the API. |
{ \"status\": \"RECEIVED\" \"destinationAddress\": \"+61418123456\" \"senderAddress\": \"+61421987654\" \"message\": \"Foo\" \"sentTimestamp\": \"2018-03-23T12:10:06+10:00\" } | Field | Description |
|---|---|
status | The final state of the message. |
destinationAddress | The number the message was sent to. |
senderAddress | The number the message was sent from. |
message | The sontent of the SMS reply. |
sentTimestamp | Time handling of the message ended. |
{ \"status\": \"RECEIVED\", \"destinationAddress\": \"+61418123456\", \"senderAddress\": \"+61421987654\", \"subject\": \"Foo\", \"sentTimestamp\": \"2018-03-23T12:15:45+10:00\", \"envelope\": \"string\", \"MMSContent\": [ { \"type\": \"application/smil\", \"filename\": \"smil.xml\", \"payload\": \"string\" }, { \"type\": \"image/jpeg\", \"filename\": \"sample.jpeg\", \"payload\": \"string\" } ] } | Field | Description |
|---|---|
status | The final state of the message. |
destinationAddress | The number the message was sent to. |
senderAddress | The number the message was sent from. |
subject | The subject assigned to the message. |
sentTimestamp | Time handling of the message ended. |
envelope | Information about about terminal type and originating operator. |
MMSContent | An array of the actual content of the reply message. |
type | The content type of the message. |
filename | The filename for the message content. |
payload | The content of the message. |
The Telstra Messaging API provides the features below.
| Feature | Description |
|---|---|
Dedicated Number | Provision a mobile number for your account to be used as from address in the API |
Send Messages | Sending SMS or MMS messages |
Receive Messages | Telstra will deliver messages sent to a dedicated number or to the notifyURL defined by you |
Broadcast Messages | Invoke a single API to send a message to a list of number provided in to |
Delivery Status | Query the delivery status of your messages |
Callbacks | Provide a notification URL and Telstra will notify your app when messages status changes |
Alphanumeric Identifier | Differentiate yourself by providing an alphanumeric string in from. This feature is only available on paid plans |
Concatenation | Send messages up to 1900 characters long and Telstra will automaticaly segment and reassemble them |
Reply Request | Create a chat session by associating messageId and to number to track responses received from a mobile number. We will store this association for 8 days |
Character set | Accepts all Unicode characters as part of UTF-8 |
Bounce-back response | See if your SMS hits an unreachable or unallocated number (Australia Only) |
Queuing | Messaging API will automatically queue and deliver each message at a compliant rate. |
Emoji Encoding | The API supports the encoding of the full range of emojis. Emojis in the reply messages will be in their UTF-8 format. |
Client key and Client secret as these will be needed to provision a number for your application and for authentication. Now head over to Getting Started where you can find a postman collection as well as some links to sample apps and SDKs to get you started.
Happy Messaging! # Getting Started
Below are the steps to get started with the Telstra Messaging API.
Client key and Client secret.
notifyURL, when the message has been delivered the API will make a call to this URL to advise of the message status. If this is not provided then you can make use the Get Replies API to poll for messages.GET /sms API get the latest replies to the message.{ to: '+61418123456' sentTimestamp: '2017-03-17T10:05:22+10:00' receivedTimestamp: '2017-03-17T10:05:23+10:00' messageId: /cccb284200035236000000000ee9d074019e0301/1261418123456 deliveryStatus: DELIVRD } | Field | Description |
|---|---|
to | The number the message was sent to. |
receivedTimestamp | Time the message was sent to the API. |
sentTimestamp | Time handling of the message ended. |
deliveryStatus | The final state of the message. |
messageId | The same reference that was returned when the original message was sent. |
receivedTimestamp | Time the message was sent to the API. |
{ \"status\": \"RECEIVED\" \"destinationAddress\": \"+61418123456\" \"senderAddress\": \"+61421987654\" \"message\": \"Foo\" \"sentTimestamp\": \"2018-03-23T12:10:06+10:00\" } | Field | Description |
|---|---|
status | The final state of the message. |
destinationAddress | The number the message was sent to. |
senderAddress | The number the message was sent from. |
message | The sontent of the SMS reply. |
sentTimestamp | Time handling of the message ended. |
{ \"status\": \"RECEIVED\", \"destinationAddress\": \"+61418123456\", \"senderAddress\": \"+61421987654\", \"subject\": \"Foo\", \"sentTimestamp\": \"2018-03-23T12:15:45+10:00\", \"envelope\": \"string\", \"MMSContent\": [ { \"type\": \"application/smil\", \"filename\": \"smil.xml\", \"payload\": \"string\" }, { \"type\": \"image/jpeg\", \"filename\": \"sample.jpeg\", \"payload\": \"string\" } ] } | Field | Description |
|---|---|
status | The final state of the message. |
destinationAddress | The number the message was sent to. |
senderAddress | The number the message was sent from. |
subject | The subject assigned to the message. |
sentTimestamp | Time handling of the message ended. |
envelope | Information about about terminal type and originating operator. |
MMSContent | An array of the actual content of the reply message. |
type | The content type of the message. |
filename | The filename for the message content. |
payload | The content of the message. |
index module provides access to constructors for all the classes which comprise the public API.
* * An AMD (recommended!) or CommonJS application will generally do something equivalent to the following: @@ -53,7 +53,7 @@ * *
* @module index - * @version 1.0.1 + * @version 1.0.4 */ var exports = { /** @@ -66,16 +66,6 @@ * @property {module:model/DeleteNumberRequest} */ DeleteNumberRequest: DeleteNumberRequest, - /** - * The ErrorError model constructor. - * @property {module:model/ErrorError} - */ - ErrorError: ErrorError, - /** - * The ErrorErrorError model constructor. - * @property {module:model/ErrorErrorError} - */ - ErrorErrorError: ErrorErrorError, /** * The GetSubscriptionResponse model constructor. * @property {module:model/GetSubscriptionResponse} @@ -101,16 +91,6 @@ * @property {module:model/MessageSentResponse} */ MessageSentResponse: MessageSentResponse, - /** - * The MessageType model constructor. - * @property {module:model/MessageType} - */ - MessageType: MessageType, - /** - * The OAuthRequest model constructor. - * @property {module:model/OAuthRequest} - */ - OAuthRequest: OAuthRequest, /** * The OAuthResponse model constructor. * @property {module:model/OAuthResponse} diff --git a/src/model/DeleteNumberRequest.js b/src/model/DeleteNumberRequest.js index c39d942..6067b26 100644 --- a/src/model/DeleteNumberRequest.js +++ b/src/model/DeleteNumberRequest.js @@ -1,13 +1,13 @@ /** * Telstra Messaging API - * The Telstra SMS Messaging API allows your applications to send and receive SMS text messages from Australia's leading network operator. It also allows your application to track the delivery status of both sent and received SMS messages. + * # Introduction Send and receive SMS and MMS messages globally using Telstra’s enterprise grade Messaging API. It also allows your application to track the delivery status of both sent and received messages. Get your dedicated Australian number, and start sending and receiving messages today. # FeaturesThe Telstra Messaging API provides the features below.
| Feature | Description |
|---|---|
Dedicated Number | Provision a mobile number for your account to be used as from address in the API |
Send Messages | Sending SMS or MMS messages |
Receive Messages | Telstra will deliver messages sent to a dedicated number or to the notifyURL defined by you |
Broadcast Messages | Invoke a single API to send a message to a list of number provided in to |
Delivery Status | Query the delivery status of your messages |
Callbacks | Provide a notification URL and Telstra will notify your app when messages status changes |
Alphanumeric Identifier | Differentiate yourself by providing an alphanumeric string in from. This feature is only available on paid plans |
Concatenation | Send messages up to 1900 characters long and Telstra will automaticaly segment and reassemble them |
Reply Request | Create a chat session by associating messageId and to number to track responses received from a mobile number. We will store this association for 8 days |
Character set | Accepts all Unicode characters as part of UTF-8 |
Bounce-back response | See if your SMS hits an unreachable or unallocated number (Australia Only) |
Queuing | Messaging API will automatically queue and deliver each message at a compliant rate. |
Emoji Encoding | The API supports the encoding of the full range of emojis. Emojis in the reply messages will be in their UTF-8 format. |
Client key and Client secret as these will be needed to provision a number for your application and for authentication. Now head over to Getting Started where you can find a postman collection as well as some links to sample apps and SDKs to get you started.
Happy Messaging! # Getting Started
Below are the steps to get started with the Telstra Messaging API.
Client key and Client secret.
notifyURL, when the message has been delivered the API will make a call to this URL to advise of the message status. If this is not provided then you can make use the Get Replies API to poll for messages.GET /sms API get the latest replies to the message.{ to: '+61418123456' sentTimestamp: '2017-03-17T10:05:22+10:00' receivedTimestamp: '2017-03-17T10:05:23+10:00' messageId: /cccb284200035236000000000ee9d074019e0301/1261418123456 deliveryStatus: DELIVRD } | Field | Description |
|---|---|
to | The number the message was sent to. |
receivedTimestamp | Time the message was sent to the API. |
sentTimestamp | Time handling of the message ended. |
deliveryStatus | The final state of the message. |
messageId | The same reference that was returned when the original message was sent. |
receivedTimestamp | Time the message was sent to the API. |
{ \"status\": \"RECEIVED\" \"destinationAddress\": \"+61418123456\" \"senderAddress\": \"+61421987654\" \"message\": \"Foo\" \"sentTimestamp\": \"2018-03-23T12:10:06+10:00\" } | Field | Description |
|---|---|
status | The final state of the message. |
destinationAddress | The number the message was sent to. |
senderAddress | The number the message was sent from. |
message | The sontent of the SMS reply. |
sentTimestamp | Time handling of the message ended. |
{ \"status\": \"RECEIVED\", \"destinationAddress\": \"+61418123456\", \"senderAddress\": \"+61421987654\", \"subject\": \"Foo\", \"sentTimestamp\": \"2018-03-23T12:15:45+10:00\", \"envelope\": \"string\", \"MMSContent\": [ { \"type\": \"application/smil\", \"filename\": \"smil.xml\", \"payload\": \"string\" }, { \"type\": \"image/jpeg\", \"filename\": \"sample.jpeg\", \"payload\": \"string\" } ] } | Field | Description |
|---|---|
status | The final state of the message. |
destinationAddress | The number the message was sent to. |
senderAddress | The number the message was sent from. |
subject | The subject assigned to the message. |
sentTimestamp | Time handling of the message ended. |
envelope | Information about about terminal type and originating operator. |
MMSContent | An array of the actual content of the reply message. |
type | The content type of the message. |
filename | The filename for the message content. |
payload | The content of the message. |
The Telstra Messaging API provides the features below.
| Feature | Description |
|---|---|
Dedicated Number | Provision a mobile number for your account to be used as from address in the API |
Send Messages | Sending SMS or MMS messages |
Receive Messages | Telstra will deliver messages sent to a dedicated number or to the notifyURL defined by you |
Broadcast Messages | Invoke a single API to send a message to a list of number provided in to |
Delivery Status | Query the delivery status of your messages |
Callbacks | Provide a notification URL and Telstra will notify your app when messages status changes |
Alphanumeric Identifier | Differentiate yourself by providing an alphanumeric string in from. This feature is only available on paid plans |
Concatenation | Send messages up to 1900 characters long and Telstra will automaticaly segment and reassemble them |
Reply Request | Create a chat session by associating messageId and to number to track responses received from a mobile number. We will store this association for 8 days |
Character set | Accepts all Unicode characters as part of UTF-8 |
Bounce-back response | See if your SMS hits an unreachable or unallocated number (Australia Only) |
Queuing | Messaging API will automatically queue and deliver each message at a compliant rate. |
Emoji Encoding | The API supports the encoding of the full range of emojis. Emojis in the reply messages will be in their UTF-8 format. |
Client key and Client secret as these will be needed to provision a number for your application and for authentication. Now head over to Getting Started where you can find a postman collection as well as some links to sample apps and SDKs to get you started.
Happy Messaging! # Getting Started
Below are the steps to get started with the Telstra Messaging API.
Client key and Client secret.
notifyURL, when the message has been delivered the API will make a call to this URL to advise of the message status. If this is not provided then you can make use the Get Replies API to poll for messages.GET /sms API get the latest replies to the message.{ to: '+61418123456' sentTimestamp: '2017-03-17T10:05:22+10:00' receivedTimestamp: '2017-03-17T10:05:23+10:00' messageId: /cccb284200035236000000000ee9d074019e0301/1261418123456 deliveryStatus: DELIVRD } | Field | Description |
|---|---|
to | The number the message was sent to. |
receivedTimestamp | Time the message was sent to the API. |
sentTimestamp | Time handling of the message ended. |
deliveryStatus | The final state of the message. |
messageId | The same reference that was returned when the original message was sent. |
receivedTimestamp | Time the message was sent to the API. |
{ \"status\": \"RECEIVED\" \"destinationAddress\": \"+61418123456\" \"senderAddress\": \"+61421987654\" \"message\": \"Foo\" \"sentTimestamp\": \"2018-03-23T12:10:06+10:00\" } | Field | Description |
|---|---|
status | The final state of the message. |
destinationAddress | The number the message was sent to. |
senderAddress | The number the message was sent from. |
message | The sontent of the SMS reply. |
sentTimestamp | Time handling of the message ended. |
{ \"status\": \"RECEIVED\", \"destinationAddress\": \"+61418123456\", \"senderAddress\": \"+61421987654\", \"subject\": \"Foo\", \"sentTimestamp\": \"2018-03-23T12:15:45+10:00\", \"envelope\": \"string\", \"MMSContent\": [ { \"type\": \"application/smil\", \"filename\": \"smil.xml\", \"payload\": \"string\" }, { \"type\": \"image/jpeg\", \"filename\": \"sample.jpeg\", \"payload\": \"string\" } ] } | Field | Description |
|---|---|
status | The final state of the message. |
destinationAddress | The number the message was sent to. |
senderAddress | The number the message was sent from. |
subject | The subject assigned to the message. |
sentTimestamp | Time handling of the message ended. |
envelope | Information about about terminal type and originating operator. |
MMSContent | An array of the actual content of the reply message. |
type | The content type of the message. |
filename | The filename for the message content. |
payload | The content of the message. |
The Telstra Messaging API provides the features below.
| Feature | Description |
|---|---|
Dedicated Number | Provision a mobile number for your account to be used as from address in the API |
Send Messages | Sending SMS or MMS messages |
Receive Messages | Telstra will deliver messages sent to a dedicated number or to the notifyURL defined by you |
Broadcast Messages | Invoke a single API to send a message to a list of number provided in to |
Delivery Status | Query the delivery status of your messages |
Callbacks | Provide a notification URL and Telstra will notify your app when messages status changes |
Alphanumeric Identifier | Differentiate yourself by providing an alphanumeric string in from. This feature is only available on paid plans |
Concatenation | Send messages up to 1900 characters long and Telstra will automaticaly segment and reassemble them |
Reply Request | Create a chat session by associating messageId and to number to track responses received from a mobile number. We will store this association for 8 days |
Character set | Accepts all Unicode characters as part of UTF-8 |
Bounce-back response | See if your SMS hits an unreachable or unallocated number (Australia Only) |
Queuing | Messaging API will automatically queue and deliver each message at a compliant rate. |
Emoji Encoding | The API supports the encoding of the full range of emojis. Emojis in the reply messages will be in their UTF-8 format. |
Client key and Client secret as these will be needed to provision a number for your application and for authentication. Now head over to Getting Started where you can find a postman collection as well as some links to sample apps and SDKs to get you started.
Happy Messaging! # Getting Started
Below are the steps to get started with the Telstra Messaging API.
Client key and Client secret.
notifyURL, when the message has been delivered the API will make a call to this URL to advise of the message status. If this is not provided then you can make use the Get Replies API to poll for messages.GET /sms API get the latest replies to the message.{ to: '+61418123456' sentTimestamp: '2017-03-17T10:05:22+10:00' receivedTimestamp: '2017-03-17T10:05:23+10:00' messageId: /cccb284200035236000000000ee9d074019e0301/1261418123456 deliveryStatus: DELIVRD } | Field | Description |
|---|---|
to | The number the message was sent to. |
receivedTimestamp | Time the message was sent to the API. |
sentTimestamp | Time handling of the message ended. |
deliveryStatus | The final state of the message. |
messageId | The same reference that was returned when the original message was sent. |
receivedTimestamp | Time the message was sent to the API. |
{ \"status\": \"RECEIVED\" \"destinationAddress\": \"+61418123456\" \"senderAddress\": \"+61421987654\" \"message\": \"Foo\" \"sentTimestamp\": \"2018-03-23T12:10:06+10:00\" } | Field | Description |
|---|---|
status | The final state of the message. |
destinationAddress | The number the message was sent to. |
senderAddress | The number the message was sent from. |
message | The sontent of the SMS reply. |
sentTimestamp | Time handling of the message ended. |
{ \"status\": \"RECEIVED\", \"destinationAddress\": \"+61418123456\", \"senderAddress\": \"+61421987654\", \"subject\": \"Foo\", \"sentTimestamp\": \"2018-03-23T12:15:45+10:00\", \"envelope\": \"string\", \"MMSContent\": [ { \"type\": \"application/smil\", \"filename\": \"smil.xml\", \"payload\": \"string\" }, { \"type\": \"image/jpeg\", \"filename\": \"sample.jpeg\", \"payload\": \"string\" } ] } | Field | Description |
|---|---|
status | The final state of the message. |
destinationAddress | The number the message was sent to. |
senderAddress | The number the message was sent from. |
subject | The subject assigned to the message. |
sentTimestamp | Time handling of the message ended. |
envelope | Information about about terminal type and originating operator. |
MMSContent | An array of the actual content of the reply message. |
type | The content type of the message. |
filename | The filename for the message content. |
payload | The content of the message. |
The Telstra Messaging API provides the features below.
| Feature | Description |
|---|---|
Dedicated Number | Provision a mobile number for your account to be used as from address in the API |
Send Messages | Sending SMS or MMS messages |
Receive Messages | Telstra will deliver messages sent to a dedicated number or to the notifyURL defined by you |
Broadcast Messages | Invoke a single API to send a message to a list of number provided in to |
Delivery Status | Query the delivery status of your messages |
Callbacks | Provide a notification URL and Telstra will notify your app when messages status changes |
Alphanumeric Identifier | Differentiate yourself by providing an alphanumeric string in from. This feature is only available on paid plans |
Concatenation | Send messages up to 1900 characters long and Telstra will automaticaly segment and reassemble them |
Reply Request | Create a chat session by associating messageId and to number to track responses received from a mobile number. We will store this association for 8 days |
Character set | Accepts all Unicode characters as part of UTF-8 |
Bounce-back response | See if your SMS hits an unreachable or unallocated number (Australia Only) |
Queuing | Messaging API will automatically queue and deliver each message at a compliant rate. |
Emoji Encoding | The API supports the encoding of the full range of emojis. Emojis in the reply messages will be in their UTF-8 format. |
Client key and Client secret as these will be needed to provision a number for your application and for authentication. Now head over to Getting Started where you can find a postman collection as well as some links to sample apps and SDKs to get you started.
Happy Messaging! # Getting Started
Below are the steps to get started with the Telstra Messaging API.
Client key and Client secret.
notifyURL, when the message has been delivered the API will make a call to this URL to advise of the message status. If this is not provided then you can make use the Get Replies API to poll for messages.GET /sms API get the latest replies to the message.{ to: '+61418123456' sentTimestamp: '2017-03-17T10:05:22+10:00' receivedTimestamp: '2017-03-17T10:05:23+10:00' messageId: /cccb284200035236000000000ee9d074019e0301/1261418123456 deliveryStatus: DELIVRD } | Field | Description |
|---|---|
to | The number the message was sent to. |
receivedTimestamp | Time the message was sent to the API. |
sentTimestamp | Time handling of the message ended. |
deliveryStatus | The final state of the message. |
messageId | The same reference that was returned when the original message was sent. |
receivedTimestamp | Time the message was sent to the API. |
{ \"status\": \"RECEIVED\" \"destinationAddress\": \"+61418123456\" \"senderAddress\": \"+61421987654\" \"message\": \"Foo\" \"sentTimestamp\": \"2018-03-23T12:10:06+10:00\" } | Field | Description |
|---|---|
status | The final state of the message. |
destinationAddress | The number the message was sent to. |
senderAddress | The number the message was sent from. |
message | The sontent of the SMS reply. |
sentTimestamp | Time handling of the message ended. |
{ \"status\": \"RECEIVED\", \"destinationAddress\": \"+61418123456\", \"senderAddress\": \"+61421987654\", \"subject\": \"Foo\", \"sentTimestamp\": \"2018-03-23T12:15:45+10:00\", \"envelope\": \"string\", \"MMSContent\": [ { \"type\": \"application/smil\", \"filename\": \"smil.xml\", \"payload\": \"string\" }, { \"type\": \"image/jpeg\", \"filename\": \"sample.jpeg\", \"payload\": \"string\" } ] } | Field | Description |
|---|---|
status | The final state of the message. |
destinationAddress | The number the message was sent to. |
senderAddress | The number the message was sent from. |
subject | The subject assigned to the message. |
sentTimestamp | Time handling of the message ended. |
envelope | Information about about terminal type and originating operator. |
MMSContent | An array of the actual content of the reply message. |
type | The content type of the message. |
filename | The filename for the message content. |
payload | The content of the message. |
The Telstra Messaging API provides the features below.
| Feature | Description |
|---|---|
Dedicated Number | Provision a mobile number for your account to be used as from address in the API |
Send Messages | Sending SMS or MMS messages |
Receive Messages | Telstra will deliver messages sent to a dedicated number or to the notifyURL defined by you |
Broadcast Messages | Invoke a single API to send a message to a list of number provided in to |
Delivery Status | Query the delivery status of your messages |
Callbacks | Provide a notification URL and Telstra will notify your app when messages status changes |
Alphanumeric Identifier | Differentiate yourself by providing an alphanumeric string in from. This feature is only available on paid plans |
Concatenation | Send messages up to 1900 characters long and Telstra will automaticaly segment and reassemble them |
Reply Request | Create a chat session by associating messageId and to number to track responses received from a mobile number. We will store this association for 8 days |
Character set | Accepts all Unicode characters as part of UTF-8 |
Bounce-back response | See if your SMS hits an unreachable or unallocated number (Australia Only) |
Queuing | Messaging API will automatically queue and deliver each message at a compliant rate. |
Emoji Encoding | The API supports the encoding of the full range of emojis. Emojis in the reply messages will be in their UTF-8 format. |
Client key and Client secret as these will be needed to provision a number for your application and for authentication. Now head over to Getting Started where you can find a postman collection as well as some links to sample apps and SDKs to get you started.
Happy Messaging! # Getting Started
Below are the steps to get started with the Telstra Messaging API.
Client key and Client secret.
notifyURL, when the message has been delivered the API will make a call to this URL to advise of the message status. If this is not provided then you can make use the Get Replies API to poll for messages.GET /sms API get the latest replies to the message.{ to: '+61418123456' sentTimestamp: '2017-03-17T10:05:22+10:00' receivedTimestamp: '2017-03-17T10:05:23+10:00' messageId: /cccb284200035236000000000ee9d074019e0301/1261418123456 deliveryStatus: DELIVRD } | Field | Description |
|---|---|
to | The number the message was sent to. |
receivedTimestamp | Time the message was sent to the API. |
sentTimestamp | Time handling of the message ended. |
deliveryStatus | The final state of the message. |
messageId | The same reference that was returned when the original message was sent. |
receivedTimestamp | Time the message was sent to the API. |
{ \"status\": \"RECEIVED\" \"destinationAddress\": \"+61418123456\" \"senderAddress\": \"+61421987654\" \"message\": \"Foo\" \"sentTimestamp\": \"2018-03-23T12:10:06+10:00\" } | Field | Description |
|---|---|
status | The final state of the message. |
destinationAddress | The number the message was sent to. |
senderAddress | The number the message was sent from. |
message | The sontent of the SMS reply. |
sentTimestamp | Time handling of the message ended. |
{ \"status\": \"RECEIVED\", \"destinationAddress\": \"+61418123456\", \"senderAddress\": \"+61421987654\", \"subject\": \"Foo\", \"sentTimestamp\": \"2018-03-23T12:15:45+10:00\", \"envelope\": \"string\", \"MMSContent\": [ { \"type\": \"application/smil\", \"filename\": \"smil.xml\", \"payload\": \"string\" }, { \"type\": \"image/jpeg\", \"filename\": \"sample.jpeg\", \"payload\": \"string\" } ] } | Field | Description |
|---|---|
status | The final state of the message. |
destinationAddress | The number the message was sent to. |
senderAddress | The number the message was sent from. |
subject | The subject assigned to the message. |
sentTimestamp | Time handling of the message ended. |
envelope | Information about about terminal type and originating operator. |
MMSContent | An array of the actual content of the reply message. |
type | The content type of the message. |
filename | The filename for the message content. |
payload | The content of the message. |
Message.
* @alias module:model/Message
* @class
- * @param to {String}
- * @param deliveryStatus {String}
- * @param messageId {String}
+ * @param to {String} Just a copy of the number the message is sent to.
+ * @param deliveryStatus {String} Gives an indication if the message has been accepted for delivery. The description field contains information on why a message may have been rejected.
+ * @param messageId {String} For an accepted message, ths will be a unique reference that can be used to check the messages status. Please refer to the Delivery Notification section. Note that `messageId` will be different for each number that the message was sent to.
*/
var exports = function(to, deliveryStatus, messageId) {
var _this = this;
@@ -84,22 +84,22 @@
}
/**
- *
+ * Just a copy of the number the message is sent to.
* @member {String} to
*/
exports.prototype['to'] = undefined;
/**
- *
+ * Gives an indication if the message has been accepted for delivery. The description field contains information on why a message may have been rejected.
* @member {String} deliveryStatus
*/
exports.prototype['deliveryStatus'] = undefined;
/**
- *
+ * For an accepted message, ths will be a unique reference that can be used to check the messages status. Please refer to the Delivery Notification section. Note that `messageId` will be different for each number that the message was sent to.
* @member {String} messageId
*/
exports.prototype['messageId'] = undefined;
/**
- *
+ * For an accepted message, ths will be the URL that can be used to check the messages status. Please refer to the Delivery Notification section.
* @member {String} messageStatusURL
*/
exports.prototype['messageStatusURL'] = undefined;
diff --git a/src/model/MessageSentResponse.js b/src/model/MessageSentResponse.js
index 5361b72..e948ffe 100644
--- a/src/model/MessageSentResponse.js
+++ b/src/model/MessageSentResponse.js
@@ -1,13 +1,13 @@
/**
* Telstra Messaging API
- * The Telstra SMS Messaging API allows your applications to send and receive SMS text messages from Australia's leading network operator. It also allows your application to track the delivery status of both sent and received SMS messages.
+ * # Introduction Send and receive SMS and MMS messages globally using Telstra’s enterprise grade Messaging API. It also allows your application to track the delivery status of both sent and received messages. Get your dedicated Australian number, and start sending and receiving messages today. # Features The Telstra Messaging API provides the features below.
| Feature | Description |
|---|---|
Dedicated Number | Provision a mobile number for your account to be used as from address in the API |
Send Messages | Sending SMS or MMS messages |
Receive Messages | Telstra will deliver messages sent to a dedicated number or to the notifyURL defined by you |
Broadcast Messages | Invoke a single API to send a message to a list of number provided in to |
Delivery Status | Query the delivery status of your messages |
Callbacks | Provide a notification URL and Telstra will notify your app when messages status changes |
Alphanumeric Identifier | Differentiate yourself by providing an alphanumeric string in from. This feature is only available on paid plans |
Concatenation | Send messages up to 1900 characters long and Telstra will automaticaly segment and reassemble them |
Reply Request | Create a chat session by associating messageId and to number to track responses received from a mobile number. We will store this association for 8 days |
Character set | Accepts all Unicode characters as part of UTF-8 |
Bounce-back response | See if your SMS hits an unreachable or unallocated number (Australia Only) |
Queuing | Messaging API will automatically queue and deliver each message at a compliant rate. |
Emoji Encoding | The API supports the encoding of the full range of emojis. Emojis in the reply messages will be in their UTF-8 format. |
Client key and Client secret as these will be needed to provision a number for your application and for authentication. Now head over to Getting Started where you can find a postman collection as well as some links to sample apps and SDKs to get you started.
Happy Messaging! # Getting Started
Below are the steps to get started with the Telstra Messaging API.
Client key and Client secret.
notifyURL, when the message has been delivered the API will make a call to this URL to advise of the message status. If this is not provided then you can make use the Get Replies API to poll for messages.GET /sms API get the latest replies to the message.{ to: '+61418123456' sentTimestamp: '2017-03-17T10:05:22+10:00' receivedTimestamp: '2017-03-17T10:05:23+10:00' messageId: /cccb284200035236000000000ee9d074019e0301/1261418123456 deliveryStatus: DELIVRD } | Field | Description |
|---|---|
to | The number the message was sent to. |
receivedTimestamp | Time the message was sent to the API. |
sentTimestamp | Time handling of the message ended. |
deliveryStatus | The final state of the message. |
messageId | The same reference that was returned when the original message was sent. |
receivedTimestamp | Time the message was sent to the API. |
{ \"status\": \"RECEIVED\" \"destinationAddress\": \"+61418123456\" \"senderAddress\": \"+61421987654\" \"message\": \"Foo\" \"sentTimestamp\": \"2018-03-23T12:10:06+10:00\" } | Field | Description |
|---|---|
status | The final state of the message. |
destinationAddress | The number the message was sent to. |
senderAddress | The number the message was sent from. |
message | The sontent of the SMS reply. |
sentTimestamp | Time handling of the message ended. |
{ \"status\": \"RECEIVED\", \"destinationAddress\": \"+61418123456\", \"senderAddress\": \"+61421987654\", \"subject\": \"Foo\", \"sentTimestamp\": \"2018-03-23T12:15:45+10:00\", \"envelope\": \"string\", \"MMSContent\": [ { \"type\": \"application/smil\", \"filename\": \"smil.xml\", \"payload\": \"string\" }, { \"type\": \"image/jpeg\", \"filename\": \"sample.jpeg\", \"payload\": \"string\" } ] } | Field | Description |
|---|---|
status | The final state of the message. |
destinationAddress | The number the message was sent to. |
senderAddress | The number the message was sent from. |
subject | The subject assigned to the message. |
sentTimestamp | Time handling of the message ended. |
envelope | Information about about terminal type and originating operator. |
MMSContent | An array of the actual content of the reply message. |
type | The content type of the message. |
filename | The filename for the message content. |
payload | The content of the message. |
MessageSentResponse.
* @alias module:model/MessageSentResponse
* @class
- * @param messages {Array.The Telstra Messaging API provides the features below.
| Feature | Description |
|---|---|
Dedicated Number | Provision a mobile number for your account to be used as from address in the API |
Send Messages | Sending SMS or MMS messages |
Receive Messages | Telstra will deliver messages sent to a dedicated number or to the notifyURL defined by you |
Broadcast Messages | Invoke a single API to send a message to a list of number provided in to |
Delivery Status | Query the delivery status of your messages |
Callbacks | Provide a notification URL and Telstra will notify your app when messages status changes |
Alphanumeric Identifier | Differentiate yourself by providing an alphanumeric string in from. This feature is only available on paid plans |
Concatenation | Send messages up to 1900 characters long and Telstra will automaticaly segment and reassemble them |
Reply Request | Create a chat session by associating messageId and to number to track responses received from a mobile number. We will store this association for 8 days |
Character set | Accepts all Unicode characters as part of UTF-8 |
Bounce-back response | See if your SMS hits an unreachable or unallocated number (Australia Only) |
Queuing | Messaging API will automatically queue and deliver each message at a compliant rate. |
Emoji Encoding | The API supports the encoding of the full range of emojis. Emojis in the reply messages will be in their UTF-8 format. |
Client key and Client secret as these will be needed to provision a number for your application and for authentication. Now head over to Getting Started where you can find a postman collection as well as some links to sample apps and SDKs to get you started.
Happy Messaging! # Getting Started
Below are the steps to get started with the Telstra Messaging API.
Client key and Client secret.
notifyURL, when the message has been delivered the API will make a call to this URL to advise of the message status. If this is not provided then you can make use the Get Replies API to poll for messages.GET /sms API get the latest replies to the message.{ to: '+61418123456' sentTimestamp: '2017-03-17T10:05:22+10:00' receivedTimestamp: '2017-03-17T10:05:23+10:00' messageId: /cccb284200035236000000000ee9d074019e0301/1261418123456 deliveryStatus: DELIVRD } | Field | Description |
|---|---|
to | The number the message was sent to. |
receivedTimestamp | Time the message was sent to the API. |
sentTimestamp | Time handling of the message ended. |
deliveryStatus | The final state of the message. |
messageId | The same reference that was returned when the original message was sent. |
receivedTimestamp | Time the message was sent to the API. |
{ \"status\": \"RECEIVED\" \"destinationAddress\": \"+61418123456\" \"senderAddress\": \"+61421987654\" \"message\": \"Foo\" \"sentTimestamp\": \"2018-03-23T12:10:06+10:00\" } | Field | Description |
|---|---|
status | The final state of the message. |
destinationAddress | The number the message was sent to. |
senderAddress | The number the message was sent from. |
message | The sontent of the SMS reply. |
sentTimestamp | Time handling of the message ended. |
{ \"status\": \"RECEIVED\", \"destinationAddress\": \"+61418123456\", \"senderAddress\": \"+61421987654\", \"subject\": \"Foo\", \"sentTimestamp\": \"2018-03-23T12:15:45+10:00\", \"envelope\": \"string\", \"MMSContent\": [ { \"type\": \"application/smil\", \"filename\": \"smil.xml\", \"payload\": \"string\" }, { \"type\": \"image/jpeg\", \"filename\": \"sample.jpeg\", \"payload\": \"string\" } ] } | Field | Description |
|---|---|
status | The final state of the message. |
destinationAddress | The number the message was sent to. |
senderAddress | The number the message was sent from. |
subject | The subject assigned to the message. |
sentTimestamp | Time handling of the message ended. |
envelope | Information about about terminal type and originating operator. |
MMSContent | An array of the actual content of the reply message. |
type | The content type of the message. |
filename | The filename for the message content. |
payload | The content of the message. |
The Telstra Messaging API provides the features below.
| Feature | Description |
|---|---|
Dedicated Number | Provision a mobile number for your account to be used as from address in the API |
Send Messages | Sending SMS or MMS messages |
Receive Messages | Telstra will deliver messages sent to a dedicated number or to the notifyURL defined by you |
Broadcast Messages | Invoke a single API to send a message to a list of number provided in to |
Delivery Status | Query the delivery status of your messages |
Callbacks | Provide a notification URL and Telstra will notify your app when messages status changes |
Alphanumeric Identifier | Differentiate yourself by providing an alphanumeric string in from. This feature is only available on paid plans |
Concatenation | Send messages up to 1900 characters long and Telstra will automaticaly segment and reassemble them |
Reply Request | Create a chat session by associating messageId and to number to track responses received from a mobile number. We will store this association for 8 days |
Character set | Accepts all Unicode characters as part of UTF-8 |
Bounce-back response | See if your SMS hits an unreachable or unallocated number (Australia Only) |
Queuing | Messaging API will automatically queue and deliver each message at a compliant rate. |
Emoji Encoding | The API supports the encoding of the full range of emojis. Emojis in the reply messages will be in their UTF-8 format. |
Client key and Client secret as these will be needed to provision a number for your application and for authentication. Now head over to Getting Started where you can find a postman collection as well as some links to sample apps and SDKs to get you started.
Happy Messaging! # Getting Started
Below are the steps to get started with the Telstra Messaging API.
Client key and Client secret.
notifyURL, when the message has been delivered the API will make a call to this URL to advise of the message status. If this is not provided then you can make use the Get Replies API to poll for messages.GET /sms API get the latest replies to the message.{ to: '+61418123456' sentTimestamp: '2017-03-17T10:05:22+10:00' receivedTimestamp: '2017-03-17T10:05:23+10:00' messageId: /cccb284200035236000000000ee9d074019e0301/1261418123456 deliveryStatus: DELIVRD } | Field | Description |
|---|---|
to | The number the message was sent to. |
receivedTimestamp | Time the message was sent to the API. |
sentTimestamp | Time handling of the message ended. |
deliveryStatus | The final state of the message. |
messageId | The same reference that was returned when the original message was sent. |
receivedTimestamp | Time the message was sent to the API. |
{ \"status\": \"RECEIVED\" \"destinationAddress\": \"+61418123456\" \"senderAddress\": \"+61421987654\" \"message\": \"Foo\" \"sentTimestamp\": \"2018-03-23T12:10:06+10:00\" } | Field | Description |
|---|---|
status | The final state of the message. |
destinationAddress | The number the message was sent to. |
senderAddress | The number the message was sent from. |
message | The sontent of the SMS reply. |
sentTimestamp | Time handling of the message ended. |
{ \"status\": \"RECEIVED\", \"destinationAddress\": \"+61418123456\", \"senderAddress\": \"+61421987654\", \"subject\": \"Foo\", \"sentTimestamp\": \"2018-03-23T12:15:45+10:00\", \"envelope\": \"string\", \"MMSContent\": [ { \"type\": \"application/smil\", \"filename\": \"smil.xml\", \"payload\": \"string\" }, { \"type\": \"image/jpeg\", \"filename\": \"sample.jpeg\", \"payload\": \"string\" } ] } | Field | Description |
|---|---|
status | The final state of the message. |
destinationAddress | The number the message was sent to. |
senderAddress | The number the message was sent from. |
subject | The subject assigned to the message. |
sentTimestamp | Time handling of the message ended. |
envelope | Information about about terminal type and originating operator. |
MMSContent | An array of the actual content of the reply message. |
type | The content type of the message. |
filename | The filename for the message content. |
payload | The content of the message. |
The Telstra Messaging API provides the features below.
| Feature | Description |
|---|---|
Dedicated Number | Provision a mobile number for your account to be used as from address in the API |
Send Messages | Sending SMS or MMS messages |
Receive Messages | Telstra will deliver messages sent to a dedicated number or to the notifyURL defined by you |
Broadcast Messages | Invoke a single API to send a message to a list of number provided in to |
Delivery Status | Query the delivery status of your messages |
Callbacks | Provide a notification URL and Telstra will notify your app when messages status changes |
Alphanumeric Identifier | Differentiate yourself by providing an alphanumeric string in from. This feature is only available on paid plans |
Concatenation | Send messages up to 1900 characters long and Telstra will automaticaly segment and reassemble them |
Reply Request | Create a chat session by associating messageId and to number to track responses received from a mobile number. We will store this association for 8 days |
Character set | Accepts all Unicode characters as part of UTF-8 |
Bounce-back response | See if your SMS hits an unreachable or unallocated number (Australia Only) |
Queuing | Messaging API will automatically queue and deliver each message at a compliant rate. |
Emoji Encoding | The API supports the encoding of the full range of emojis. Emojis in the reply messages will be in their UTF-8 format. |
Client key and Client secret as these will be needed to provision a number for your application and for authentication. Now head over to Getting Started where you can find a postman collection as well as some links to sample apps and SDKs to get you started.
Happy Messaging! # Getting Started
Below are the steps to get started with the Telstra Messaging API.
Client key and Client secret.
notifyURL, when the message has been delivered the API will make a call to this URL to advise of the message status. If this is not provided then you can make use the Get Replies API to poll for messages.GET /sms API get the latest replies to the message.{ to: '+61418123456' sentTimestamp: '2017-03-17T10:05:22+10:00' receivedTimestamp: '2017-03-17T10:05:23+10:00' messageId: /cccb284200035236000000000ee9d074019e0301/1261418123456 deliveryStatus: DELIVRD } | Field | Description |
|---|---|
to | The number the message was sent to. |
receivedTimestamp | Time the message was sent to the API. |
sentTimestamp | Time handling of the message ended. |
deliveryStatus | The final state of the message. |
messageId | The same reference that was returned when the original message was sent. |
receivedTimestamp | Time the message was sent to the API. |
{ \"status\": \"RECEIVED\" \"destinationAddress\": \"+61418123456\" \"senderAddress\": \"+61421987654\" \"message\": \"Foo\" \"sentTimestamp\": \"2018-03-23T12:10:06+10:00\" } | Field | Description |
|---|---|
status | The final state of the message. |
destinationAddress | The number the message was sent to. |
senderAddress | The number the message was sent from. |
message | The sontent of the SMS reply. |
sentTimestamp | Time handling of the message ended. |
{ \"status\": \"RECEIVED\", \"destinationAddress\": \"+61418123456\", \"senderAddress\": \"+61421987654\", \"subject\": \"Foo\", \"sentTimestamp\": \"2018-03-23T12:15:45+10:00\", \"envelope\": \"string\", \"MMSContent\": [ { \"type\": \"application/smil\", \"filename\": \"smil.xml\", \"payload\": \"string\" }, { \"type\": \"image/jpeg\", \"filename\": \"sample.jpeg\", \"payload\": \"string\" } ] } | Field | Description |
|---|---|
status | The final state of the message. |
destinationAddress | The number the message was sent to. |
senderAddress | The number the message was sent from. |
subject | The subject assigned to the message. |
sentTimestamp | Time handling of the message ended. |
envelope | Information about about terminal type and originating operator. |
MMSContent | An array of the actual content of the reply message. |
type | The content type of the message. |
filename | The filename for the message content. |
payload | The content of the message. |
The Telstra Messaging API provides the features below.
| Feature | Description |
|---|---|
Dedicated Number | Provision a mobile number for your account to be used as from address in the API |
Send Messages | Sending SMS or MMS messages |
Receive Messages | Telstra will deliver messages sent to a dedicated number or to the notifyURL defined by you |
Broadcast Messages | Invoke a single API to send a message to a list of number provided in to |
Delivery Status | Query the delivery status of your messages |
Callbacks | Provide a notification URL and Telstra will notify your app when messages status changes |
Alphanumeric Identifier | Differentiate yourself by providing an alphanumeric string in from. This feature is only available on paid plans |
Concatenation | Send messages up to 1900 characters long and Telstra will automaticaly segment and reassemble them |
Reply Request | Create a chat session by associating messageId and to number to track responses received from a mobile number. We will store this association for 8 days |
Character set | Accepts all Unicode characters as part of UTF-8 |
Bounce-back response | See if your SMS hits an unreachable or unallocated number (Australia Only) |
Queuing | Messaging API will automatically queue and deliver each message at a compliant rate. |
Emoji Encoding | The API supports the encoding of the full range of emojis. Emojis in the reply messages will be in their UTF-8 format. |
Client key and Client secret as these will be needed to provision a number for your application and for authentication. Now head over to Getting Started where you can find a postman collection as well as some links to sample apps and SDKs to get you started.
Happy Messaging! # Getting Started
Below are the steps to get started with the Telstra Messaging API.
Client key and Client secret.
notifyURL, when the message has been delivered the API will make a call to this URL to advise of the message status. If this is not provided then you can make use the Get Replies API to poll for messages.GET /sms API get the latest replies to the message.{ to: '+61418123456' sentTimestamp: '2017-03-17T10:05:22+10:00' receivedTimestamp: '2017-03-17T10:05:23+10:00' messageId: /cccb284200035236000000000ee9d074019e0301/1261418123456 deliveryStatus: DELIVRD } | Field | Description |
|---|---|
to | The number the message was sent to. |
receivedTimestamp | Time the message was sent to the API. |
sentTimestamp | Time handling of the message ended. |
deliveryStatus | The final state of the message. |
messageId | The same reference that was returned when the original message was sent. |
receivedTimestamp | Time the message was sent to the API. |
{ \"status\": \"RECEIVED\" \"destinationAddress\": \"+61418123456\" \"senderAddress\": \"+61421987654\" \"message\": \"Foo\" \"sentTimestamp\": \"2018-03-23T12:10:06+10:00\" } | Field | Description |
|---|---|
status | The final state of the message. |
destinationAddress | The number the message was sent to. |
senderAddress | The number the message was sent from. |
message | The sontent of the SMS reply. |
sentTimestamp | Time handling of the message ended. |
{ \"status\": \"RECEIVED\", \"destinationAddress\": \"+61418123456\", \"senderAddress\": \"+61421987654\", \"subject\": \"Foo\", \"sentTimestamp\": \"2018-03-23T12:15:45+10:00\", \"envelope\": \"string\", \"MMSContent\": [ { \"type\": \"application/smil\", \"filename\": \"smil.xml\", \"payload\": \"string\" }, { \"type\": \"image/jpeg\", \"filename\": \"sample.jpeg\", \"payload\": \"string\" } ] } | Field | Description |
|---|---|
status | The final state of the message. |
destinationAddress | The number the message was sent to. |
senderAddress | The number the message was sent from. |
subject | The subject assigned to the message. |
sentTimestamp | Time handling of the message ended. |
envelope | Information about about terminal type and originating operator. |
MMSContent | An array of the actual content of the reply message. |
type | The content type of the message. |
filename | The filename for the message content. |
payload | The content of the message. |
The Telstra Messaging API provides the features below.
| Feature | Description |
|---|---|
Dedicated Number | Provision a mobile number for your account to be used as from address in the API |
Send Messages | Sending SMS or MMS messages |
Receive Messages | Telstra will deliver messages sent to a dedicated number or to the notifyURL defined by you |
Broadcast Messages | Invoke a single API to send a message to a list of number provided in to |
Delivery Status | Query the delivery status of your messages |
Callbacks | Provide a notification URL and Telstra will notify your app when messages status changes |
Alphanumeric Identifier | Differentiate yourself by providing an alphanumeric string in from. This feature is only available on paid plans |
Concatenation | Send messages up to 1900 characters long and Telstra will automaticaly segment and reassemble them |
Reply Request | Create a chat session by associating messageId and to number to track responses received from a mobile number. We will store this association for 8 days |
Character set | Accepts all Unicode characters as part of UTF-8 |
Bounce-back response | See if your SMS hits an unreachable or unallocated number (Australia Only) |
Queuing | Messaging API will automatically queue and deliver each message at a compliant rate. |
Emoji Encoding | The API supports the encoding of the full range of emojis. Emojis in the reply messages will be in their UTF-8 format. |
Client key and Client secret as these will be needed to provision a number for your application and for authentication. Now head over to Getting Started where you can find a postman collection as well as some links to sample apps and SDKs to get you started.
Happy Messaging! # Getting Started
Below are the steps to get started with the Telstra Messaging API.
Client key and Client secret.
notifyURL, when the message has been delivered the API will make a call to this URL to advise of the message status. If this is not provided then you can make use the Get Replies API to poll for messages.GET /sms API get the latest replies to the message.{ to: '+61418123456' sentTimestamp: '2017-03-17T10:05:22+10:00' receivedTimestamp: '2017-03-17T10:05:23+10:00' messageId: /cccb284200035236000000000ee9d074019e0301/1261418123456 deliveryStatus: DELIVRD } | Field | Description |
|---|---|
to | The number the message was sent to. |
receivedTimestamp | Time the message was sent to the API. |
sentTimestamp | Time handling of the message ended. |
deliveryStatus | The final state of the message. |
messageId | The same reference that was returned when the original message was sent. |
receivedTimestamp | Time the message was sent to the API. |
{ \"status\": \"RECEIVED\" \"destinationAddress\": \"+61418123456\" \"senderAddress\": \"+61421987654\" \"message\": \"Foo\" \"sentTimestamp\": \"2018-03-23T12:10:06+10:00\" } | Field | Description |
|---|---|
status | The final state of the message. |
destinationAddress | The number the message was sent to. |
senderAddress | The number the message was sent from. |
message | The sontent of the SMS reply. |
sentTimestamp | Time handling of the message ended. |
{ \"status\": \"RECEIVED\", \"destinationAddress\": \"+61418123456\", \"senderAddress\": \"+61421987654\", \"subject\": \"Foo\", \"sentTimestamp\": \"2018-03-23T12:15:45+10:00\", \"envelope\": \"string\", \"MMSContent\": [ { \"type\": \"application/smil\", \"filename\": \"smil.xml\", \"payload\": \"string\" }, { \"type\": \"image/jpeg\", \"filename\": \"sample.jpeg\", \"payload\": \"string\" } ] } | Field | Description |
|---|---|
status | The final state of the message. |
destinationAddress | The number the message was sent to. |
senderAddress | The number the message was sent from. |
subject | The subject assigned to the message. |
sentTimestamp | Time handling of the message ended. |
envelope | Information about about terminal type and originating operator. |
MMSContent | An array of the actual content of the reply message. |
type | The content type of the message. |
filename | The filename for the message content. |
payload | The content of the message. |
The Telstra Messaging API provides the features below.
| Feature | Description |
|---|---|
Dedicated Number | Provision a mobile number for your account to be used as from address in the API |
Send Messages | Sending SMS or MMS messages |
Receive Messages | Telstra will deliver messages sent to a dedicated number or to the notifyURL defined by you |
Broadcast Messages | Invoke a single API to send a message to a list of number provided in to |
Delivery Status | Query the delivery status of your messages |
Callbacks | Provide a notification URL and Telstra will notify your app when messages status changes |
Alphanumeric Identifier | Differentiate yourself by providing an alphanumeric string in from. This feature is only available on paid plans |
Concatenation | Send messages up to 1900 characters long and Telstra will automaticaly segment and reassemble them |
Reply Request | Create a chat session by associating messageId and to number to track responses received from a mobile number. We will store this association for 8 days |
Character set | Accepts all Unicode characters as part of UTF-8 |
Bounce-back response | See if your SMS hits an unreachable or unallocated number (Australia Only) |
Queuing | Messaging API will automatically queue and deliver each message at a compliant rate. |
Emoji Encoding | The API supports the encoding of the full range of emojis. Emojis in the reply messages will be in their UTF-8 format. |
Client key and Client secret as these will be needed to provision a number for your application and for authentication. Now head over to Getting Started where you can find a postman collection as well as some links to sample apps and SDKs to get you started.
Happy Messaging! # Getting Started
Below are the steps to get started with the Telstra Messaging API.
Client key and Client secret.
notifyURL, when the message has been delivered the API will make a call to this URL to advise of the message status. If this is not provided then you can make use the Get Replies API to poll for messages.GET /sms API get the latest replies to the message.{ to: '+61418123456' sentTimestamp: '2017-03-17T10:05:22+10:00' receivedTimestamp: '2017-03-17T10:05:23+10:00' messageId: /cccb284200035236000000000ee9d074019e0301/1261418123456 deliveryStatus: DELIVRD } | Field | Description |
|---|---|
to | The number the message was sent to. |
receivedTimestamp | Time the message was sent to the API. |
sentTimestamp | Time handling of the message ended. |
deliveryStatus | The final state of the message. |
messageId | The same reference that was returned when the original message was sent. |
receivedTimestamp | Time the message was sent to the API. |
{ \"status\": \"RECEIVED\" \"destinationAddress\": \"+61418123456\" \"senderAddress\": \"+61421987654\" \"message\": \"Foo\" \"sentTimestamp\": \"2018-03-23T12:10:06+10:00\" } | Field | Description |
|---|---|
status | The final state of the message. |
destinationAddress | The number the message was sent to. |
senderAddress | The number the message was sent from. |
message | The sontent of the SMS reply. |
sentTimestamp | Time handling of the message ended. |
{ \"status\": \"RECEIVED\", \"destinationAddress\": \"+61418123456\", \"senderAddress\": \"+61421987654\", \"subject\": \"Foo\", \"sentTimestamp\": \"2018-03-23T12:15:45+10:00\", \"envelope\": \"string\", \"MMSContent\": [ { \"type\": \"application/smil\", \"filename\": \"smil.xml\", \"payload\": \"string\" }, { \"type\": \"image/jpeg\", \"filename\": \"sample.jpeg\", \"payload\": \"string\" } ] } | Field | Description |
|---|---|
status | The final state of the message. |
destinationAddress | The number the message was sent to. |
senderAddress | The number the message was sent from. |
subject | The subject assigned to the message. |
sentTimestamp | Time handling of the message ended. |
envelope | Information about about terminal type and originating operator. |
MMSContent | An array of the actual content of the reply message. |
type | The content type of the message. |
filename | The filename for the message content. |
payload | The content of the message. |
SendSMSRequest.
* @alias module:model/SendSMSRequest
* @class
- * @param to {String} Phone number (in E.164 format) to send the SMS to. This number can be in international format if preceeded by a ‘+’, or in national format.
- * @param body {String} The text body of the message. Messages longer than 160 characters will be counted as multiple messages.
+ * @param to {String} Phone number (in E.164 format) to send the SMS to. This number can be in international format `\"to\": \"+61412345678\"` or in national format. Can be an array of strings if sending to multiple numbers: `\"to\": \"+61412345678, +61418765432\"`
+ * @param body {String} The text body of the message. Messages longer than 160 characters will be counted as multiple messages. This field contains the message text, this can be up to 1900 (for a single recipient) or 500 (for multiple recipients) UTF-8 characters. As mobile devices rarely support the full range of UTF-8 characters, it is possible that some characters may not be translated correctly by the mobile device
*/
var exports = function(to, body) {
var _this = this;
@@ -56,6 +56,7 @@
+
};
/**
@@ -90,45 +91,53 @@
if (data.hasOwnProperty('replyRequest')) {
obj['replyRequest'] = ApiClient.convertToType(data['replyRequest'], 'Boolean');
}
+ if (data.hasOwnProperty('priority')) {
+ obj['priority'] = ApiClient.convertToType(data['priority'], 'Boolean');
+ }
}
return obj;
}
/**
- * Phone number (in E.164 format) to send the SMS to. This number can be in international format if preceeded by a ‘+’, or in national format.
+ * Phone number (in E.164 format) to send the SMS to. This number can be in international format `\"to\": \"+61412345678\"` or in national format. Can be an array of strings if sending to multiple numbers: `\"to\": \"+61412345678, +61418765432\"`
* @member {String} to
*/
exports.prototype['to'] = undefined;
/**
- * The text body of the message. Messages longer than 160 characters will be counted as multiple messages.
+ * The text body of the message. Messages longer than 160 characters will be counted as multiple messages. This field contains the message text, this can be up to 1900 (for a single recipient) or 500 (for multiple recipients) UTF-8 characters. As mobile devices rarely support the full range of UTF-8 characters, it is possible that some characters may not be translated correctly by the mobile device
* @member {String} body
*/
exports.prototype['body'] = undefined;
/**
- * Phone number (in E.164 format) the SMS was sent from. If not present, the serverice will use the mobile number associated with the application, or it be an Alphanumeric address of up to 11 characters.
+ * The Alphanumeric sender ID of up to 11 characters or phone number the SMS was sent from. If not present, the service will use the mobile number associated with the application (in E.164 format). This feature is only available on paid plans.
* @member {String} from
*/
exports.prototype['from'] = undefined;
/**
- * How long the platform should attempt to deliver the message for. This period is specified in minutes from the message
+ * How long the platform should attempt to deliver the message for. This period is specified in minutes from the message. Normally if the message cannot be delivered immediately, it will be stored and delivery will be periodically reattempted. The network will attempt to send the message for up to seven days. It is possible to define a period smaller than 7 days by including this parameter and specifying the number of minutes that delivery should be attempted. eg: including `\"validity\": 60` will specify that if a message can't be delivered within the first 60 minutes them the network should stop.
* @member {Number} validity
*/
exports.prototype['validity'] = undefined;
/**
- * How long the platform should wait before attempting to send the message - specified in minutes.
+ * How long the platform should wait before attempting to send the message - specified in minutes. e.g.: If `\"scheduledDelivery\": 120` is included, then the network will not attempt to start message delivery for two hours after the message has been submitted
* @member {Number} scheduledDelivery
*/
exports.prototype['scheduledDelivery'] = undefined;
/**
- * Contains a URL that will be called once your message has been processed. The status may be delivered, expired, deleted, etc.
+ * Contains a URL that will be called once your message has been processed. The status may be delivered, expired, deleted, etc. It is possible for the network to make a call to a URL when the message has been delivered (or has expired), different URLs can be set per message. Please refer to the Delivery Notification section.
* @member {String} notifyURL
*/
exports.prototype['notifyURL'] = undefined;
/**
- * If set to true, the reply message functionality will be implemented and the to address will be ignored if present. If false or not present, then normal message handling is implemented.
+ * If set to true, the reply message functionality will be implemented and the to address will be ignored if present. If false or not present, then normal message handling is implemented. When set to true, network will use a temporary number to deliver this message. All messages sent by mobile to this temporary number will be stored against the same `messageId`. If a `notifyURL` is provided then user response will be delivered to the URL where `messageId` will be same as `messageId` in reponse to original API request. This field contains the message text, this can be up to 500 UTF-8 characters. As mobile devices rarely support the full range of UTF-8 characters, it is possible that some characters may not be translated correctly by the mobile device.
* @member {Boolean} replyRequest
*/
exports.prototype['replyRequest'] = undefined;
+ /**
+ * When messages are queued up for a number, then it is possible to set where a new message will be placed in the queue. If the priority is set to true then the new message will be placed ahead of all messages with a normal priority. If there are no messages queued for the number, then this parameter has no effect.
+ * @member {Boolean} priority
+ */
+ exports.prototype['priority'] = undefined;
diff --git a/src/model/Status.js b/src/model/Status.js
index 96bd51e..6380e86 100644
--- a/src/model/Status.js
+++ b/src/model/Status.js
@@ -1,13 +1,13 @@
/**
* Telstra Messaging API
- * The Telstra SMS Messaging API allows your applications to send and receive SMS text messages from Australia's leading network operator. It also allows your application to track the delivery status of both sent and received SMS messages.
+ * # Introduction Send and receive SMS and MMS messages globally using Telstra’s enterprise grade Messaging API. It also allows your application to track the delivery status of both sent and received messages. Get your dedicated Australian number, and start sending and receiving messages today. # Features The Telstra Messaging API provides the features below.
| Feature | Description |
|---|---|
Dedicated Number | Provision a mobile number for your account to be used as from address in the API |
Send Messages | Sending SMS or MMS messages |
Receive Messages | Telstra will deliver messages sent to a dedicated number or to the notifyURL defined by you |
Broadcast Messages | Invoke a single API to send a message to a list of number provided in to |
Delivery Status | Query the delivery status of your messages |
Callbacks | Provide a notification URL and Telstra will notify your app when messages status changes |
Alphanumeric Identifier | Differentiate yourself by providing an alphanumeric string in from. This feature is only available on paid plans |
Concatenation | Send messages up to 1900 characters long and Telstra will automaticaly segment and reassemble them |
Reply Request | Create a chat session by associating messageId and to number to track responses received from a mobile number. We will store this association for 8 days |
Character set | Accepts all Unicode characters as part of UTF-8 |
Bounce-back response | See if your SMS hits an unreachable or unallocated number (Australia Only) |
Queuing | Messaging API will automatically queue and deliver each message at a compliant rate. |
Emoji Encoding | The API supports the encoding of the full range of emojis. Emojis in the reply messages will be in their UTF-8 format. |
Client key and Client secret as these will be needed to provision a number for your application and for authentication. Now head over to Getting Started where you can find a postman collection as well as some links to sample apps and SDKs to get you started.
Happy Messaging! # Getting Started
Below are the steps to get started with the Telstra Messaging API.
Client key and Client secret.
notifyURL, when the message has been delivered the API will make a call to this URL to advise of the message status. If this is not provided then you can make use the Get Replies API to poll for messages.GET /sms API get the latest replies to the message.{ to: '+61418123456' sentTimestamp: '2017-03-17T10:05:22+10:00' receivedTimestamp: '2017-03-17T10:05:23+10:00' messageId: /cccb284200035236000000000ee9d074019e0301/1261418123456 deliveryStatus: DELIVRD } | Field | Description |
|---|---|
to | The number the message was sent to. |
receivedTimestamp | Time the message was sent to the API. |
sentTimestamp | Time handling of the message ended. |
deliveryStatus | The final state of the message. |
messageId | The same reference that was returned when the original message was sent. |
receivedTimestamp | Time the message was sent to the API. |
{ \"status\": \"RECEIVED\" \"destinationAddress\": \"+61418123456\" \"senderAddress\": \"+61421987654\" \"message\": \"Foo\" \"sentTimestamp\": \"2018-03-23T12:10:06+10:00\" } | Field | Description |
|---|---|
status | The final state of the message. |
destinationAddress | The number the message was sent to. |
senderAddress | The number the message was sent from. |
message | The sontent of the SMS reply. |
sentTimestamp | Time handling of the message ended. |
{ \"status\": \"RECEIVED\", \"destinationAddress\": \"+61418123456\", \"senderAddress\": \"+61421987654\", \"subject\": \"Foo\", \"sentTimestamp\": \"2018-03-23T12:15:45+10:00\", \"envelope\": \"string\", \"MMSContent\": [ { \"type\": \"application/smil\", \"filename\": \"smil.xml\", \"payload\": \"string\" }, { \"type\": \"image/jpeg\", \"filename\": \"sample.jpeg\", \"payload\": \"string\" } ] } | Field | Description |
|---|---|
status | The final state of the message. |
destinationAddress | The number the message was sent to. |
senderAddress | The number the message was sent from. |
subject | The subject assigned to the message. |
sentTimestamp | Time handling of the message ended. |
envelope | Information about about terminal type and originating operator. |
MMSContent | An array of the actual content of the reply message. |
type | The content type of the message. |
filename | The filename for the message content. |
payload | The content of the message. |