Redrabbit Cloud-based Communications Platform SMS APIs

Similar documents
ARTIO SMS Services HTTP API Documentation

This file contains an excerpt from the character code tables and list of character names for The Unicode Standard, Version 3.0.

Wired 2 Wireless Technology Solutions API Help Document Copyright Introduction. 2. Parameter list

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

HTTP API. Table of Contents

text2reach2 SMS API Sep 5, 2013 v1.1 This document describes application interface (API) between SMS service provider (SP) and SMS gateway (SMSGW).

You 2 Software

ARTIO VM SMS Documentation

Bulk HTTP API Specification

SMS+ Client User Manual

API Integration Guide

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

HTTP Specification Version 1.83

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

API HTTP TECHNICAL DOCUMENTATION WEB-BASED SMS SENDING PLATFORM. Version Update: July 12th Mobile Marketing and Messaging Solutions

UTF and Turkish. İstinye University. Representing Text

HTTP API - HELP DOCUMENT

SMSPortal SMS Encapsulation (8bit data)

Representing Characters and Text

Cloud SMS API Guide. Version 5.1

Quenbec inc # henri bourassa H3L-3N3 Montreal, QC,Canada Toll free: Mobile

J2 LCM Customer Display. Manual

SMS API TECHNICAL SPECIFICATION

SMS API - Web Services with SSL SHA2 HMAC Version 1.7

To SMS Technical Guide

mvaayoo API Ver 1.2.0

Banner 8 Using International Characters

User Manual RouteSms SmsPlus Desktop. Version 1.0

HTTP API-HELP DOCUMENT

Brain Corporate Bulk SMS

Before you start! : 1. It is important to know some things code, before starting the deal with this file.

API-SMS HTTP/GET Interface Ref Push SMS, Balance, ACKs. April 18, 2017 v1.12

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

Integrating with Cellsynt's SMS gateway via HTTP interface (technical documentation)

Pe h-ōe-jī Unicode Correspondence Table

B-Speech MiniPad User Manual. User Manual For Nokia Page 1 of 23

Personal Conference Manager (PCM)

Appendix C. Numeric and Character Entity Reference

Microsoft Pocket PC 2003 Windows Mobile 5.0 Phone Edition

Service Segment Version 3

SMS HTTP API DOCUMENTATION December 2012

Unicode and Non Unicode Printing with the Swiss 721 Font

Response: Note: Please define Dynamic Value in ##Field## The following are the parameters used: For Unicode Message:

HTTP Interface API. for SMS Services. Version 2. Claude ICT Poland Sp. z o. o.

Requirement Document v1.2 WELCOME TO CANLOG.IN. API-Key Help Document. Version SMS Integration Document

124 DISTO pro 4 / pro 4 a-1.0.0zh

SMS4BD Gateway Integration

Trigger SMS API. API Documentation SPLIO - SPRING Contact and Campaign Trigger SMS API - EN v4.0.docx

Overview Introduction Messaging Error Codes Message parameter details Contact Details... 7

Requirement Document v1.1 WELCOME TO CANLOG.IN. API Help Document. Version SMS Integration Document

Telenor Corporate Call & SMS. API Documentation

SMSCenter. SMSCenter API

SMS Submit Interface description HTTP Version 1.5

Using non-latin alphabets in Blaise

Terry Carl Walker 1739 East Palm Lane Phoenix, AZ United States

SMS Outbound. HTTP interface - v1.1

Lecture 5 C Programming Language

Transformations Review

Support for word-by-word, non-cursive handwriting

Message parameter details

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

APPLESHARE PC UPDATE INTERNATIONAL SUPPORT IN APPLESHARE PC

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

Guide to Importing Data

SMS Relay. API Documentation SPLIO - SPRING Contact and Campaign SMS Relay API - EN v1.2.docx

ezeesms URL API Documentation

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

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.

Veritas SaaS Backup for Salesforce

Version March 7, 2012

Veritas SaaS Backup for Office 365

One station Impact Printer. Model: WP-300 Version : 1.03

JAVELIN FLX USER GUIDE

CMe2100/CMi21xx Operations guide English v 1.0

Requirement Document v1.1 WELCOME TO CANLOG.IN. API Help Document. Version SMS Integration Document

ERNST. Environment for Redaction of News Sub-Titles

New Dashboard - Help Screens

Certification Test Plan SSRF Conformance for OpenSSRF Software v Document WINNF-14-S-0023

Alphanumeric Operator Display

Representing Characters, Strings and Text

WLAN Connection Manual. Mobile Printer SPP-R300 SPP-R400.

SurePassID Local Agent Guide SurePassID Authentication Server 2016

PJ-600 Series Printer ESC/P Command Reference

