SMS Aggregation - API Documentation

Size: px
Start display at page:

Download "SMS Aggregation - API Documentation"

Transcription

1 SMS Aggregation - API Documentation Wireless Logic Version Issue Date - 20th February 2014 Wireless Logic Ltd Grosvenor House Horseshoe Crescent Beaconsfield, Buckinghamshire HP9 1LJ Tel: +44 (0) Web :

2 Section 1. Wireless Logic Quality Control 1.1 Document Properties Client Assignment Document Title Wireless Logic Reference Client Reference Document Status Wireless Logic SMS Aggregation API Documentation None None Working Draft 1.2 Version History Author Date Version Paul Mansell 19th December Paul Mansell 27th February Matt Thomas 14th March Paul Mansell 20th February Company Confidential Page 2

3 Section 2. Contents Section 1. Wireless Logic Quality Control Document Properties Version History... 2 Section 2. Contents... 3 Section 3. Overview... 4 Section 4. Mobile Terminated Messages SOAP Request REST Request... 9 Section 5. Delivery receipt SOAP API REST API Section 6. Mobile Originated Messages SOAP API REST API Section 7. Testing Section 8. Code examples Sending an SMS SOAP REST Sending a wake-up message SOAP REST Receiving a Delivery Receipt SOAP REST Receiving an SMS SOAP REST Company Confidential Page 3

4 Section 3. Overview The Wireless Logic SMS API allows SMS messages to be sent to and from mobile devices. Sending a message to a mobile device, which is called a Mobile Terminated (MT) message, involves a simple request to the Wireless Logic API. The option of receiving a delivery receipt is also available for MT messages. Receiving a message from a mobile device, which is called a Mobile Originated (MO) message, requires you to create an API that you host to receive requests from the Wireless Logic SMS API. The following diagram shows you this in more detail All communication with the Wireless Logic SMS API must use Transport Layer Security (TLS) to ensure that network communication is encrypted. Details and examples of the above follow in this document. For further help please contact Wireless Logic on support@wirelesslogic.com. Company Confidential Page 4

5 Section 4. Mobile Terminated Messages Sending an SMS to a mobile device requires a call to the Wireless Logic SMS API. The API supports SOAP and REST request formats, with the REST request allowing both XML and JSON data formats. To make a call to the API you need to include a user Id and password these will be provided when you register to use the API. The API supports sending an SMS message using the send method and sending a wake-up message using the wakeup method. The Wireless Logic SMS API will respond to your API call by immediately returning either a success or failure result this is to indicate whether or not the message has been sent. To receive notification regarding the delivery status of that message you can implement a delivery receipt API and receive notification when the message either expires or is delivered. This is covered later in this section. Each of the requests to the Wireless Logic SMS API allow flexibility in identifying the recipient of the SMS Message by allowing you to specify either an ICCID, IMSI or MSISDN. Please note that when specifying the MSDISN it should include both the country code and subscriber number, for example for a UK SIM. The following sections give details on how to connect to the SMS API and what information should be sent and what you should expect to receive in response. 4.1 SOAP Request The Wireless Logic SMS API supports SOAP and supplies a Web Services Description Language (WSDL) file for easy interaction. The WSDL is available at There are 3 SOAP functions available - SendWakeup, which sends a wake-up message in the form of an SMS to the mobile device, SendSMS which sends a Text SMS message to a mobile device and SendBinarySMS which sends a Binary SMS Message to a mobile device. Currently the SendWakeup request is only available on SIMs using the Vodafone Global network. The WSDL and the calls to the functions defined within the WSDL require HTTP Basic Authentication using the user id and password you have been supplied Company Confidential Page 5

6 The SOAP Body for the SendSMS function must contain the following parameters ident Identification e.g. Mobile phone number (MSISDN) / IMSI or String ICCID identtype The type of the ident. Options are IMSI, MSISDN or ICCID String IMSI message The message text to send. Limited to 160 characters String Text Message messageid A correlation Id this will be included on the response and String 1234 on delivery receipts should you wish to enable this feature inbox Optional the inbox name you want replies sent to String inboxname The response from the SendSMS function is Status If the execution was successful or not. True or Boolean True False is returned. statusmessage If status is false then this will contain error information String Unable to find MSISDN messageid The correlation id from the request String 1234 The SOAP Body for the SendBinarySMS function must contain the following parameters ident Identification e.g. Mobile phone number (MSISDN) / String IMSI or ICCID identtype The type of the ident. Options are IMSI, MSISDN or String IMSI ICCID udh The User Data Header in HEX format d10000 message The message text to send in HEX format. Limited to 140 String 0B747A6163 characters messageid A correlation Id this will be included on the response String 1234 and on delivery receipts should you wish to enable this feature inbox Optional the inbox name you want replies sent to String inboxname The response from the SendBinarySMS function is Status If the execution was successful or not. True or Boolean True False is returned. statusmessage If status is false then this will contain error information String Unable to find MSISDN messageid The correlation id from the request String 1234 The SOAP Body for the SendWakeup function must contain the following parameters Ident Identification e.g. mobile phone number (MSISDN) / IMSI or String ICCID identtype The type of the ident. Options are IMSI, MSISDN or ICCID String IMSI messageid A correlation Id this will be included on the response String 1234 Company Confidential Page 6

7 The response from the SendWakeup function is Status If the execution was successful or not. True or Boolean True False is returned. statusmessage If status is false then this will contain error information String Unable to find MSISDN messageid The correlation id from the request String 1234 Company Confidential Page 7

8 The following SOAP request example sends an SMS to a mobile device <soapenv:envelope xmlns:soapenv=" xmlns:con=" <soapenv:header> </soapenv:header> <soapenv:body> <con:sendsms> <SendSMSRequest> <ident> </ident> <identtype>imsi</identtype> <message>test Message</message> <messageid>1</messageid> </SendSMSRequest> </con:sendsms> </soapenv:body> </soapenv:envelope> The above would send the message Test Message to a mobile device using a SIM with the IMSI of The response would be <SOAP-ENV:Envelope xmlns:soap-env=" xmlns:ns1=" <SOAP-ENV:Body> <ns1:sendsmsresponse> <return> <status>true</status> <messageid>1</messageid> </return> </ns1:sendsmsresponse> </SOAP-ENV:Body> </SOAP-ENV:Envelope> The above response shows a successful SMS message being sent (status = true) and the message Id from the request. There are code examples showing how to use the Wireless Logic SMS API available in the Code Examples section at the end of this document Company Confidential Page 8

9 4.2 REST Request The Wireless Logic SMS API supports both XML and JSON request formats for REST requests, the response format will be in the same format as the request. There are 3 REST functions available - wakeup, which sends a wake-up message in the form of an SMS to the mobile device, send which sends a Text SMS message to a mobile device and send_binary which sends a Binary SMS message to a mobile device. Currently the wakeup function is only available on SIMs using the Vodafone Global network. The URL for REST requests is For example to send an SMS message using a JSON request format the URL would be The REST API requires you to authenticate using HTTP Basic Authentication using the user id and password supplied by Wireless Logic. A send request must contain the following parameters ident Identification e.g. Mobile phone number (MSISDN) / IMSI or String ICCID identtype The type of the ident. Options are IMSI, MSISDN or ICCID String IMSI message The message text to send. Limited to 160 characters String Text Message messageid A correlation Id this will be included on the response and String 1234 on the delivery receipt if you enable this feature inbox Optional the inbox name you want replies sent to String inboxname The response to a send request will contain the following parameters Status If the execution was successful or not. True or Boolean True False is returned. statusmessage If status is false then this will contain error information String Unable to find MSISDN messageid The correlation id from the request String 1234 A send_binary request must contain the following parameters ident Identification e.g. Mobile phone number (MSISDN) / String IMSI or ICCID identtype The type of the ident. Options are IMSI, MSISDN or String IMSI ICCID udh The User Data Header in HEX format d10000 message The message text to send in HEX format. Limited to 140 String 0B747A6163 characters messageid A correlation Id this will be included on the response String 1234 Company Confidential Page 9

