API Documentation. Release Version 1 Beta

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

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

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

HTTP API-HELP DOCUMENT

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

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

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

HTTP API. Table of Contents

Account Activity Migration guide & set up

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

Message parameter details

HTTP API Specification V2.7

Account Activity Migration guide & set up

SMS HTTP API DOCUMENTATION December 2012

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

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

Bulk HTTP API Specification

SMS Outbound. SMTP interface - v1.1

API Spec Sheet For Version 2.5

API Integration Guide

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

SMS Submit Interface description HTTP Version 1.5

Cloud SMS API Guide. Version 5.1

BulkSMS Marketo Gateway

REST SERVICE. Web Services API Version 1.5

SMS Outbound. HTTP interface - v1.1

We currently are able to offer three different action types:

Report API v1.0 Splio Customer Platform

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

If the presented credentials are valid server will respond with a success response:

HTTP API - HELP DOCUMENT

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

NIC SMS SERVICE INTEGRATION

Ciphermail Gateway PDF Encryption Setup Guide

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

Technical Guide. REST API for Mobile Outbound SMS

ezeesms URL API Documentation

HappyFox API Technical Reference

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

Partner Web Services. GetOrderStatus Version 1 Service Manual

User Manual RouteSms SmsPlus Desktop. Version 1.0

Gatesms.eu Mobile Solutions for Business

SMS-Bulk Gateway HTTP interface

HTTP Specification Version 1.83

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

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

HTTP Based Unified API

Moxie Notifications Documentation

1. Overview Account Configuration Details... 3

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

Samples using API. User Guide

ARTIO SMS Services HTTP API Documentation

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

Integration Guide Xura Messaging SMTP- Interface

API Integration Document

SMS+ Client User Manual

MultiTexter.com Smart Messaging System. HTTP Application Programming Interface

Shopitem API A technical guide to the REST API for managing updates of shopitems

YIFTEE REWARDS DEVELOPER GUIDE

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

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

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

Quick Answers. You may create any Sender ID for the transactional route, provided the Sender ID should be of 6 alpha characters only.

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

XML API Developer-Documentation Version 2.01

PonyExpress API V1. The PonyExpress API allows you to perform operations that you do with our web client.

API HTTP / HTTPS INTEGRATE THE SMS IN YOUR APPLICATIONS, YOUR WEBSITE AUTOMATE YOUR TEXT OF SHIPMENTS SETTING SINGLE PLACE WITHOUT ADDITIONAL COST

Web Service API for. Document version 0.5 (2015-8) (Draft)

XML API SMS GATEWAY. Issue 2.0 Dec XML API

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

Unity SDK for Xiaomi (IAP) Unity IAP provides an easy way to integrate Xiaomi IAP with Unity.

UReport USSD application Documentation

Requests that are forwarded via redirects by a customer's web browser are authenticated via browser API authentication.

Reseller Web Site Instructions Manual

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

The Merit Palk API allows 3rd party developers to expand and build on the Merit Palk platform.

mvaayoo API Ver 1.2.0

Integration Architecture Of SDMS

vrealize Log Insight Developer Resources

vrealize Log Insight Developer Resources Update 1 Modified on 03 SEP 2017 vrealize Log Insight 4.0

API Guide. Version 2.3

Document version: 3.1

Contents Overview... 3 Steps to run an Excel Add-In Setup:... 4 Add-Ins LOGIN SEND SMS Send Text or Flash Sms... 1

External Trigger SDK. for. Version 4.5

PCCW mobile SMS Web Access 2.0 User Guide

STATS API: AN INTRODUCTION

Integration REST Text2Speech Version 1.1

SMS4BD Gateway Integration

JobFeed Push Services

EBULKSMS

Partner Web Services. GetMyPrice Service Manual

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

Integration Guide Xura Messaging HTTP-Interface

Quick help quide to GSM PDU mode structure

Partner Integration API Details

Instructions for Using New API. Instructions for Using New API

Zipwhip API Developer Reference Messaging API

1. Sending SMS using any client 2. Outlook Mobile Service (OMS) integrated SMS sending via outlook 2007 and 2010

TACHO ONLINE API. TUNGVOGNSSPECIALISTEN APS Københavnsvej 265, DK-4000 Roskilde

Consents Service - SMBC NextGenPSD2

Transcription:

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 contents 1 Base URL 2 Authentication 3 Methods 3.1 Send SMS 3.1.1 Request Parameters 3.1.2 Response 3.1.2.1 Success 3.1.2.2 Error 3.1.3 Settings 3.1.4 Callback URL 3.1.4.1 Settings 3.2 Get a list of sent transactions 3.2.1 Request Parameters 3.2.2 Response 3.2.2.1 Success 3.2.2.2 Error 3.3 Get a single sent transaction 3.3.1 Request Parameters 3.3.2 Response 3.3.2.1 Success 3.3.2.2 Error 3.3.3 Settings PROMOTEXTER V3 BETA - API Documentation 2

