Messaging Service REST API Specification V2.3.2 Last Modified: 07.October, 2016
|
|
- Dorcas Lambert
- 5 years ago
- Views:
Transcription
1 Messaging Service REST API Specification V2.3.2 Last Modified: 07.October, 2016 page 1
2 Revision history Version Date Details Writer /16/2014 First draft Sally Han /13/2014 Revised v.1.1 document. Sally Han /14/2014 Revised v.1.2 document. Sally Han /19/2014 Revised v1.3 document. Sally Han /11/2014 Revised v1.4 document. Sally Han /02/ Changed XML parameters. (replaced _ (underscore) with - Sally Han (bar)) 2. Added Report Responses and return values /23/ Added the description on Concatenated Message. Sally Han 2. Added the Submit packet charset field. 3. Removed to_country from the report set. 4. Added charset to the Submit field /29/ Added the msg_type field to Response. Sally Han 2. Added rescnt to REPORT Response /08/2015 Supplemented specification description. Sally Han /08/2015 Added the report connection information. Sally Han /17/2015 Added the MMS title field. Sally Han /03/2015 Added error codes related a Korean regulation of Sender ID. Sally Han /27/ Changed the Base URL./Added the HTTPS protocol. 2. Changed the report receiving IP. Goonghee Nam 3. Changed the result code. 4. Added the response code (credit/sender ID alteration, etc.) 5. Removed the status parameter of the result sending API Changed Report format Added Sample code Goonghee Nam correct the Response Code : Success example Cliff Lee <err_code>1000</err_code> <err_code>r000</err_code> Request format Added payment_code, client_sub_id field Goonghee Nam As is : path: 'sms/xml?id' + encodeuricomponent('infobank_test') To be : path: 'sms/xml?id=' + encodeuricomponent('infobank_tes t') Goonghee Nam page 2
3 Added Report Return code : Charset conversion error Goonghee Nam page 3
4 Table of Contents 1. INTRO SERVICE FLOWCHART MESSAGE SPECIFICATIONS BASE URL RECEIVING THE RESULT INFORMATION REQUEST FORMAT Example of Request PHP Shell(BASH) Python Ruby nodejs REQUEST RESPONSE FORMAT Example of Request Response Success Fail REPORT FORMAT Example of Report Format Success Failure REPORT RESPONSE FORMAT Example of Report Response RESPONSE AND RESULT CODE RESPONSE RETURN CODE REPORT RETURN CODE APPENDIX CONCATENATED SMS CONTACT US...14 page 4
5 1. Intro This document defines the protocol specification for constructing the interface that enables the Client to send SMS messages via the Infobank Server. Using the HTTP API specification (RESTful method) described in this document, the following functionality is provided: - Connecting & disconnecting to the Infobank Servers (platform) - Sending messages using HTTP, XML and plain text - Collect delivery receipt (DLR) 2. Service Flowchart 6. Response Reports Wireless Environment 1. Request HTTP: The client sends a message according to the REST API specification, using TCP/IP communication. 2. Response HTTP: The server responds to the message sending request received from the client. 3. SEND SMS: The server sends the message to the local carrier. 4. Get Reports: The server receives the message report from the local carrier. 5. Get Reports: Transfers the message report to the client, which has been sent to the server by the local carrier. 6. Response Reports: Transfers the response about the normal reception of the message report to the server. page 5
6 3. Message specifications HTTP METHOD - The HTTP GET/POST method is provided to make a transfer request, and the XML method is used for the transfer response. ENCODING - UTF-8 encoding is provided by default. TIMEZONE - Korean Standard Time KST (UTC+9) is used as the base time of the message Base URL HTTP HTTPS Receiving the result information The IP of the Infobank s server, which sends the result value, should be allowed to access and send us your IP and PORT, in order to receive the message sending result. IP information of the server that sends the result: / Please send your IP and PORT to support@infobank.net 3.3. Request format UTF-8 encoding is used to support various languages. [M] Mandatory, [O] Optional Parameter M/O Type Description from M Char Sender ID (up to 16bytes) e.g.,) When sending to Korea: from= to_country M Char Country code (1 ~ 3 bytes) e.g.,) When sending to Korea: to_country=82 to M Char Recipient (up to 13bytes) e.g.,) When sending to Korea: to= title O Char Message title (up to 40 byte) - The message title requires UTF-8 and URL encoding. - Valid only when sending LMS to Korea. message M Char Message content - The message content requires UTF-8 and URL encoding. report_req M Char Report receiving status - 1 : Reports are received. (This parameter should be set.) page 6
7 charset O Char Encoding setting (1: UTF-8, 2: euc-kr) - UTF-8 encoding will be applied if this parameter is not set. e.g.,) charset=2 (euc-kr) ref O Char A spare field that can be set by the user. (Up to 20bytes, alphabets/numbers only) ttl O Char Valid time of the message (in seconds) e.g.,) ttl=86400 (24hour = 60 * 60 * 24) payment_code O Char Field for separating payment by departments (Max 20 byte) client_sub_id O Char Filed for using several Sender ID and Signature (Max 20 byte) The Sender ID only supports numeric format. If a message exceeding 90bytes in size is sent to Korea, the message will be automatically switched to an LMS (MMS without an attached file) Example of Request PHP <?php $url = ' http_build_query([ 'id' => 'infobank_test', 'pwd' => 'pwinfobank', 'from' => ' ', 'to_country' => '82', 'to' => ' ', 'message' => 'Hello Infobank', 'report_req' => '1' ]); $ch = curl_init($url); curl_setopt($ch, CURLOPT_RETURNTRANSFER, true); $response = curl_exec($ch); $xml = simplexml_load_string($response); if ($xml === false) { echo "Failed loading XML: "; } else { //print_r($xml); //echo($xml->to_country); //echo($xml->to); echo("response code : ". $xml->messages->message->err_code); page 7
8 }?> Shell(BASH) #!/bin/bash curl ' \ -d id=infobank_test \ -d pwd=pwinfobank \ -d from= \ -d to_country=82 \ -d to= \ --data-urlencode "message=hello Infobank" \ -d report_req= Python import urllib params = { 'id': 'infobank_test', 'pwd': 'pwinfobank', 'from': ' ', 'to_country': '82', 'to': ' ', 'message': 'Hello Infobank', 'report_req': '1' } url = ' + urllib.urlencode(params) response = urllib.urlopen(url) print response.read() Ruby require "net/http" require "uri" uri = URI.parse(" params = { "id" => "infobank_test", page 8
9 } "pwd" => "pwinfobank", "from" => " ", "to_country" => "82", "to" => " ", "message" => "Hello Infobank", "report_req" => "1" response = Net::HTTP.post_form(uri, params) puts response.body nodejs var https = require('https'); var options = { host: 'rest.supersms.co', path: 'sms/xml?id=' + encodeuricomponent('infobank_test') + '&pwd=' + encodeuricomponent('pwinfobank') + '&from=' + encodeuricomponent(' ') + '&to_country=' + encodeuricomponent('82') + '&to=' + encodeuricomponent(' ') + '&message=' + encodeuricomponent('hello Infobank') + '&report_req=' + encodeuricomponent(1) }; var req = https.request(options); req.end(); var responsedata = ''; req.on('response', function(res){ res.on('data', function(chunk){ responsedata += chunk; }); res.on('end', function(){ }); console.log(responsedata); page 9
10 }); 3.4. Request Response format Success/Failure can be checked using the response to the request. [M] Mandatory: [O] Optional: Parameter M/O Type Description msgid M Char An ID assigned to the sent message. to_country M Char Country code (1 ~ 3 bytes) e.g.,) When sending to Korea <to_country>82</to_country> to M Char Recipient err_code M Char Message sending result code messages cnt M Char Number of messages msg_type M Char Message type (1. SMS, 2. MMS) E.g.,) If the message has been sent as an MMS <msg_type>2</msg_type> ref O Char A spare field that can be set by the user. - Transfers the ref value set in Request Example of Request Response Success <?xml version='1.0' encoding='utf-8'?> <submit_response> <to_country>82</to_country> <to> </to> <messages cnt= 1 > <message> <msgid> </msgid> <err_code> R000</err_code> <msg_type>1</msg_type> </message> </messages> <ref>aa </ref> </submit_response> Fail <?xml version='1.0' encoding='utf-8'?> <submit_response> page 10
11 <to_country>82</to_country> <to> </to> <messages cnt= 1 > <message> <err_code>r007</err_code> </message> </messages> <ref>aa </ref> </submit_response> See 4.1 Response Return Code for err_code 3.5. Report Format The report transfers the result value with the GET method, using the access information provided by the client. [M] Mandatory: [O] Optional: Parameter M/O Type Description msgid M Char An ID assigned to the sent message. to M Char Recipient (Country code should be excluded) ex) to_country M Char Country code of recipient number ex) 82 err_code M Char Detailed report result code network M Char Mobile network MCCMNC. (MCC: Country code, MNC: Local carrier code) e.g.,) (SKT), (LGU+), (KT) rescnt M Char Number of actual message billing cases * For concatenated messages, send the number of messages that is actually charged. sent_date O Char Time of sent - Based on Korean Standard Time: KST(UTC+9), YYYYMMDDHHMMSS ref O Char A spare field that can be set by the user. - Transfers the ref value set in Request Example of Report Format Success?msgid = &to= &to_country=82&ref=AA &network=45008 &rescnt=1&err_code=1000&sent_date= page 11
12 Failure?msgid= &to= &to_country=82&ref=AA &network=45008&rescnt= 0&err_code=3001 See 4.2. Report Return Code for more details on err_code & status Report Response Format Please see 3.2 Receiving the result information to receive report. The report transfers the result value with the GET method, using the access information provided by the client. [M] Mandatory: [O] Optional: Parameter M/O Type Description msgid M Char An ID assigned to the sent message. to_country M Char Country code (1 ~ 3 bytes) e.g.,) When sending to Korea: to_country=82 To M Char Recipient Example of Report Response <?xml version='1.0' encoding='utf-8'?> <report_response> <msgid> </msgid> <to_country>82</to_country> <to> </to> </report_response > 4. Response and result code 4.1. Response Return Code Status code Description SUCCESS R000 Success FAILURE R001 Server busy INVALID R002 Verification failed INVALID R003 Incorrect recipients format INVALID R004 Incorrect Sender ID format INVALID R005 Invalid message format INVALID R006 Invalid TTL page 12
13 INVALID R007 Invalid parameter error INVALID R008 Spam filtering INVALID R009 Server capacity exceeded. Please retry. INVALID R010 Unregistered Sender ID INVALID R011 A Sender ID is used that violated the Sender ID alteration prevention standard. INVALID R012 No right to send the pertinent service type INVALID R013 Exceeded the maximum number of messages that can be sent UNKNOWN R999 Unknown error 4.2. Report Return Code Status code Description SUCCESS 1000 Success FAILURE 2000 Sending time exceeded. FAILURE 2001 Failed to send. FAILURE 2002 Failed to send. FAILURE 2003 The handset is turned off. FAILURE 2004 The handset message is full. FAILURE 2005 Shadow area FAILURE 2006 The message has been deleted. FAILURE 2007 Temporary handset problem INVALID 3000 Unable to send. INVALID 3001 No subscriber INVALID 3002 Age verification failed. INVALID 3003 Invalid recipients format INVALID 3004 Handset service suspended temporarily. INVALID 3005 Handset call processing state INVALID 3006 Declining incoming calls INVALID 3007 Handset cannot receive a callback URL. INVALID 3008 Other handset problems INVALID 3009 Invalid message format INVALID 3010 Handset that doesn t support MMS. INVALID 3011 Server error INVALID 3012 Spam INVALID 3013 Service denial INVALID 3014 Others INVALID 3015 No transmission path page 13
14 INVALID 3016 Failed to limit the size of the attached file. - Violated the bylaws to prevent alteration of Sender ID. - Some messages during a broadcast message violated the bylaws. INVALID 3018 Prohibited sender ID by Korean carriers. INVALID 3019 Prohibited sender ID by Korean governmental agencies. INVALID 3022 Charset conversion error 5. APPENDIX 5.1. Concatenated SMS A method of sending messages longer than 160 characters. This method is supported by some countries and local carriers. The entire message will be shown as a single message on the actual mobile phone. It is charged according to the number of characters, based on one standard SMS message. When concatenated SMS messages are used, the code to process a long message is included. As a result, 153 characters are considered as the maximum message length when charging the fee. For example, if a 350 character-long message is sent to a country that uses a 160 character-long SMS message as a standard, the fee of three messages will be charged (153 characters characters + 44 characters = 350 characters). 6. Contact Us For any inquiries or comment about these specifications, please send us an (support@infobank.net). page 14
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 informationConnect 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 informationAPI 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 informationAll 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 informationLINK 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 informationSMS Aggregation - API Documentation
SMS Aggregation - API Documentation Wireless Logic Version - 2.0 Issue Date - 20th February 2014 Wireless Logic Ltd Grosvenor House Horseshoe Crescent Beaconsfield, Buckinghamshire HP9 1LJ Tel: +44 (0)1494
More informationForthnet 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 information2. 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 informationWay2mint 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 informationGatesms.eu Mobile Solutions for Business
TECHNICAL SPECIFICATIONS XML Web API GATESMS.EU, version 1.1 Prepared by: Gatesms.eu Contents Document version history...3 Security...3 General requirements...3 HTTP transmission security mechanism...3
More informationARTIO 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 informationQuriiri 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 informationAPI 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 informationRevision: 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 informationSMS 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 informationSMS 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 informationSMS4BD 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 informationHTTP 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 informationTechnical Guide. REST API for Mobile Outbound SMS
Technical Guide REST API for Mobile Outbound SMS Munich +49 89 202 451 100 Singapore +65 6478 3020 London +44 207 436 0283 San Francisco +1 415 527 0903 sales@tyntec.com www.tyntec.com Table of Contents
More information1. 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 informationcellip 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 informationIntegration 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 informationAPI 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 informationIntegrating with Cellsynt's SMS gateway via HTTP interface (technical documentation)
Integrating with Cellsynt's SMS gateway via HTTP interface (technical documentation) Integrating with Cellsynt's SMS gateway via HTTP interface (technical documentation) Table of Contents Part I Introduction
More informationMCB Gateway. 1 Introduction. 2 Change history. 3 Table of contents
MCB Gateway 1 Introduction This document describes the communication interface (API) of our Mobile Content Billing (MCB/DB) gateway called FuturePay. This technical document is meant for system engineers
More informationversion 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 informationFuture Pay MCB API. Version
Future Pay MCB API Version 03 2014-02-11 Contents Contents... 2 1. Document history... 3 2. Scope and intended audience... 3 3. Communication with Future Pay... 4 3.1 overview... 4 3.2 Request... 6 3.3
More informationFax Broadcast Web Services
Fax Broadcast Web Services Table of Contents WEB SERVICES PRIMER... 1 WEB SERVICES... 1 WEB METHODS... 1 SOAP ENCAPSULATION... 1 DOCUMENT/LITERAL FORMAT... 1 URL ENCODING... 1 SECURE POSTING... 1 FAX BROADCAST
More informationSophisticated 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 informationXML API Developer-Documentation Version 2.01
XML API Developer-Documentation Version 2.01 07/23/2015 1 Content Introduction...4 Who needs this information?...4 S-PAY Testing Environment...4 URL to our API...4 Preparation...5 Requirements...5 API
More informationSophisticated 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 informationAPI Specification Doc
API Specification Doc (SMS System Gateway) Version Date Description 1.0 01-Nov-2017 Initial draft 1.1 18-Feb-2018 Updated to include Delivery report call back options 1.2 10-Apr-2018 Appended API to include
More informationRHODE ISLAND Electronic Business Transactions
RHODE ISLAND Electronic Business Transactions For TRANSACTION SET Functional Acknowledgment Ver/Rel 004010 RI997 (004010UIG) Version: 99.1 8-1-1999 997 Functional Acknowledgment Introduction: RHODE ISLAND
More informationCloud 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 informationERMES. Technical Specification for ex MPAY services integration. version /10/2018
ERMES Technical Specification for ex MPAY services integration version 1.7 26/10/2018 Summary 1.Changes...3 2.Introduction...4 2.1.Glossary...4 3.ERMES API Overview...5 3.1.Protocol...6 4.ERMES API...9
More informationSMS Outbound. HTTP interface - v1.1
SMS Outbound HTTP interface - v1.1 Table of contents 1. Version history... 5 2. Conventions... 5 3. Introduction... 6 4. Application Programming Interface (API)... 7 5. Gateway connection... 9 5.1 Main
More informationBulk HTTP API Specification
Bulk HTTP API Specification (Document Version 1.0) (This Document gives details on how to send messages via the Bulk HTTP API for the CloudSMS Gateway) HTTP API to submit messages to CloudSMS http://developers.cloudsms.com.ng/api.php?userid=xxxx&password=yyyyy&type=y&destinati
More informationAPI HTTP TECHNICAL DOCUMENTATION WEB-BASED SMS SENDING PLATFORM. Version Update: July 12th Mobile Marketing and Messaging Solutions
Mobile Marketing and Messaging Solutions WEB-BASED SMS SENDING PLATFORM API HTTP 12/05/2015 1:50PM Hello. Your order ref: 123456 is ready for pickup at your Relay Point 10 Amiens Street, 75002 Paris. Please
More informationSending 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 informationHTTP API. https://www.smsn.gr. Table of Contents
HTTP API https://www.smsn.gr Table of Contents Send SMS...2 Query SMS...3 Multiple Query SMS...4 Credits...5 Save Contact...5 Delete Contact...7 Delete Message...8 Email: sales@smsn.gr, Τηλ: 211 800 4200,
More informationAPI-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 informationSending 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 informationtext2reach2 SMS API Sep 5, 2013 v1.1 This document describes application interface (API) between SMS service provider (SP) and SMS gateway (SMSGW).
text2reach2 SMS API Sep 5, 2013 v1.1 This document describes application interface (API) between SMS service provider (SP) and SMS gateway (SMSGW). Table of Contents API Interface Types...3 Bulk SMS interface...3
More informationSMSCenter. 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 informationAPI 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 informationSending 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 informationZipwhip API Developer Reference Messaging API
Zipwhip API Developer Reference Messaging API Version 2.0, May 2017 Copyright 2017 Zipwhip, Inc. All rights reserved. Zipwhip, Inc Copyright 2017 Zipwhip, Inc. All rights reserved. For Customer Use Only
More informationIntegration 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 informationSONERA 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 informationSOAP 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 informationWhatsATool 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 informationFront Gateway Product Description for the connection between the SMS gateway and customer
Front Gateway Product Description for the connection between the SMS gateway and customer Applies to: SMS Gateway Standard SMS Gateway Proff SMS Gateway PSK Development Manual v.2.22 2017-05-05 Side 1
More informationSending 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 informationSMS 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 informationSMS GATEWAY API INTEGRATION GUIDE
SMS GATEWAY API INTEGRATION GUIDE For PHP Developers Are you a developer or bulk SMS reseller? You can interface your application, website or system with our 247 reliable messaging gateway by using our
More informationQliq Cloud API Guide
Qliq Cloud API Guide QliqSOFT provides Cloud API for third party applications to send Secure Messages to Qliq users. Following steps need to be performed prior to sending messages: 1. The Application provider
More informationMessaging Messaging Basics Customizing Mail Address Creating/Sending Messages Incoming Messages Using Messages...
Basics... -2 Customizing Mail Address... -3 Creating/Sending Messages... -3 S! Mail...-3 SMS...-5 Graphic Mail...-6 Incoming Messages... -7 Viewing New Messages...-7 Retrieving Messages Manually...-8 Viewing
More informationREST 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 informationSMS 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 informationMessaging Messaging Basics Customizing Mail Address Creating/Sending Messages Advanced Settings
Basics... -2 S! Mail & SMS... -2 Sending & Receiving Messages... -3 Managing Messages... -3 Customizing Mail Address... - Creating/Sending Messages... - S! Mail... - SMS... -7 Using Templates... -8 Incoming
More informationNIC SMS SERVICE INTEGRATION
Overview NIC Messaging Division has set up new SMS Gateway services. In order to integrate your application and to access different services like reports and statistics please refer to below steps. To
More informationService Requestor/User Protection Document
Service Requestor/User Protection Document 1- The Service Provider must not put any conditions, obligations or restrictions on the user that contradict or violate any provisions contained in the Communication
More informationX12 Implementation Guidelines For Inbound 997 v (I )
X12 Implementation Guidelines For Inbound 997 v004010 (I9974010) 997-4010 (i9974010) 1 10/12/2009 997 Functional Acknowledgment Functional Group ID=FA Introduction: This Draft Standard for Trial Use contains
More informationSMS Outbound. SMTP interface - v1.1
SMS Outbound SMTP interface - v1.1 Table of contents 1. Version history... 5 2. Conventions... 5 3. Introduction... 6 4. Gateway connection... 7 4.1 E-mail message format... 7 4.2 Header section... 7 4.3
More informationUnity SDK for Xiaomi (IAP) Unity IAP provides an easy way to integrate Xiaomi IAP with Unity.
Unity SDK for Xiaomi (IAP) 1. Overview 2. Login & Purchase Flow 2.1 Stand-alone login & purchase 2.2 Online login & purchase 3. Technical Integration 3.1 Onboarding to Unity 3.2 Server side integration
More informationWebSMS 5.0. User Guide. June 2011
WebSMS 5.0 User Guide June 2011 Revision History Version Date Version History 3.0 Apr, 21 2010 Document Released 3.1 Jun, 22 2010 Updated some screen shots 4.0 Aug, 5 2010 Added the following features
More informationBME Data Feed Interface Specifications. Version: Related to: BME Data Feed Release 13.0
1.1 BME Data Feed s Document Name: BME Data Feed s Version: 3.00 Related to: BME Data Feed Release 13.0 Last Updated BME Data Feed s Page 2 of 2 REVISION HISTORY This section refers to the major changes
More informationPART 7 - Central Office Optional Features Original Sheet 1 SECTION 3 - Complementary Network Services (CNS) 7.3 COMPLEMENTARY NETWORK SERVICES
PART 7 - Central Office Optional Features Original Sheet 1 7.3.1. ENHANCED SERVICE PROVIDER SERVICES 7.3.1.1. BASIC SERVICE ELEMENTS A. DESCRIPTION Basic Service Elements (BSEs) are new services for Enhanced
More informationBefore you start! : 1. It is important to know some things code, before starting the deal with this file.
Introduction: Do you have a special program you want linking it with the mobile messaging service SMS? We offer you in the SMS Mobily.ws service gate transmission API that lets you effortlessly connect
More informationTerms and Conditions of Mobile Phone Service (Post-Paid) Between Operator and Subscriber
Terms and Conditions of Mobile Phone Service (Post-Paid) Between Operator and Subscriber Section 1 General 1.1 This Terms and Conditions of Mobile Phone Service shall be effective between Advanced Wireless
More informationConfiguring Gmail (G Suite) with Cisco Cloud Security
Configuring Gmail (G Suite) with Cisco Cloud Email Security This document covers the steps required to integrate Cisco Cloud Email Security with Google G Suite for inbound and outbound email delivery.
More informationLIPNET OUTBOUND API FORMS DOCUMENTATION
LIPNET OUTBOUND API FORMS DOCUMENTATION LEGAL INAKE PROFESSIONALS 2018-03-0926 Contents Description... 2 Requirements:... 2 General Information:... 2 Request/Response Information:... 2 Service Endpoints...
More informationMessaging Messaging Basics Customizing Mail Address Creating/Sending Messages Incoming Messages Using Messages...
Basics... -2 Customizing Mail Address... -3 Creating/Sending Messages... -3 S! Mail...-3 SMS...-5 Graphic Mail...-6 Incoming Messages... -7 Viewing New Messages...-7 Retrieving Messages Manually...-8 Viewing
More informationRules and Regulations - MENA. Version 2
Rules and Regulations - MENA Version 2 Introduction Character Limits TOPICS Rules and Regulations Delivery Reports Sender Name Registrations Operator Details Contact Us Version Control Version number Section
More informationmvaayoo API Ver 1.2.0
Ver 1.2.0 DOCUMENT RELEASE NOTE Ver 1.2.0 Author(s): Sriram Gopal Reddy K Date: 21/10/2009 Reviewer(s): Dipto Mukherjee Date: 21/10/2009 Approved by: Date: REVISION HISTORY Document No: Document Title:
More informationAPERAK Application Error and Acknowledgement Message From INTTRA To Customer EDIFACT Version D Release 99B. User Guide Version 1.0
APERAK Application Error and Acknowledgement Message From INTTRA To Customer EDIFACT Version D Release 99B User Guide Version 1.0 Version 1.0 Page 1 of 32 Table of Contents I. Audience... 3 II. Business
More informationDynmark Messaging Platform XML HTTP Interface Quick Start Guide. Draft Revision September
Dynmark Messaging Platform XML HTTP Interface Quick Start Guide Draft Revision 3.0.5 4 September 2006 E-mail: support@e-txt.co.uk CONTENTS Sending Messages... 3 Sending a Simple Message...3 Text Merge
More informationClick 2 Call. All rights reserved to Voicenter Revision
Click Call . Click Call Click Call enables executing direct phone calls, with just the click of a button. It s super easy to implement and integrate, using our ready-to-use code. This great and versatile
More informationThe Callback API Guide
The Callback API Guide A reference guide for developers who want to calculate their own shipping or promotional discounts for their Checkout by Amazon orders. 2009-11 Amazon.com, Inc. or its Affiliates
More informationThe HTTP protocol. Fulvio Corno, Dario Bonino. 08/10/09 http 1
The HTTP protocol Fulvio Corno, Dario Bonino 08/10/09 http 1 What is HTTP? HTTP stands for Hypertext Transfer Protocol It is the network protocol used to delivery virtually all data over the WWW: Images
More informationIP Pay. End User System Reference Manual. Document revision October 2008
IP Pay End User System Reference Manual Document revision 1.3 6 October 2008 1 Table of Contents Introduction 3 DECLINE Response Codes 4 AVS Result Codes 7 CVV2/CVC/CID Result Codes 9 CAVV Result Codes
More informationSession Capabilities in OBEX
Session Capabilities in OBEX Version 0.14 July 16, 2002 Authors: David Suvak Contributors: Kevin Hendrix Extended Systems Extended Systems Revision History Revision Date Comments 0.1 30-May-01 Initial
More informationWired 2 Wireless Technology Solutions API Help Document Copyright Introduction. 2. Parameter list
1. Introduction Wired 2 Wireless Technology Solutions offers an easy way to send and receive messages via its built-in webserver using HTTP. In this document you will learn how to send SMS, check delivery
More informationPRE BID REPLIES FOR NPCI:RFP: /0020 DATED RFQ FOR SMS GATEWAY SERVICES FOR INTEGRATION WITH FRM SOLUTIONS
PRE BID REPLIES FOR NPCI:RFP:2012-13/0020 DATED 27.11.2012 RFQ FOR SMS GATEWAY SERVICES FOR INTEGRATION WITH FRM SOLUTIONS SR.No Document Ref Page No Clause No Description in RFQ Clarification Sought Addittional
More informationHTTP Interface API. for SMS Services. Version 2. Claude ICT Poland Sp. z o. o.
Version 2 HTTP Interface API for SMS Services Claude ICT Poland Sp. z o. o. WWW.TELECUBE.PL Table of Contents 1. Foreword...2 2. Revision History...2 3. Introduction Please Note...3 a. Communication Protocol...
More informationEnabler 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 informationPC-FAX.com Web Customer Center
PC-FAX.com Web Customer Center Web Customer Center is a communication center right in your browser. You can use it anywhere you are. If you are registered by Fax.de, you have received a customer number
More informationBC95-G&BC68 MQTT Application Note
BC95-G&BC68 MQTT Application Note Rev. BC95-G&BC68_MQTT_Application_Note_V1.0 Date: 2018-09-06 Status: Released www.quectel.com Our aim is to provide customers with timely and comprehensive service. For
More informationMy MessageMedia User Guide
My MessageMedia User Guide Copyright and Trademark Statement 2011 MessageMedia All rights reserved. Apart from any use permitted under the Copyright Act 1968, no part of this publication may be reproduced,
More informationResponse: Note: Please define Dynamic Value in ##Field## The following are the parameters used: For Unicode Message:
For Unicode Message: Promotional Unicode Message API http://cloud.smsindiahub.in/vendorsms/pushsms.aspx?user=youruserid&password=yourpassword& msisdn=919898xxxxxx&sid=senderid&msg=पर षण स द श &fl=0&dc=8
More informationTerms and Conditions of Mobile Phone Service (Pre-Paid) Between Operator and Subscriber
Terms and Conditions of Mobile Phone Service (Pre-Paid) Between Operator and Subscriber Section 1 General 1.1 This Terms and Conditions of Mobile Phone Service shall be effective between Advanced Wireless
More informationSMS Pro/Billing Pro. Interface specification. Version 3.0.1
SMS Pro/Billing Pro Interface specification Version 3.0.1 Copyright Telenor Sverige AB 2008 Contents: 1 Introduction... 3 2 Protocols for interconnection... 3 3 Content format... 3 4 XML References...
More informationAutomatic 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 informationAPI Developer Reference Manual. Version 1.0
API Developer Reference Manual Version 1.0 1 Table of contents Table of contents... 2 Overview... 4 What is the HiPay Mobile API... 4 What is an API?... 4 What is a REST Web Service?... 4 Who may use this
More informationNODE.JS SERVER SIDE JAVASCRIPT. Introduc)on Node.js
NODE.JS SERVER SIDE JAVASCRIPT Introduc)on Node.js Node.js was created by Ryan Dahl starting in 2009. For more information visit: http://www.nodejs.org 1 What about Node.js? 1. JavaScript used in client-side
More informationXML API SMS GATEWAY. Issue 2.0 Dec XML API
XML API SMS GATEWAY Issue 2.0 Dec 2016 1 XML API XML API INTRODUCTION The XML API allows sending SMS through XML queries to our SMS Gateway. The SMS Gateway can be used for sending following types of SMS.
More information1WorldSync Content1 Web Services
1WorldSync Content1 Web Services API HMAC Guide Version 1.1 26-Oct-2016 2 REVISION HISTORY Date Ver # Description of Change Author October 14, 2015 1.0 Initial Version 1WorldSync October 26, 2016 1.1 Updated
More informationINTERNATIONAL TELECOMMUNICATION UNION
INTERNATIONAL TELECOMMUNICATION UNION ITU-T E.212 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (05/2004) SERIES E: OVERALL NETWORK OPERATION, TELEPHONE SERVICE, SERVICE OPERATION AND HUMAN FACTORS International
More informationInstaMember 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 informationThis description gives important information that requires attention when using Prepaid SIM for Travel data service.
Please enter into the contract after understanding and agreeing to these notes. Using Prepaid SIM for Travel data service. This description
More information