10 and on the delivery receipt if you enable this feature inbox Optional the inbox name you want replies sent to String inboxname The response to a send_binary request will contain the following parameters Status If the execution was successful or not. True or Boolean True False is returned. statusmessage If status is false then this will contain error information String Unable to find MSISDN messageid The correlation id from the request String 1234 Company Confidential Page 10

11 The request to the wakeup function must contain the following parameters Ident Identification e.g. mobile phone number (MSISDN) or IMSI String identtype The type of the ident. Options are IMSI, MSISDN or ICCID String IMSI messageid A correlation Id this will be included on the response String 1234 The response parameters from the wakeup request are Status If the execution was successful or not. True or Boolean True False is returned. statusmessage If status is false then this will contain error information String Unable to find MSISDN messageid The correlation id from the request String 1234 The following JSON example sends an SMS to a mobile device "ident": " ", "identtype": "imsi", "message": "Test Message", "messageid": "1" This would send the message Test Message to the mobile device with a SIM having an IMSI of The response would be "status": true, "status_message": "", "message_id": "1" The above response shows a successful SMS message being sent (status = true) and the message Id from the request. Company Confidential Page 11

12 The equivalent XML request would be <?xml version="1.0" encoding="utf-8"?> <document> <ident> </ident> <identtype>imsi</identtype> <message>test Message</message> <messageid>1</messageid> </document> The response would be <?xml version="1.0" encoding="utf-8"?> <result> <status>true</status> <status_message> <![CDATA[]]> </status_message> <message_id> <![CDATA[1]]> </message_id> </result> There are code examples showing how to use the Wireless Logic SMS API available in the Code Examples section at the end of this document Company Confidential Page 12

13 Section 5. Delivery receipt The Wireless Logic SMS API will respond to your API call by immediately returning either a success or failure result this is to indicate whether or not the message has been sent. To receive notification regarding the delivery status of that message you can implement a delivery receipt API and receive notification when the message either expires or is delivered. The details of your API (format accepted and URL details) will be agreed when your setup your agreement with Wireless Logic to use the SMS API. We currently support making a SOAP or REST (XML or JSON data format) request to your API. The following sections details how the call will be made to your API and what data you can expect to receive SOAP API If you wish to receive delivery receipts to your SOAP API you must accept a SOAP request for the method DeliveryReceipt that contains a WLAuth object within the SOAP Header with the following userid Userid* String User password Password* String Pass *These parameters will be agreed upon setup of the SMS API. And a SOAP Body containing a DeliveryReceiptRequest object with the following parameters messageid The correlation Id you specified when sending the message String 1234 status The status of the message either delivered or expired String delivered Your API must respond with the following DeliveryReceiptResponse object Status If the execution was successful or not. True or Boolean True False is returned. statusmessage If status is false then this will contain error information String Unable to process request If your API responds with a status of false then the request will be attempted up to a maximum of 3 times, first after 1 minute then after 5 minutes and then finally after 30 minutes of the original request. Company Confidential Page 13

14 An example SOAP request sent to your API would be <soapenv:envelope xmlns:soapenv=" xmlns:con=" <soapenv:header> <WLAuth> <userid>user</userid> <password>pass</password> </WLAuth> </soapenv:header> <soapenv:body> <con:deliveryreceipt> <DeliveryReceiptRequest> <messageid>1234</ messageid > <status>delivered</ status > </ DeliveryReceiptRequest > </con: DeliveryReceipt > </soapenv:body> </soapenv:envelope> An example response would be <SOAP-ENV:Envelope xmlns:soap-env=" xmlns:ns1=" <SOAP-ENV:Body> <ns1: DeliveryReceiptResponse> <return> <status>true</status> <statusmessage/> </return> </ns1: DeliveryReceiptResponse> </SOAP-ENV:Body> </SOAP-ENV:Envelope> The code examples section contains an example SOAP Server for receiving and responding to requests from the Wireless Logic SMS API REST API If you wish to receive delivery receipts to your REST API you must accept either JSON or XML within the request body. All transactions from the Wireless Logic SMS API will be sent using an HTTP POST. The request from the Wireless Logic SMS API will contain the following elements. WLAuth element with the following parameters userid Userid* String User password Password* String Pass *These parameters will be agreed upon setup of the SMS API. Company Confidential Page 14

15 And the following POST data messageid The correlation Id you specified when sending the message String 1234 status The status of the message either delivered or expired String delivered A response must be sent back to the Wireless Logic SMS API and must contain the following status If the execution was successful or not. True or Boolean True False is returned. statusmessage If status is false then this will contain error information String Unable to process request If your API responds with a status of false then the request will be attempted up to a maximum of 3 times, first after 1 minute then after 5 minutes and then finally after 30 minutes of the original request. An example JSON request sent to your API would be "wlauth": "userid": "user", "password": "pass", "messageid": "1234", "status": "delivered" With the expected response of "status": true, "statusmessage": "" And an example XML request sent to your API would be <?xml version="1.0" encoding="utf-8"?> <document> <wlauth> <userid>user</userid> <password>pass</password> </wlauth> <messageid>1234</ messageid > <status>delivered</status> </document> Company Confidential Page 15

16 With the expected response of <?xml version="1.0" encoding="utf-8"?> <result> <status>true</status> <statusmessage> <![CDATA[]]> </statusmessage> </result> The code examples section contains an example for receiving and responding to REST requests from the Wireless Logic SMS API. Company Confidential Page 16

17 Section 6. Mobile Originated Messages Mobile Originated (MO) messages are SMS messages that are sent from a mobile device to the Wireless Logic SMS API, the SMS API will then log the request and make a call to your API. The Wireless Logic SMS API supports SOAP and REST calls to your API. The details of your API (format accepted and URL details) will be agreed when your setup your agreement with Wireless Logic to use the SMS API. We currently support making a SOAP or REST (XML or JSON data format) request to your API. To enable the Wireless Logic SMS API to make the call to your API you need to setup your API to accept a request and send a response that matches the parameters detailed below. 6.1 SOAP API If you wish to receive MO messages to your SOAP API you must accept a SOAP request for the method SendSMS that contains a WLAuth object within the SOAP Header with the following userid Userid* String User password Password* String Pass *These parameters will be agreed upon setup of the SMS API. And a SOAP Body containing a SMSRequest object with the following parameters ident Identification e.g. Mobile phone number (MSISDN) String or IMSI identtype The type of the ident. Options are IMSI, MSISDN or String IMSI ICCID message The message text sent this will be base64 encoded String VGVzdCBNZXNzYWdl Your API must respond with the following SMSResponse object Status If the execution was successful or not. True or Boolean True False is returned. statusmessage If status is false then this will contain error information String Unable to find MSISDN If your API responds with a status of false then the request will be attempted up to a maximum of 3 times, first after 1 minute then after 5 minutes and then finally after 30 minutes of the original request. An example SOAP request sent to your API would be <soapenv:envelope xmlns:soapenv=" xmlns:con=" <soapenv:header> Company Confidential Page 17

18 <WLAuth> <userid>user</userid> <password>pass</password> </WLAuth> </soapenv:header> <soapenv:body> <con:sendsms> <SMSRequest> <ident> </ident> <identtype>imsi</identtype> <message>vgvzdcbnzxnzywdl</message> </SMSRequest> </con:sendsms> </soapenv:body> </soapenv:envelope> An example response would be <SOAP-ENV:Envelope xmlns:soap-env=" xmlns:ns1=" <SOAP-ENV:Body> <ns1:sendsmsresponse> <return> <status>true</status> <statusmessage/> </return> </ns1:smsresponse> </SOAP-ENV:Body> </SOAP-ENV:Envelope> The code examples section contains an example SOAP Server for receiving and responding to requests from the Wireless Logic SMS API. 6.2 REST API If you wish to receive MO messages to your REST API you must accept either JSON or XML within the request body. All transactions from the Wireless Logic SMS API will be sent using an HTTP POST. The request from the Wireless Logic SMS API will contain the following elements. WLAuth element with the following parameters Company Confidential Page 18