1 Base URL All requests to Promotexter API must be submitted to the base URL using GET or POST method. When using POST, set the Content-Type header to application/json and pass the parameters in the payload. https://rest-portal.promotexter.com 2 Authentication All API requests must come with these mandatory parameters : Parameter apikey apisecret Description API Pass Key set for the user API Secret Key Password set for the user These parameters are managed in the user management module in the web tool. Obtain your apikey and apisecret using the API Key Generation feature from the Promotexter Menu once logged in: https://portal.promotexter.com/settings/api-settings/authentication-settings PROMOTEXTER V3 BETA - API Documentation 3

3 Methods 3.1 Send SMS /sms/send 3.1.1 Request Parameters API Parameters from Required. An alphanumeric string giving your sender address. For example, MyCompany. This is also called the SenderID. SenderIDs must be whitelisted in your account for all mobile carriers to be used. Country-specific restriction applies. <See appendix: Country Specific Features and Restrictions) > to Required. A single mobile number in international format, with country code but without 00 or +, eg 185000000000 (USA), 447890000000 (UK), 852200000000 (HK), 639000000000 (Philippines), Mobile numbers starting with 0 will be treated as a local mobile number of the country set to the account. ie: if this number is used, 061658910 and the country set to the account is Denmark, then 0 will be converted to the country prefix 45. Hence, the number will be re-written to 4561658910. text Required. The SMS body. Message must be in UTF-8 format and URL encoded. Standard - Max 5 parts of SMS (765 standard gsm characters or 335 Unicode characters). Philippines - Max 3 parts of SMS. (459 standard gsm characters) PROMOTEXTER V3 BETA - API Documentation 4

referenceid dlrreport dlrcallback This is an ID that the client can send with the API call for identifying the multiple transactions in the client system. Set to 1 to receive Delivery Receipt. A URL endpoint to where the DLRs will be forwarded. This is required if dlrreport is set to 1 3.1.2 Response 3.1.2.1 Success JSON Response { status : ok, message : { id : <generated uuid>, unitcost : <cost of the transaction>, messageparts : <message parts>, transactioncost : <transaction price>, remaining : <remaining balance>, from : <from>, to : <internationalized value of TO param>, operatorcode : <operator code>, source : <ip address of sender> } } Response fields Key id unitprice transactionprice messageparts Value A unique identifier of the transaction assigned by the Promotexter API. We will be using the <id> when we send the DLR The price of the message per part The price of the transaction. This is basically <unitprice> * parts The number of SMS parts the message has PROMOTEXTER V3 BETA - API Documentation 5

remaining from to operatorcode How much credit left in the account The < from > parameter in the request The < to > parameter in the request This is the operator the mobile number < to > parameter is tagged with. 3.1.2.2 Error JSON Response { statuscode : <HTTP Error code>, error : <HTTP error description>, message : <error extended description> } Error types: HTTP Error Code Type Description 401 Authentication Error apikey and apisecret must be valid and active 400 Missing Parameter Required params: apikey apisecret from to text 400 Invalid mobile number to parameter - must be a valid mobile number format. No prefix for recipient Number of digits is less than the country min_length or greater than the country max_length 400 Invalid SenderID from parameter - must be whitelisted in the account Sender ID not whitelisted PROMOTEXTER V3 BETA - API Documentation 6

400 Invalid IP If whitelisting is enabled and the source IP is not in the list. 400 Insufficient credit The transaction cost is greater than the remaining balance. No credit 400 DLR Callback Required dlrcallback parameter is required when dlrreport is set to 1 400 Non-Account User User does not belong to an account 400 Message Length Error Message length exceeds the valid message parts (3 for Philippines, 5 for non-philippines) 400 Invalid Callback URL Format Needs at least the http or https protocol, the hostname and the path 429 Sending too fast The number of requests are higher than the set limit Transactions will be rejected. 3.1.3 Settings Sending Speed The number of requests that can be sent in a second. 5 TPS * If you need more speed, please contact your account manager. 3.1.4 Callback URL The DLR can be forwarded to a callback URL either as part of the API call or by configuring it in the account settings. Placeholder variables and what we are going to replace it with: Variable Description Auto-append field %t UTC timestamp will be added here. This _timestamp PROMOTEXTER V3 BETA - API Documentation 7

represents the time we received and forwarded the DLR status %i The generated transaction ID the API returned from the original API request. %d DLR Status Code _id _status 1 - Delivered 2 - Bounced 8 - In-transit 16 - Rejected Alternatively, if the system did not find the variables as listed above, it will automatically append the data using the Auto-append field. The callback URL endpoint must respond with HTTP 200 OK. 3.1.4.1 Settings Variable retries Value 3 retries. The system will request to the callback URL a maximum of 3 times. Request timeout 3 seconds. The system will wait for 3 seconds timeout before cutting the connection if no reply. Please ensure that your system responds within 3 seconds. Forwarding concurrency 30 transactions. Maximum 30 concurrent transactions that we will forward to the callback URL. Request Speed 1 request per second PROMOTEXTER V3 BETA - API Documentation 8