Configuring SMS Gateways on GateManager

TM-H6000V. WebConfig API User's Manual. Overview. Web API Specification. Reference. M Rev.A. Describes an overview of WebConfig API.

Homework 4 assignment for ECE374 Posted: 04/06/15 Due: 04/13/15

Communication and processing of text in the Kildin Sámi, Komi, and Nenets, and Russian languages.

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

Note 8. Internationalization

API Specification Doc

Oracle Primavera P6 Enterprise Project Portfolio Management Performance and Sizing Guide. An Oracle White Paper December 2011

REST SERVICE. Web Services API Version 1.5

SMS Mobile Termination (MT) API Guide for HTTPS

Cartons (PCCs) Management

Sabine Dolderer, DENIC eg

Technical Guide. REST API for Mobile Outbound SMS

SMS Outbound. SMTP interface - v1.1

GSM GSM TECHNICAL March 1996 SPECIFICATION Version 5.1.0

General Information 1. Connection 2. User Interface 3 ATC5300. Menus 4. Automatic Transfer Controller. Remote Control Software Manual A5E

State of Connecticut Workers Compensation Commission

Transcription:

Redrabbit Cloud-based Communications Platform SMS APIs Prepared by US Office 8530 Crows Ct. Tampa, Florida 33647 Jordan Office Adnan Halawa Center, Industrial Road

Biader Wadi AL-Seer Amman Jordan www.javna.com Notice of Disclaimer While every precaution has been taken in the preparation of this document, I assume no responsibility for errors, omissions, or for damages resulting from the use of the information herein. Product or corporate names may be trademarks or registered trademarks of other companies and used for its explanation and evaluation, without intent to infringe. Copyright 2017 by Javna wireless software solutions. All Rights Reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system or translated into any language in any form by any means without the written permission of Javna wireless software solutions. Javna 2/7

HTTP API There are two main operations/requests that you will be using: send message and query status of a sent message. A. Send Message: This request is used to send messages to the RedRabbit gateway, the API will use HTTP POST or GET methods, but for sending large data it is recommended to use POST method, like sending the message content for more large number of recipients. Request: The expected input parameters for this request type are the following: 1. LoginName: String - The user name provided when the account is opened. 2. Password: String - The password of the account. Type String. 3. MessageBody: String UTF8 string that can contain English and Unicode characters, if the message is onepart English it can contain up to 160 characters and if the message is one-part Unicode it can contain up to 70 characters. If the message is longer than that the message will be sent in more than one part where each part in English will contain 153 characters and Unicode will contain 67 characters. Message content for Unicode could be sent using Hex-string format 4. MessageRecipients: String - A comma separated string that includes mobile numbers of message recipients, the acceptable format of mobile numbers should have no special characters, no spaces, nor area code zeroes, for example: 962777338555. The maximum number of recipients per request is 50 and there should be no duplicate numbers in a message, if any duplicate number is found then the message will be sent only once for the recipient. 5. SenderName: String - A value of maximum 11 characters none of them should be Unicode, this is the name that will be viewed on mobile when message is received by recipient 6. MsgTyp: The type of the message as per below table: Message Type Description 4 SMS 5 Long SMS 9 Unicode Hex-String 10 Long Unicode Hex-String 12 WAP Push Javna 3/7

13 Binary 14 Flash 15 Long Flash 16 Flash Unicode Hex String 17 Long Flash Unicode Hex String Response: When a request is sent to the gateway with valid values for the above parameters, the gateway will process the input data, validate the user name and password, create the message and respond with the following responses in a string that you can read as HTTP response: Example response will be: Error=0<BR>Message_Id=303391206<BR> 1. Error: Integer - the value of the error will be 0 if your request was processed successfully or an error code if there was any error, possible error numbers are: a. 1: Invalid user-name or password b. 2: Error in input parameters. c. 3: Insufficient Credit. 2. Message_Id: Integer - value that represents the Id of this message that is sent to the recipients, the value should be saved to query its status later. HTTP API URLs for Sending Messages: 1. Send a message URL: http://http1.javna.com/epicenter/gatewaysend.asp Example text message http://http1.javna.com/epicenter/gatewaysend.asp?loginname=xxxx&password=xxxx& MessageRecipients=962777232069&MessageBody=hi&SenderName= xxx if the message content is too long or the number of recipients is large, then use the URL with HTTP POST method Example Hex-String format http://http1.javna.com/epicenter/gatewaysend.asp?loginname=xxx&password=xxx&msgtyp=9&message Recipients=962777232069&MessageBody=06270644062B06440627062B06270621&SenderName=xxx Long SMS Message / Unicode / Hex-String Format Javna 4/7