19 Userid Userid* String User password Password* String Pass *These parameters will be agreed upon setup of the SMS API. And the following POST data Ident Identification e.g. Mobile phone number (MSISDN) / String IMSI or ICCID identtype The type of the ident. Options are IMSI, MSISDN or String IMSI ICCID message The message text sent this will be base64 encoded String VGVzdCBNZXNzYWdl A response must be sent back to the Wireless Logic SMS API and must contain the following status If the execution was successful or not. True or Boolean True False is returned. statusmessage If status is false then this will contain error information String Unable to find MSISDN If your API responds with a status of false then the request will be attempted up to a maximum of 3 times, first after 1 minute then after 5 minutes and then finally after 30 minutes of the original request. An example JSON request sent to your API would be "wlauth": "userid": "user", "password": "pass", "ident": " ", "identtype": "imsi", "message": "VGVzdCBNZXNzYWdl" With the expected response of "status": true, "statusmessage": "" Company Confidential Page 19

20 And an example XML request sent to your API would be <?xml version="1.0" encoding="utf-8"?> <document> <wlauth> <userid>user</userid> <password>pass</password> </wlauth> <ident> </ident> <identtype>imsi</identtype> <message>vgvzdcbnzxnzywdl</message> </document> With the expected response of <?xml version="1.0" encoding="utf-8"?> <result> <status>true</status> <statusmessage> <![CDATA[]]> </statusmessage> </result> The code examples section contains an example for receiving and responding to REST requests from the Wireless Logic SMS API. Company Confidential Page 20

21 Section 7. Testing To test the API you can send messages to specific numbers detailed below. These test numbers allow you to test both delivery receipts and MO messages. To enable testing the API you need to send a message to any of the following numbers SendTo Action/Effect Message is received and a delivery receipt is generated with the status of delivered Message is received and a delivery receipt is generated with the status of expired Message is received and a Mobile Originated message is generated the MO message is sent to An example JSON request to generate a delivered delivery receipt would be: "ident": " ", "identtype": "imsi", "message": "Test Message", "messageid": "1" Company Confidential Page 21

22 Section 8. Code examples This section contains code examples for use with the Wireless Logic SMS API 8.1 Sending an SMS The following examples show how to send an SMS message to a mobile device SOAP This example is written in PHP and sends an SMS message to a mobile device using the SOAP interface // init soap client $service = new SoapClient(' // call sendsms and get result $result = $service->sendsms(array( 'ident' => ' ', 'identtype' => 'imsi', 'message' => 'Test Message', 'messageid' => '123' )); // output result if ($result->status) echo "Message sent"; else // output error message echo "Error sending message - ". $result->statusmessage; Company Confidential Page 22

23 8.1.2 REST This example is written in PHP and sends an SMS message to a mobile device using the REST interface using JSON data format // setup parameters $params = array( 'ident' => ' ', 'identtype' => 'imsi', 'message' => 'JSON Test', 'messageid' => '1' ); // setup url $url = ' // json encode params $data_string = json_encode($params); // make request $ch = curl_init($url); curl_setopt($ch, CURLOPT_CUSTOMREQUEST, "POST"); curl_setopt($ch, CURLOPT_POSTFIELDS, $data_string); curl_setopt($ch, CURLOPT_RETURNTRANSFER, true); curl_setopt($ch, CURLOPT_HTTPHEADER, array( 'Content-Type: application/json', 'Content-Length: '. strlen($data_string) ) ); $result = curl_exec($ch); // output result print_r($result); This example is written in PHP and sends an SMS message to a mobile device using the REST interface using XML data format // parameters $params = <<<XML <?xml version="1.0" encoding="utf-8"?> <document> <ident> </ident> <identtype>imsi</identtype> <message>test Message</message> <messageid>1</messageid> </document> XML; // convert string to xml $xml = simplexml_load_string($params); // setup url $url = ' // make request $ch = curl_init($url); curl_setopt($ch, CURLOPT_CUSTOMREQUEST, "POST"); curl_setopt($ch, CURLOPT_POSTFIELDS, $xml->asxml()); curl_setopt($ch, CURLOPT_RETURNTRANSFER, true); curl_setopt($ch, CURLOPT_HTTPHEADER, array( 'Content-Type: application/xml', Company Confidential Page 23

24 'Content-Length: '. strlen($xml->asxml()) ) ); $result = curl_exec($ch); // output result print_r($result); 8.2 Sending a wake-up message The following examples show how to send an SMS message to a mobile device SOAP This example is written in PHP and sends a wake-up message to a mobile device using the SOAP interface // init soap client $service = new SoapClient(' // call sendsms and get result $result = $service->sendwakeup(array( 'ident' => ' ', 'identtype' => 'imsi', 'messageid' => '123' )); // output result if ($result->status) echo "Message sent"; else // output error message echo "Error sending message - ". $result->statusmessage; REST This example is written in PHP and sends a wake-up message to a mobile device using the REST interface and XML data format // parameters $params = <<<XML <?xml version="1.0" encoding="utf-8"?> <document> <ident> </ident> <identtype>imsi</identtype> <messageid>1</messageid> </document> XML; // convert string to xml $xml = simplexml_load_string($params); // setup url $url = ' Company Confidential Page 24

25 // make request $ch = curl_init($url); curl_setopt($ch, CURLOPT_CUSTOMREQUEST, "POST"); curl_setopt($ch, CURLOPT_POSTFIELDS, $xml->asxml()); curl_setopt($ch, CURLOPT_RETURNTRANSFER, true); curl_setopt($ch, CURLOPT_HTTPHEADER, array( 'Content-Type: application/xml', 'Content-Length: '. strlen($xml->asxml()) ) ); $result = curl_exec($ch); // output result print_r($result); Company Confidential Page 25

26 This example is written in PHP and sends a wake-up message to a mobile device using the REST interface and XML data format // setup parameters $params = array( 'ident' => ' ', 'identtype' => 'imsi', 'messageid' => '1' ); // setup url $url = ' // json encode params $data_string = json_encode($params); // make request $ch = curl_init($url); curl_setopt($ch, CURLOPT_CUSTOMREQUEST, "POST"); curl_setopt($ch, CURLOPT_POSTFIELDS, $data_string); curl_setopt($ch, CURLOPT_RETURNTRANSFER, true); curl_setopt($ch, CURLOPT_HTTPHEADER, array( 'Content-Type: application/json', 'Content-Length: '. strlen($data_string) ) ); $result = curl_exec($ch); // output result print_r($result); 8.3 Receiving a Delivery Receipt The following examples show how to receive a delivery receipt from the Wireless Logic SMS API SOAP This example is written in PHP receives a request from the Wireless Logic SMS API and sends back a response // define a class to handle request class MyClass public $user; public $password; public $authenticated = false; // this will process the request public function DeliveryReceipt($DeliveryReceiptRequest) // check authenticated if (!$this->authenticated) $response = new stdclass(); $response->status = false; $response->statusmessage = 'Incorrect User and Pass'; return $response; // Array $DeliveryReceiptRequest gives you access to the incoming data Company Confidential Page 26