3.2 Get a list of sent transactions /sms/transactions 3.2.1 Request Parameters API Parameters page A number which would represent the wanted page Default: 1 Format: Number limit A number which would represent the number of transactions wanted per page Default: 10 Max: 100 Format: Number datefrom The starting date of the list the client want to pull Default: null Format: YYYY-MM-DD dateto The end date of the transaction list the client want to pull Default: null Format: YYYY-MM-DD to Optional filter. Recipient of the message Default: null Format: Mobile number with country code (e.g.639000000000) from Optional filter. Sender ID used in the transactions Default: null Format: Max. 11 Alpha Characters referenceid Optional filter. Search by referenceid Default: null Format: Alphanumeric max. 32 characters PROMOTEXTER V3 BETA - API Documentation 9

id Optional filter. Search by transaction ID Format: UUID 3.2.2 Response 3.2.2.1 Success JSON Response { status : ok, data : { list : [ { id : <transaction uuid>, referenceid : <referenceid from the original request>, datecreated : <UTC date when the transaction is created>, to : <to>, from : <from>, message : <message>, status : <dlr status>, operatorcode : <operator code>, unitcost : <unit price>, transactioncost : <transaction price>, }, { id : <transaction uuid>, referenceid : <referenceid from the original request>, datecreated : <UTC date when the transaction is created>, to : <to>, from : <from>, message : <message>, status : <dlr status>, operatorcode : <operator code>, unitcost : <unit price>, transactioncost : <transaction price>, } ], limit: <limit parameter>, page: <page parameter>, datefrom : <datefrom>, dateto : <dateto>, } } PROMOTEXTER V3 BETA - API Documentation 10

Response fields Key id unitprice messageparts transactionprice from to operatorcode Value A unique identifier of the transaction assigned by the Promotexter API. We will be using the <id> when we send the DLR The price of the message (per single part) The number of SMS parts the message has. The price of the transaction. This is basically (<unitprice> x parts) The <from> parameter in the request The <to> (mobile number) parameter in the request This is the operator the mobile number <to> parameter is tagged with. 3.2.2.2 Error JSON Response { statuscode : <HTTP Error code>, error : <HTTP error description>, message : <error extended description> } Error types: HTTP Error Code Type Description 401 Authentication Error apikey and apisecret must be valid and active 400 Missing Parameters Required params: apikey apisecret 400 Invalid Date Format Valid date format YYYY-MM-DD PROMOTEXTER V3 BETA - API Documentation 11

400 Invalid Date Range Date from should not be later than the Date To parameter 403 Ip not whitelisted IP Whitelisting is enabled and the IP address is not part of the list 429 Sending too fast The number of requests are higher than the set limit Transactions will be rejected. 3.3 Get a single sent transaction /sms/transactions/{id} 3.3.1 Request Parameters API Parameters id The id generated by the API. 3.3.2 Response 3.3.2.1 Success JSON Response { status : ok, "data": { "id": "778bf5e7-5b28-43bc-b21f-03155ad875d3", "datecreated": "2016-04-01T05:51:52.000Z", "to": "639192516979", "from": "<sender id>", "text": "<message>", "status": "delivered", "operatorcode": "PHL_SMART", "unitprice": 0.975, "transactionprice": 0.975 } } PROMOTEXTER V3 BETA - API Documentation 12

Response fields Key id unitprice transactionprice from to operatorcode status Value A unique identifier of the transaction assigned by the Promotexter API. We will be using the <id> when we send the DLR The price of the message (single part) The price of the transaction. This is basically <unitprice> * parts The <from> parameter in the request The <to> (mobile number) parameter in the request This is the operator the mobile number <to> parameter is tagged with. Delivery status with the following values: in-transit, delivered, bounced, rejected, error 3.3.2.2 Error JSON Response { statuscode : <HTTP Error code>, error : <HTTP error description>, message : <error extended description> } Error types: Error Code Type Description 400 Missing Parameters Required params: apikey apisecret 401 Authentication Error apikey and apisecret must be valid and active 403 Ip not whitelisted IP Whitelisting is enabled and the IP address is not part of the list PROMOTEXTER V3 BETA - API Documentation 13

404 Transaction not found Verify the reference ID 429 Sending too fast The number of requests are higher than the set limit Transactions will be rejected. 3.3.3 Settings Sending Speed The number of requests that can be done in a second. 5 TPS PROMOTEXTER V3 BETA - API Documentation 14