http://http1.javna.com/epicenter/gatewaysendg.asp?loginname=xxx&password=xxx&msgtyp=10&messa gerecipients=962777232069&messagebody=06270644062b06440627062b06270621&sendername=xxx FLASH SMS Message http://http1.javna.com/epicenter/gatewaysendg.asp?loginname=xxxx&password=xxxx=1&msgtyp=14&m essagerecipients=962777232069&messagebody=hi& SenderName=xxx FLASH Long SMS Message http://http1.javna.com/epicenter/gatewaysendg.asp?loginname=xxxx&password=xxxx=1&msgtyp=15&m essagerecipients=962777232069&messagebody=hi& SenderName=xxx FLASH SMS Message / Unicode / Hex-String Format http://http1.javna.com/epicenter/gatewaysendg.asp?loginname=xxx&password=xxx&msgtyp=16&messa gerecipients=962777232069&messagebody=06270644062b06440627062b06270621&sendername=xxx FLASH Long SMS Message / Unicode / Hexa Format http://http1.javna.com/epicenter/gatewaysendg.asp?loginname=xxx&password=xxx&msgtyp=17&messa gerecipients=962777232069&messagebody=06270644062b06440627062b06270621&sendername=xxx Wap Push Message To send a WAP push message, you will need to follow the following simple rule for the content as the example below: wp http://www.yahoo.com Salam as you can see, the first part contains " wp" for wap push, then " URL" for the target URL, then Content the content that will appear in the received message keep in mind that this content should be kept small for the message to be sent successfully http://http1.javna.com/epicenter/gatewaysendg.asp?loginname=xxx&password=xxx&msgtyp=12&messag erecipients=xxxxxxx&messagebody= wp http://ww w.yahoo.com S&SenderName=xxx B. Query Tracking: This request is used to query the status of a previously sent message; this API will be used each time to check for the message status. Javna 5/7

Request: The expected input parameters for this request type are the following: 1. LoginName: String - The user name provided when the account is opened 2. Password: String - The password of the account. Type String 3. Message_Id: Integer - message Id that was generated by the gateway upon sending the message successfully. Response: When sending a request to the gateway with valid values for the above parameters, the gateway will process input data and send you back the following response: Example response will be: Error=0<BR>MessageRecipients=962777232069,<BR>Statuses=1,<BR> 1. Error: Integer - the value of the error will be 0 if your request was processed successfully or an error code if there was any error, possible error numbers are: a. 1: Invalid user-name or password b. 2: Error in input parameters. 2. MessageRecipients: String - a Comma-Separated string that contains all the recipients' mobile numbers for this message. 3. Statuses: String - A comma-separated string that contains the statuses of each single message sent for each recipient in the same order of the MessageRecipients string. Status numbers are as in the following table: Status Type Description 1 Delivered to Mobile (Final Status) 2 Failed (Final Status) 3 Sent (intermediate Status) HTTP API URLs for Status Inquiry http://http1.javna.com/epicenter/gatewayquerytrack.asp Track message statuses API example http://http1.javna.com/epicenter/gatewayquerytrack.asp?loginname=xxxx&password =xxxx&message_id=xxxxx Javna 6/7

B. Query Credit: This request is used to query the credit in SMS. Request: The expected input parameters for this request type are the following: 1. LoginName: String - The user name provided when the account is opened 2. Password: String - The password of the account. Type String Response: When sending a request to the gateway with valid values for the above parameters, the gateway will process input data and send you back the following response: Example response will be: Error=0<BR>Remaining Credit=2549079.00 SMS <BR> 1. Error: Integer - the value of the error will be 0 if your request was processed successfully or an error code if there was any error, possible error numbers are: a. 1: Invalid user-name or password b. 2: Error in input parameters. 2. Remaining Credit: String a value for the remaining credit in SMS. HTTP API URLs for Remaining-Credit Inquiry http://http1.javna.com/epicenter/gatewayremainingcredit.asp Remaining-Credit API example http://http1.javna.com/epicenter/gatewayremainingcredit.asp?loginname=xxxx&password=xxxx Character-Set: English Characters that are allowed for the Text messages that will be sent as 160 characters: [New line] 10 [carriage return] 13 [space]! " # $ % & ' ( ) * +, -. / 0 1 2 3 4 5 6 7 8 9 : ; < = >? @ A B C D E F G H I J K L M N O P Q R S T U V W X Y Z _ a b c d e f g h i j k l m n o p q r s t u v w x y z Ä Å Æ Ç É Ñ Ø Ü ß à ä å æ è é ì ñ ò ö ø ù ü Ö Unicode Any Unicode character can be sent to the gateway like Arabic, Chinese, etc. Javna 7/7