27 $messageid = $DeliveryReceiptRequest ->messageid; $status= $DeliveryReceiptRequest->status; // create and response $response = new stdclass(); $response->status = true; $response->statusmessage = ''; return $response; // this function will process the header with the same name public function WLAuth($wlauth) $this->user = $wlauth->userid; $this->password = $wlauth->password; // check if userid / password are correct if ($this->user == 'user' $this->password == 'pass') $this->authenticated = true; // setup SOAPServer and handle request $server = new SOAPServer( NULL, array( 'uri' => ' ) ); // specify the class that will handle request $server->setclass('myclass'); $server->handle(); REST This example is written in PHP receives a request from the Wireless Logic SMS API and sends back a response using the JSON data format // get request body $post_body = file_get_contents('php://input'); // decode json $DeliveryReceiptRequest = json_decode($post_body); // check header If ($DeliveryReceiptRequest ->wlauth->userid!= user && $DeliveryReceiptRequest ->wlauth- >password!= pass) // handle authentication failure // extract values $messageid = $DeliveryReceiptRequest ->messageid; $status = $DeliveryReceiptRequest->status; // create a response $response = array( 'status' => true, 'statusmessage' => '' ); // encode and output echo json_encode($response); Company Confidential Page 27

28 This example is written in PHP receives a request from the Wireless Logic SMS API and sends back a response using the XML data format // get request body $post_body = file_get_contents('php://input'); error_log($post_body); $DeliveryReceiptRequest = simplexml_load_string($post_body); // check header If ($DeliveryReceiptRequest ->wlauth->userid!= user && $DeliveryReceiptRequest ->wlauth- >password!= pass) // handle authentication failure // extract values $messageid = $DeliveryReceiptRequest ->messageid; $status = $DeliveryReceiptRequest->status; // create a response $xml = <<<XML <?xml version="1.0" encoding="utf-8"?> <result> <status>true</status> <statusmessage> <![CDATA[]]> </statusmessage> </result> XML; $response = simplexml_load_string($xml); // encode and output echo $response->asxml(); Company Confidential Page 28

29 8.4 Receiving an SMS The following examples show how to receive an SMS message from the Wireless Logic SMS API SOAP This example is written in PHP receives a request from the Wireless Logic SMS API and sends back a response // define a class to handle request class MyClass public $user; public $password; public $authenticated = false; // this will process the request public function sendsms($smsrequest) // check authenticated if (!$this->authenticated) $response = new stdclass(); $response->status = false; $response->statusmessage = 'Incorrect User and Pass'; return $response; // Array $SMSRequest gives you access to the incoming data $message = base64_decode($smsrequest->message); // create and response $response = new stdclass(); $response->status = true; $response->statusmessage = ''; return $response; // this function will process the header with the same name public function WLAuth($wlauth) $this->user = $wlauth->userid; $this->password = $wlauth->password; // check if userid / password are correct if ($this->user == 'user' $this->password == 'pass') $this->authenticated = true; // setup SOAPServer and handle request $server = new SOAPServer( NULL, array( 'uri' => ' ) ); // specify the class that will handle request $server->setclass('myclass'); $server->handle(); Company Confidential Page 29

30 8.4.2 REST This example is written in PHP receives a request from the Wireless Logic SMS API and sends back a response using the JSON data format // get request body $post_body = file_get_contents('php://input'); // decode json $SMSRequest = json_decode($post_body); // check header If ($SMSRequest->wlauth->userid!= user && $SMSRequest->wlauth->password!= pass) // handle authentication failure // extract values $message = base64_decode($smsrequest->message); // create a response $response = array( 'status' => true, 'statusmessage' => '' ); // encode and output echo json_encode($response); This example is written in PHP receives a request from the Wireless Logic SMS API and sends back a response using the XML data format // get request body $post_body = file_get_contents('php://input'); error_log($post_body); $SMSRequest = simplexml_load_string($post_body); // check header If ($SMSRequest->wlauth->userid!= user && $SMSRequest->wlauth->password!= pass) // handle authentication failure // extract values $message = base64_decode($smsrequest->message); // create a response $xml = <<<XML <?xml version="1.0" encoding="utf-8"?> <result> <status>true</status> <statusmessage> <![CDATA[]]> </statusmessage> </result> XML; $response = simplexml_load_string($xml); // encode and output echo $response->asxml(); Company Confidential Page 30

Connect Media Bulk SMS API Documentation

Connect Media Bulk SMS API Documentation Connect Media Bulk SMS API Documentation All requests are submitted through the POST Method Base URL: http://www.connectmedia.co.ke/user-board/?api Information About Parameters: PARAMETERS username Your

More information

User Guide. Billing Accounts. Version Issue Date - 30th January 2014

User Guide. Billing Accounts.   Version Issue Date - 30th January 2014 User Guide Billing Accounts Version - 1.0 Issue Date - 30th January 2014 Wireless Logic Ltd Grosvenor House Horseshoe Crescent Beaconsfield, Buckinghamshire HP9 1LJ T +44 (0)1494 679 800 www.wirelesslogic.com

More information

User Guide. Customer Documentation. Version Issue Date - 1st August 2014

User Guide. Customer Documentation.  Version Issue Date - 1st August 2014 User Guide Customer Documentation Version - 1.1 Issue Date - 1st August 2014 Wireless Logic Ltd Grosvenor House Horseshoe Crescent Beaconsfield, Buckinghamshire HP9 1LJ T +44 (0)1494 679 800 www.wirelesslogic.com

More information

Objective: Review how to use access the Bulkvs.com Origination and 911 SOAP API using SOAP UI

Objective: Review how to use access the Bulkvs.com Origination and 911 SOAP API using SOAP UI Objective: Review how to use access the Bulkvs.com Origination and 911 SOAP API using SOAP UI Perquisites: 1. Have access to your bulkvs.com API ID 2. Have an MD5 equivalent of your bllkvs.com password

More information

ARTIO SMS Services HTTP API Documentation

ARTIO SMS Services HTTP API Documentation ARTIO SMS Services HTTP API Documentation David Jozefov Michal Unzeitig Copyright 2013 - ARTIO International Co. ARTIO SMS Services HTTP API Documentation ARTIO Publication date: 4.9.2013 Version: 1.0.1

More information

The contents of this publication the specifications of this application are subject to change without notice.

The contents of this publication the specifications of this application are subject to change without notice. V.1.0. Publication Notice The contents of this publication the specifications of this application are subject to change without notice. GFI Software reserves the right to make changes without notice to

More information

API Spec Sheet For Version 2.5

API Spec Sheet For Version 2.5 INTRODUCTION The Wholesale SMS API is ideally suited for sending individual sms messages and/or automated responses through our premium routes. To send bulk messages through the API you can set your server

More information

API Spec Sheet For HLR v1.4

API Spec Sheet For HLR v1.4 API Spec Sheet For HLR v1.4 INTRODUCTION The Wholesale SMS HLR API provides an easy to use method of accessing the HLR (Home Location Register) for all networks worldwide that support HLR. For large batch

More information

Integration REST Text2Speech Version 1.1

Integration REST Text2Speech Version 1.1 1 Integration REST Text2Speech Version 1.1 2 Table of Contents Introduction P. 3 Technical Platform Request for shipments voicemails P. 4 JSON request P. 4 Example request CURL P. 5 Sample PHP request

More information

API USER GUIDE MARKETING MESSAGES & BROADCASTS

API USER GUIDE MARKETING MESSAGES & BROADCASTS API USER GUIDE MARKETING MESSAGES & BROADCASTS General Overview So, what do you want to do? 3 3 Marketing Messages with replies 4 First, let s send the messages Advanced API developers note Next, let s

More information

Messaging Service REST API Specification V2.3.2 Last Modified: 07.October, 2016

Messaging Service REST API Specification V2.3.2 Last Modified: 07.October, 2016 Messaging Service REST API Specification V2.3.2 Last Modified: 07.October, 2016 page 1 Revision history Version Date Details Writer 1.0.0 10/16/2014 First draft Sally Han 1.1.0 11/13/2014 Revised v.1.1

More information

LINK Mobility SMS REST API MT and Delivery Reports Version 1.3; Last updated September 21, 2017

