The purpose of the Conversion web api is to enable the third party to deliver conversion details per message to CM.
A conversion is a confirmation by a third party that their end-user has used the contents of the sms/voice/push message that was processed by CM.
Credentials will be provided by your account manager
Every request will get an HTTP response with status 200 -OK. If the request was correct, the response will be empty. If the authorization failed the HTTP response will have status 401. General errors or internal issues will have status 500 or 503 in its response.
The interface expects a valid XML document to be posted. This XML document should be encoded in UTF-8. The values within the document elements should be XML encoded.
Every request will get an HTTP response with status 200 -OK. If the request was correct, the response will be empty. If the request was incorrect or malformed, the HTTP response will have status 401 – Unauthorized or status 500 – Internal Server Error.
|Customer||True||Numeric||Unique client ID (provided by CM).|
|login||True||Alphanumeric||Login name (provided by CM).|
|Password||True||Alphanumeric||Password (provided by CM).|
|Reference||True*||Alphanumeric||Unique ID of the sms/voice/push message that was processed by CM|
|Msisdn||True*||Numeric||Recipient mobile number in international format with 00 prefix. Example: 0031612345678|
|ConvertedTimestamp||False||DateTime (UTC)||Moment of confirmed code by end user in UTC. Format: hh:mm:ss%20yy/mm/dd Example: 12:28:17%2014/08/20|
*At least one of the fields is required to be filled. If available, post both the Reference and Msisdn