~~NOTOC~~
====== 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 [[misc:otto|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 [[sdk:fire_message_json|Fire message Descriptor]] file |
| publicKey | The public key to access this API. //if you don't know yours please request it using our [[misc:otto|ticketing tool]], you will need to provide your Mobile Engagement Campaign Manager's URL and your user login// |
| signature | The unique [[restapi:appx_ciphering#SHA256 - Cipher|SHA256]] signature for this call, it's involve all input parameters. To learn about generating the correct signature please visit our [[restapi:appx_call_ex|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 [[restapi:appx_resp_xml|Response XML Basics]] section if you want to learn more about the response parts.
twoWayMessage
OKCompleteddummy1200000001Hello there