LINK Mobility SMS REST API MT and Delivery Reports Version 1.3; Last updated September 21, 2017 LINK Mobility SMS REST API MT and Delivery Reports Version 1.3; Last updated September 21, 2017 For help, contact support@linkmobility.com The most up-to-date version of this document is available at http://www.linkmobility.com/developers/

More information

Oracle. Field Service Cloud Integrating with Outbound API 18A

Oracle. Field Service Cloud Integrating with Outbound API 18A Oracle Field Service Cloud 18A Part Number: E92187-01 Copyright 2018, Oracle and/or its affiliates. All rights reserved Authors: The Field Service Cloud Information Development Team This software and related

More information

Sending Job Requsition Data to Tenstreet API Guide (rev 09/2018)

Sending Job Requsition Data to Tenstreet API Guide (rev 09/2018) Sending Job Requsition Data to Tenstreet API Guide (rev 09/2018) Contents Introduction... 1 Agreements and Acknowledgements... 2 Understanding the API... 2 Debugging... 2 Logging... 2 Data Accuracy...

More information

Sending Documents to Tenstreet API Guide (rev 06/2017)

Sending Documents to Tenstreet API Guide (rev 06/2017) Sending Documents to Tenstreet API Guide (rev 06/2017) Contents Introduction... 1 Agreements and Acknowledgements... 2 Understanding the API... 2 Debugging... 2 Logging... 2 Data Accuracy... 2 Support

More information

REST SERVICE. Web Services API Version 1.5

REST SERVICE. Web Services API Version 1.5 REST SERVICE Web Services API Version 1.5 The information contained within this document is the property of PageOne Communications Ltd and may not be copied used or disclosed in whole or in part, except

More information

WebADM and OpenOTP are trademarks of RCDevs. All further trademarks are the property of their respective owners.

WebADM and OpenOTP are trademarks of RCDevs. All further trademarks are the property of their respective owners. API The specifications and information in this document are subject to change without notice. Companies, names, and data used in examples herein are fictitious unless otherwise noted. This document may

More information

Sending Data Updates to Tenstreet API Guide (rev 10/2017)

Sending Data Updates to Tenstreet API Guide (rev 10/2017) Sending Data Updates to Tenstreet API Guide (rev 10/2017) Contents Introduction... 1 Agreements and Acknowledgements... 2 Understanding the API... 2 Debugging... 2 Logging... 2 Data Accuracy... 2 Support

More information

IUID Registry Application Programming Interface (API) Version Software User s Manual (SUM)

IUID Registry Application Programming Interface (API) Version Software User s Manual (SUM) IUID Registry Application Programming Interface (API) Version 5.11 Software User s Manual (SUM) Document Version 5.11 January 04, 2016 Prepared by: CACI 50 N Laura Street Jacksonville FL 32202 Prepared

More information

City/Zip Lookup Web Service Implementation Guide Version 1.00

City/Zip Lookup Web Service Implementation Guide Version 1.00 City/Zip Lookup Web Service Implementation Guide Version 1.00 Revised: 10/04/2016 SECTION 1 - NARRATIVE... 1 SECTION 2 - INPUT PARAMETERS... 2 SECTION 3 - OUTPUT PARAMETERS... 3 SECTION 4 - SOAP XML EXAMPLES...

More information

We currently are able to offer three different action types:

We currently are able to offer three different action types: SMS Inbound Introduction SMS Inbound provides a simple to use interface for receiving inbound MMS messages. Inbound Message Actions Inbound Message Actions in SMS Inbound are things that our system can

More information

2. On completing your registration you will get a confirmation . Click on the link or paste the link into your browser to validate the account.

2. On completing your registration you will get a confirmation  . Click on the link or paste the link into your browser to validate the account. Bongo Live SMS API v1.4 Revision History: v 1.1 - Initial Release. v1.2 19/6/2013 - Added Balance check and Sender Name Check v1.3 15/10/2013 Added incoming sms specifications v1.4 13/05/2014 Added API

More information

InstaMember USER S GUIDE

InstaMember USER S GUIDE InstaMember USER S GUIDE InstaMember Licensing API Guide 1 InstaMember Licensing API Guide The InstaMember licensing feature is designed to integrate seamlessly with your web applications or scripts. It

More information

Revision: 50 Revision Date: :43 Author: Oliver Zabel. GTX Mobile Messaging SMS Gateway Interface Simple HTTP API Manual

Revision: 50 Revision Date: :43 Author: Oliver Zabel. GTX Mobile Messaging SMS Gateway Interface Simple HTTP API Manual Revision: 50 Revision Date: 09.06.17 14:43 Author: Oliver Zabel GTX Mobile Messaging SMS Gateway Interface Simple HTTP API Manual Table of Contents Table of Contents... 2 Introduction... 3 Sending SMS...

More information

Real-Time Claim Adjudication and Estimation Connectivity Specifications

Real-Time Claim Adjudication and Estimation Connectivity Specifications Real-Time Claim Adjudication and Estimation Connectivity Specifications Mountain State Blue Cross Blue Shield June 18, 2009 Contents 1. Real-Time Overview 2. Connectivity Requirements 3. SOAP Request Message

More information

NEMSIS V3 Performance Measure Service Technical Guide

NEMSIS V3 Performance Measure Service Technical Guide NEMSIS TAC Whitepaper NEMSIS V3 Performance Measure Service Technical Guide Date June 1, 2017 Authors Joshua Legler NEMSIS Consultant Subhadeep Nag NEMSIS Software Design Engineer N. Clay Mann NEMSIS P.I.

More information

Version Date Description Author First version Nate. send_sms request Added DELIVERED. status in Send Sms.

Version Date Description Author First version Nate. send_sms request Added DELIVERED. status in Send Sms. New API Version Date Description Author 0.1 2014-12-25 First version Nate 0.2 2015-1-22 Added user_id in Nate send_sms request 0.3 2015-3-20 Added DELIVERED Nate status in Send Sms Result 0.4 2015-4-24

More information

API. If you already done integration with Btc-e.com previously, it will be very easy task to use our API.

API. If you already done integration with Btc-e.com previously, it will be very easy task to use our API. API Documentation Link : https://vip.bitcoin.co.id/trade api Our API is very similar with BTC-e s API. If you already done integration with Btc-e.com previously, it will be very easy task to use our API.

More information

Sending Application Data to Tenstreet API Guide

Sending Application Data to Tenstreet API Guide Sending Application Data to Tenstreet API Guide Contents Introduction... 1 Agreements and Acknowledgements... 2 Understanding the API... 2 Debugging... 2 Logging... 2 Data Accuracy... 2 Support Requests...

More information

Reqs-LTE-SMS. Device Requirements Issued: Mar-16

Reqs-LTE-SMS. Device Requirements Issued: Mar-16 Reqs-LTE-SMS Device Requirements Issued: Mar-16 This document provides initial information related to Verizon Wireless Long Term Evolution (LTE) Reqs-LTE- SMS requirement document. All information herein

More information

Introduction to the Cisco ANM Web Services API

Introduction to the Cisco ANM Web Services API 1 CHAPTER This chapter describes the Cisco ANM Web Services application programming interface (API), which provides a programmable interface for system developers to integrate with customized or third-party

More information

SMS Gateway. API & Application Technical Documentation. Revision 1. Current as at 10 th August Document ID: DOC-SMS-API-R1

SMS Gateway. API & Application Technical Documentation. Revision 1. Current as at 10 th August Document ID: DOC-SMS-API-R1 SMS Gateway API & Application Technical Documentation Revision 1 Current as at 10 th August 2010 Document ID: DOC-SMS-API-R1 Information in this document is subject to change without notice. This document

More information

Issue No. Date Description of Changes Initial issue Added basic authentication

Issue No. Date Description of Changes Initial issue Added basic authentication Department: Subject: IT API Documentation Revision History: Issue No. Date Description of Changes 1.0 04.18.17 Initial issue 1.1 05.11.17 Added basic authentication Related Documents: Page 1 of 28 Classification

