Two Way Message

Overview

Obtain the MT response to a given MO. The real MT will not be delivered to the specified mobile number.

URL

Http access method: POST

Parameters on the following URL are inside braces { }

{base_url}/rest/api/twoWayMessage/{instanceId}/{publicKey}/{signature}

Parameter Name	Description
instanceId	An instance id is the workspace identification number, if you don't know yours please request it using our ticketing tool, you will need to provide your Mobile Engagement Campaign Manager's URL and your user login
Json POST	Values to fire the message. Learn more about the Fire message Descriptor file
publicKey	The public key to access this API. if you don't know yours please request it using our ticketing tool, you will need to provide your Mobile Engagement Campaign Manager's URL and your user login
signature	The unique SHA256 signature for this call, it's involve all input parameters. To learn about generating the correct signature please visit our Java Example

Response

The Response XML is divided in a static part and a dynamic one, we call it dynamic because it will vary depending on the method you invoke. Please read our Response XML Basics section if you want to learn more about the response parts.

<response>
 <input>twoWayMessage</input>
 <status>OK</status>
 <description>Completed</description>
 <result>
  <mtSent>
   <from>dummy</from>
   <mobilenumber>1200000001</mobilenumber>
   <text>Hello there</text>
  </mtSent>
 </result>
</response>