More information

Recharge API Document

Recharge API Document Recharge API Document API Methods 1. GetBalance 2. MobileRecharge 3. DTHRecharge 4. PostPaidBillPay 5. GetTransactionStatus 6. ChangeSMSPin 7. ComplaintRegister API URL http:// DomainName /mrechargeapi/service.asmx

More information

SMS API User Guide. Document Reference: October Version: 6

SMS API User Guide. Document Reference: October Version: 6 SMS API User Guide Document Reference: 8297 October 2016 Version: 6 Version Date Author Changes Number 1 Apr 2015 John Lindsay 2 Sep 2015 Sam Smith Branding updated USSD section added Postman updated 3

More information

API Integration Guide

API Integration Guide API Integration Guide Introduction SULU Mobile Solutions API is a programmable SMS message service. It enables your in-house applications to have fully featured SMS capabilities using your favorite programming

More information

Lab 3: Simple Integration Use Case

Lab 3: Simple Integration Use Case Exercise 1 : Create the web service...2 Exercise 2 : Deploy the web service...4 Exercise 3 : Test the service...8 1/16 In this exercise, you will learn how to activate a Maximo inbound web service. This

More information

Industry Training Register. Guide to integration for ITOs

Industry Training Register. Guide to integration for ITOs Industry Training Register Guide to integration for ITOs Version 5.0 Objective id A823307 Published 15 January 2013 Page 2 of 29 ITR guide to integration for ITOs Contents 1 INTRODUCTION... 4 1.1 About

More information

Real-Time Connectivity Specifications

Real-Time Connectivity Specifications Real-Time Connectivity Specifications United Concordia Companies, Inc. (UCCI) 2006 Contents 1. Real-Time Overview 2. Requirements 3. SOAP Messages 4. SOAP Faults 5. UCCI EDI WebServices Certificate 1.

More information

SMS HTTP API DOCUMENTATION December 2012

SMS HTTP API DOCUMENTATION December 2012 SMS HTTP API DOCUMENTATION December 2012 TABLE OF CONTENTS 1.0) INTRODUCTION 3 2.0) SENDING NORMAL TEXT MESSAGES 4 3.0) SENDING UNICODE (UCS2) MESSAGES (MULTILINGUAL) 5 4.0) SENDING UDH HEADER MESSAGES

More information

Cisco Encryption

Cisco  Encryption This chapter contains the following sections: Overview of, page 1 How to Encrypt Messages with a Local Key Server, page 2 Encrypting Messages using the Email Security Appliance, page 3 Determining Which

More information

SMSCenter. SMSCenter API

SMSCenter. SMSCenter API www.smscenter.co.il SMSCenter Multi Messaging Software Server SMS / MMS / IVR / WAP Push SMSCenter API SMSCenter API The software described in this book is furnished under a license agreement and may be

More information

All requests must be authenticated using the login and password you use to access your account.

All requests must be authenticated using the login and password you use to access your account. The REST API expects all text to be encoded as UTF-8, it is best to test by sending a message with a pound sign ( ) to confirm it is working as expected. If you are having issues sending as plain text,

More information

SOAP API. The correct URL has been hidden. Please contact your account manager for the full URL information.

SOAP API. The correct URL has been hidden. Please contact your account manager for the full URL information. SMS Help Guides TNZ Group Limited sales@tnz.co.nz +64 9 9293000 +64 9 522 8839 SOAP API SOAP is a simple way of sending SMS/TXT messages via the internet. It is a great solution for integration into existing

More information

SONERA OPERATOR SERVICE PLATFORM OPAALI PORTAL SMS. FREQUENTLY ASKED QUESTIONS, version 2.0

SONERA OPERATOR SERVICE PLATFORM OPAALI PORTAL SMS. FREQUENTLY ASKED QUESTIONS, version 2.0 SONERA OPERATOR SERVICE PLATFORM FREQUENTLY ASKED QUESTIONS, version 2.0 OPAALI PORTAL Q: Why Registration link to Opaali portal does not work currently, HTTP Operation Forbidden error is shown? A: Sonera's

More information

Broadband Connectivity Service (BBCS),Full Access Services (FA) and Cooperation Partner Services (COPA) General Functions Interface Specification

Broadband Connectivity Service (BBCS),Full Access Services (FA) and Cooperation Partner Services (COPA) General Functions Interface Specification Broadband Connectivity Service (BBCS),Full Access Services (FA) and Cooperation Partner Services (COPA) General Functions Interface Specification Issue date 29.09.2016 Replaces version 25 or previous Valid

More information

API-SMS HTTP/POST Interface Ref Push SMS, Balance, ACKs. April 18, 2017 v2.15

API-SMS HTTP/POST Interface Ref Push SMS, Balance, ACKs. April 18, 2017 v2.15 Ref. 17041801 - Push SMS, Balance, ACKs. Index Page 1 Introduction 3 1.1 Changelog 3 2 Send SMS messages (MT) 4 2.1 Required information 4 2.2 HTTP/POST Messaging 4 2.3 XML format 4 2.4 XML examples 7

More information

CKO2 - XML Protocols. CKO2 outputs - A2A general description. NBB - IT Department. IT Applications - PRSM. Date: 12/05/2011. Document version: V0.

CKO2 - XML Protocols. CKO2 outputs - A2A general description. NBB - IT Department. IT Applications - PRSM. Date: 12/05/2011. Document version: V0. CKO2 outputs - A2A general description Author: Service: NBB - IT Department IT Applications - PRSM Date: 12/05/2011 Document version: V0.4 Table of Contents 1. Introduction 3 1.1 Document history 3 1.2

More information

Notification Services

Notification Services Apple Push Notifications, page 1 Email Notifications, page 5 Multiple Email Notification Configuration, page 9 SMS Notifications, page 12 Multiple SMSC Server Configuration, page 20 Real Time Notifications,

More information

Cloud SMS API Guide. Version 5.1

Cloud SMS API Guide. Version 5.1 Cloud SMS API Guide Version 5.1 Cloud API Guide v5.1 Page 1 of 18 Table of Content 1 Overview 1 2 MACH Push Messaging 2 3 MT API Details 3 3.1 Send Message 3 3.2 Send Long Concatenated Messages 8 4 MO

More information

Using BMC SRM OOB Web Services

Using BMC SRM OOB Web Services Using BMC SRM OOB Web Services The BMC Service Request Management application is shipped with a number of OOB Web Services that can be used to Create, Query and Modify requests (see Figure 1. at end of

More information

Composer Help. Web Request Common Block

Composer Help. Web Request Common Block Composer Help Web Request Common Block 7/4/2018 Web Request Common Block Contents 1 Web Request Common Block 1.1 Name Property 1.2 Block Notes Property 1.3 Exceptions Property 1.4 Request Method Property

More information

EBULKSMS

EBULKSMS EBULKSMS www.ebulksms.com (Customized Text Messaging System) API Specification Doc Version Date Author Description 1.0 01-August-2013 Dr Fox Initial draft 1.1 14-July-2017 Dr Fox Get API Key Index SEND

More information

HappyFox API Technical Reference

HappyFox API Technical Reference HappyFox API Technical Reference API Version 1.0 Document Version 0.1 2011, Tenmiles Corporation Copyright Information Under the copyright laws, this manual may not be copied, in whole or in part. Your

More information

SafetyNet Web Services

SafetyNet Web Services SafetyNet Web Services Application Program Interface (API) JSON Supplement June 28, 2017 Copyright 2014-2017 Predictive Solutions, Inc. All rights reserved.. Contents Change History... 1 Request HTTP Headers...

More information

SMS Submit Interface description HTTP Version 1.5

SMS Submit Interface description HTTP Version 1.5 SMS Submit Interface description HTTP Version 1.5 This document is intended for application developers with knowledge about the HTTP protocol. Document history Version Description 1.5 Spelling error corrected

More information

API Documentation. Release Version 1 Beta

API Documentation. Release Version 1 Beta API Documentation Release Version 1 Beta Document Version Control Version Date Updated Comment 0.1 April 1, 2016 Initialize document 1 Release version PROMOTEXTER V3 BETA - API Documentation 1 Table of

More information

Data Transport. Publisher's Note

Data Transport. Publisher's Note Data Transport Publisher's Note This document should be considered a draft until the message formats have been tested using the latest release of the Apache Foundation's SOAP code. When those tests are

More information

SIMPro - User Guide. Customer Documentation. Version Issue Date 17/08/2017. Wireless Logic Ltd Horizon Honey Lane Hurley, Berkshire SL6 6RJ

SIMPro - User Guide. Customer Documentation. Version Issue Date 17/08/2017. Wireless Logic Ltd Horizon Honey Lane Hurley, Berkshire SL6 6RJ SIMPro - User Guide Customer Documentation Version - 1.9 Issue Date 17/08/2017 Wireless Logic Ltd Horizon Honey Lane Hurley, Berkshire SL6 6RJ Tel: +44 330 056 3300 Web : www.wirelesslogic.com Section

More information

Backup Gateway Documentation

Backup Gateway Documentation Backup Gateway Documentation Written by Jateen Mistry Revised: 18 th May 2004, Revised: 29 th May 2004 [Adam Beaumont] SUPPORT: For support related issues please logon to the support forum at http://aqcorporate.com/support.php

More information

An introduction API testing with SoapUI

An introduction API testing with SoapUI An introduction API testing with SoapUI Vincent Vonk 12-06-2018 CGI Group Inc. Agenda for the next 50 minutes What is SoapUI? What are Web APIs? Why test on API level? What can SoapUI do? Types of Web

More information

Automatic system alerts on Primo or, How to respond to a system outage in your sleep

Automatic system alerts on Primo or, How to respond to a system outage in your sleep Automatic system alerts on Primo or, How to respond to a system outage in your sleep Deborah Fitchett Library, Teaching and Learning, Lincoln University The problem The solution Step 1 System status http://status.exlibrisgroup.com/

More information

Way2mint SMS Mobile Terminate (MT) API Guide for HTTP / HTTPS

Way2mint SMS Mobile Terminate (MT) API Guide for HTTP / HTTPS Way2mint SMS Mobile Terminate (MT) API Guide for HTTP / HTTPS 10/1/2009 Way2mint Services Prepared by: Mohit Jaswani Copyright Way2mint Services The content of this document are copyright and remain the

More information

Sophisticated Simplicity In Mobile Interaction. Technical Guide Number Information Services - Asynchronous SOAP. Version 1.3

Sophisticated Simplicity In Mobile Interaction. Technical Guide Number Information Services - Asynchronous SOAP. Version 1.3 Sophisticated Simplicity In Mobile Interaction Technical Guide Number Information Services - Asynchronous SOAP Version 1.3 Table of Contents Page 1. Introduction to Number Information Services 3 2. Requirements

More information

SMS4BD Gateway Integration

SMS4BD Gateway Integration SMS4BD Gateway Integration TECHNICAL DOCUMENTATION v3.0 This document is intended to help IT experts in integration of SMS gateway of SMS4BD. Any alteration of this document without permission is strictly

More information

SOAP Introduction Tutorial

SOAP Introduction Tutorial SOAP Introduction Tutorial Herry Hamidjaja herryh@acm.org 1 Agenda Introduction What is SOAP? Why SOAP? SOAP Protocol Anatomy of SOAP Protocol SOAP description in term of Postal Service Helloworld Example

More information

How To Add a Borrower Via Web Services API

How To Add a Borrower Via Web Services API How To Add a Borrower Via Web Services API Summary This document outlines the use of the Web Services API available in the version 5(v5) knowledge content and library management (KCLM) solution for adding,

More information

Forthnet Mobile Platform - groupsms http interface v1.0 1 / 9

Forthnet Mobile Platform - groupsms http interface v1.0 1 / 9 Table of Contents Introduction... 2 Requirements... 2 Connecting to Forthnet Mobile Platform... 2 Message submission... 3 Client Request... 3 Parameters... 4 Parameter user... 4 Parameter pass... 4 Parameter

More information

Sage Documentation. Release 2.0. Ash Islam

Sage Documentation. Release 2.0. Ash Islam Sage Documentation Release 2.0 Ash Islam December 19, 2013 Contents i ii The SAGE API exposes methods for geocoding, address correction, and district assignment given addresses or geocoordinates as input.

More information

API DOCUMENTATION INDODAX.COM

API DOCUMENTATION INDODAX.COM API DOCUMENTATION INDODAX.COM v1.8 Last updated: 9 April 2018 Table of Contents Public API 3 Private API 3 Authentication 4 Responses 4 API Methods 5 getinfo 5 transhistory 6 trade 7 tradehistory 8 openorders

More information

1. Overview Account Configuration Details... 3

1. Overview Account Configuration Details... 3 WhatsApp Enterprise API - Technical Guide V4.4 July 2018 Index 1. Overview... 3 2. Account Configuration Details... 3 2.1 Provisioning of a Demo API... 3 2.2 Activation of Production API... 3 2.3 Setting

More information

version 2.0 HTTPS SMSAPI Specification Version 1.0 It also contains Sample Codes for -.Net - PHP - Java

version 2.0 HTTPS SMSAPI Specification Version 1.0 It also contains Sample Codes for -.Net - PHP - Java HTTPS SMS API SPEC version 2.0 HTTPS SMSAPI Specification This document contains HTTPS API information about - Pushing SMS, - Pushing Unicode SMS, - Scheduling SMS - Checking SMS credits, Version 1.0 -

More information

https://blogs.oracle.com/angelo/entry/rest_enabling_oracle_fusion_sales., it is

https://blogs.oracle.com/angelo/entry/rest_enabling_oracle_fusion_sales., it is More complete RESTful Services for Oracle Sales Cloud Sample/Demo Application This sample code builds on the previous code examples of creating a REST Facade for Sales Cloud, by concentrating on six of

More information

HP Operations Orchestration

HP Operations Orchestration HP Operations Orchestration for the Windows and Linux operating systems Software Version: OO 10.x Web Services Wizard Guide Document Release Date: February 2014 Software Release Date: February 2014 Legal

More information

cellip CELLIPS SMS INTERFACE DESCRIPTION HTTP GET INNEHÅLLSFÖRTECKNING

cellip CELLIPS SMS INTERFACE DESCRIPTION HTTP GET INNEHÅLLSFÖRTECKNING INNEHÅLLSFÖRTECKNING Innehållsförteckning... 1 1 Introduction... 2 1.1 Scope... 2 2 HTTP Get interface... 2 2.1 Mobile Terminated Messages... 2 2.1.1 Usage... 2 2.1.2 Parameters... 2 2.1.3 Codes... 4 2.1.4

More information

Inforce Transactions TECHNICAL REFERENCE. DTCCSOLUTIONS September Copyright 2011 Depository Trust Clearing Corporation. All Rights Reserved.

Inforce Transactions TECHNICAL REFERENCE. DTCCSOLUTIONS September Copyright 2011 Depository Trust Clearing Corporation. All Rights Reserved. TECHNICAL REFERENCE Inforce Transactions Page 1 Table of Contents 1 Overview... 3 2 Roles and Responsibilities... 3 2.1 Participants... 3 2.2 DTCC Server... 4 3 Communication Protocols... 5 3.1 SOAP Messages...

More information

Sophisticated Simplicity In Mobile Interaction. Technical Guide Number Information Services - Synchronous SOAP. Version 1.3

Sophisticated Simplicity In Mobile Interaction. Technical Guide Number Information Services - Synchronous SOAP. Version 1.3 Sophisticated Simplicity In Mobile Interaction Technical Guide Number Information Services - Synchronous SOAP Version 1.3 Table of Contents Page 1. Introduction to Number Information Services 3 4 2. Requirements

More information

dciphering Computing Amazon Seller Central Soap/XML Services as of Jan/2009

dciphering Computing Amazon Seller Central Soap/XML Services as of Jan/2009 Introduction: If you have had opportunity to review the documentation for Amazon s Web Services API for Seller Central you may have been impressed with all the documentation available and thought it would

More information

Business Register Web Services XML Services (v6 adapter)

Business Register Web Services XML Services (v6 adapter) Business Register Web Services XML Services (v6 adapter) Last modification: 13. September 2018 Business register web services XML services Introduction:... 3 1. Simple company data query (status query)...

More information

Enabler Test Specification for RCS Conformance

Enabler Test Specification for RCS Conformance Enabler Test Specification for RCS Conformance Candidate Version 1.2.2 10 Mar 2014 Open Mobile Alliance OMA-ETS-RCS-CON-V1_2_2-20140310-C OMA-ETS-RCS-CON-V1_2_2-20140310-C Page 2 (74) Use of this document

More information

27-Jan Customer Portal API. Quick reference for developers

27-Jan Customer Portal API. Quick reference for developers 27-Jan-2015 Customer Portal API Quick reference for developers Content 1. Brief overview and process flow... 2 1.1. Session... 2 1.2. Customer authorization... 2 1.3. Audio upload... 3 1.4. Calculate price...

More information

All About Integration

All About Integration All About Integration XOG XML Open Gateway Lars Seibert, Engineering Services Architect July 2009 Terms of This Presentation This presentation was based on current information and resource allocations

More information

COP 4814 Florida International University Kip Irvine. Inside WCF. Updated: 11/21/2013

COP 4814 Florida International University Kip Irvine. Inside WCF. Updated: 11/21/2013 COP 4814 Florida International University Kip Irvine Inside WCF Updated: 11/21/2013 Inside Windows Communication Foundation, by Justin Smith, Microsoft Press, 2007 History and Motivations HTTP and XML

More information

SONERA OPERATOR SERVICE PLATFORM

SONERA OPERATOR SERVICE PLATFORM SONERA OPERATOR SERVICE PLATFORM OMA Messaging REST API Guide Copyright 2016 Aepona Limited, and copyright 2016 Telia Company All rights reserved by respective owners. Revision: 8.2 Legal Information Legal

More information

HTTP API Specification V2.7

HTTP API Specification V2.7 HTTP API Specification V2.7 Version information Version Comment Date V2.7 Added testsms call 2017-08-09 V2.6 HTTPS information added 2016-12-10 Added error code 4007 V2.5 Changed endpoints 2016-12-09 Added

More information

Enterprise Integration Using IEC

Enterprise Integration Using IEC Enterprise Integration Using IEC 61968-100 Scott Neumann, UISOL Margaret Goodrich, SISCO Michael Johnson, Elster CIMug Meeting Introduction The purpose of this presentation is to describe enterprise integration

More information

myinsight for Documentum myinsight Web Services User Guide

myinsight for Documentum myinsight Web Services User Guide myinsight for Documentum myinsight Web Services User Guide Contents 1. Version History... 3 2. Product... 4 3. Webservice Introduction... 6 3.1. REST End Points... 6 3.2. SOAP End Points...6 4. Authorization...

More information

SmartFocus Cloud Service APIs

SmartFocus Cloud Service APIs SmartFocus Cloud Service APIs Document name SmartFocus User Guide Service Campaign management for managing email campaigns Protocol SOAP & REST over HTTP Version 11.8 Last updated on June 22, 2015 Table

More information

REST Web Services Objektumorientált szoftvertervezés Object-oriented software design

REST Web Services Objektumorientált szoftvertervezés Object-oriented software design REST Web Services Objektumorientált szoftvertervezés Object-oriented software design Dr. Balázs Simon BME, IIT Outline HTTP REST REST principles Criticism of REST CRUD operations with REST RPC operations

More information

User Guide. Push Service REST API. Push Service REST API Version 1.5

User Guide. Push Service REST API. Push Service REST API Version 1.5 Push Service REST API Push Service REST API Version 1.5 User Guide The information contained within this document is the property of PageOne Communications Ltd and may not be copied used or disclosed in

More information

Integration Architecture. A quick introduction to the basics of Wynne s Integration Architecture

Integration Architecture. A quick introduction to the basics of Wynne s Integration Architecture Integration Architecture A quick introduction to the basics of Wynne s Integration Architecture The Basics: What is XML? HTML HyperText Markup Language XML Extensible Markup Language The biggest difference

More information

Brain Corporate Bulk SMS

Brain Corporate Bulk SMS Brain Corporate Bulk SMS W e S i m p l y D e l i v e r! API Documentation V.2.0 F e b r u a r y 2 0 1 9 2 Table of Contents Sending a Quick Message... 3 API Description... 3 Request Parameter... 4 API

More information

Quriiri HTTP MT API. Quriiri HTTP MT API v , doc version This document describes the Quriiri HTTP MT API version 1 (v1).

Quriiri HTTP MT API. Quriiri HTTP MT API v , doc version This document describes the Quriiri HTTP MT API version 1 (v1). Quriiri HTTP MT API This document describes the Quriiri HTTP MT API version 1 (v1). Sending messages Request types Security Request parameters Request examples JSON POST GET Response JSON response example

More information

emag Marketplace API Implementation Best Practices v1.0

emag Marketplace API Implementation Best Practices v1.0 emag Marketplace API Implementation Best Practices v1.0 17.03.2015 Version Date modified Changes 1.0 12.02.2015 First draft Table of Contents 1. General guidelines for authentication... 2 2. Maximum size

More information

External HTTPS Trigger AXIS Camera Station 5.06 and above

External HTTPS Trigger AXIS Camera Station 5.06 and above HOW TO External HTTPS Trigger AXIS Camera Station 5.06 and above Created: October 17, 2016 Last updated: November 19, 2016 Rev: 1.2 1 Please note that AXIS does not take any responsibility for how this

More information

Integration Guide Xura Messaging HTTP-Interface

Integration Guide Xura Messaging HTTP-Interface Integration Guide Xura Messaging HTTP-Interface Version 2.1.5 Content is subject to change Xura Secure Communications GmbH Tel.: +49 89 201 727 0 e-mail.: asc-support@xura.com All rights reserved. This

More information

XchangeCore Quick Start Guide to the Incident Management Service And Incident Work Products

XchangeCore Quick Start Guide to the Incident Management Service And Incident Work Products XchangeCore Quick Start Guide to the Incident Management Service And Incident Work Products The XchangeCore Community www.xchangecore.com Revision Number Date Description Revisions R05C00 6/16/2014 Initial

More information

WhatsATool API - REST-Like Interface to WhatsATool Services

WhatsATool API - REST-Like Interface to WhatsATool Services Disclaimer This service and also mtms Solutions GmbH is not associated in any case with WhatsApp. WhatsApp is a registered Trademark owned by WhatsApp Inc. mtms is not related in any way with WhatsApp

More information

SortMyBooks API (Application programming

SortMyBooks API (Application programming SortMyBooks API (Application programming interface) Welcome to Sort My Books. This documentation will help you to get started with SortMyBooks API. General Considerations SortMyBooks works with objects

More information

IUID Registry Application Programming Interface (API) Version 5.6. Software User s Manual (SUM)

IUID Registry Application Programming Interface (API) Version 5.6. Software User s Manual (SUM) IUID Registry Application Programming Interface (API) Version 5.6 Software User s Manual (SUM) Document Version 1.0 May 28, 2014 Prepared by: CACI 50 N Laura Street Jacksonville FL 32202 Prepared for:

More information