1 SMS DIRECT CONNECTION INTRODUCTION

Telkomsel SMS Direct Connection is a suite of applications and tools for the enterprise to leverage
SMS as a enterprise productivity tools. Using Telkomsel SMS Direct Connection, you can enhance
your in-house systems or solutions with SMS alerts, information-on-demand capabilities.

2 APPLICATION PROTOCOL INTERFACE (API)

The available API is as follow.

2.1 Send

In order for Corporate application to send SMS message, Telkomsel Administrator will
assign an username and password. These parameters will be used to authenticate your
application when you submit the request to the service.
SMS sending mechanism is based on a simple http request/response as shown below

Corporate application must have a web-component that is able to request a http GET
method call. The URL of the applications sending component must be configured by
Corporate Application Administrator. This call will be made using plain HTTP, with the
following parameters.
Variable Name
Values & Description
cp_name
Assigned by Telkomsel
pwd
Assigned by Telkomsel
msisdn
MSISDN of the receiver. It includes the country code (CC)
without (+) and the network destination code (NDC)
e.g.62811917676
sms
Message content to be sent to customer (URL-Encoded
content)
Note that the length of this message up to 1000 characters.
If user sends > 1000 characters, Telkomsel Direct
Connection Server will cut it.
URL Example:
http://123.123.123.123:9002/submit.jsp?cp_name=<cp_name>&pwd=<password>&msisd
n=<msisdn_number>&sms=<sms_content>
Example
Assuming
- cp_name = corporate1
- pwd = difpass123
- msisdn = 62811917676
- sms content = Test Message
Corporate application invokes an http GET command with the following details:
URL: http://123.123.123.123:9002/submit.jsp
Parameter:
cp_name = corporate1
pwd = difpass123
msisdn = 62811917676
sms content = Test+Message

Telkomsels Direct Connection Server will return http response with the following
parameter.
Value
Values & Description
0
Parameter error
5
Account is blocked
4
Account not found
1:trx_id
SMS sending success with reference of trx_id. Corporate application should
keep the trx_id for reference
8
Internal Telkomsel problem
(Optional) Telkomsels Direct Connection Server will also invokes an http GET command
after a succesfull sent message to Mobile User (delivery report). Corporate application
must have a web-component that is able to receive a http GET method call. The URL of
the delivery report applications component must be configured by Corporate
Application Administrator, with the following parameter
Variable Name
Values & Description
trxid
Reference from the previous sms sending process
status
1. Single or multiple value D , if the SMS is succesfully
delivered to Mobile User (amount of D related to the
length of the SMS)
URL Example: http://123.123.123.123/delreport.ext?trxid=<trxid>&status=<status>
Example
Assuming the receive path of the Corporate Applications delivery report
component is:
- http://123.123.123.123/delreport.ext
In an event of a successful sent message Telkomsel Direct Connection Server
invokes an http GET command with the following details:
URL: http://123.123.123.123/delreport.ext
Parameter:
trxid=134492180128247209085
status=DD

2.2 Receive

Corporate application must have a web-component that is able to receive a http GET
method call. The URL of the applications receiving component must be configured by
Corporate Application Administrator. This call will be made using plain HTTP.

Mobile User send SMS to specific short number (ADN), e.g. 9009, using specified
SENDERID keyword followed by specified delimiter (#) and message content.
Telkomsels Direct Connection Server will first check whether the mobile user is
authorized to use the service. Telkomsel will pass the request to the Corporate
Application to check whether the number is authorized with following parameters
Variable Name
Values & Description
msisdn
MSISDN of the sender. It includes the country code (CC)
without (+) and the network destination code (NDC)
e.g.62811917676
URL Example: http://123.123.123.123/checkmember.ext?msisdn=<msisdn_sender>
Example
Assuming the receive path of the Corporate Applications check member
component is:
- http://123.123.123.123/checkmember.ext
Mobile user send SMS to ADN e.g. 9009 with the following format
- SENDERID#Test+Message.
Telkomsel Direct Connection Server receives incoming SMS and determines it
need to be routed to Coporate Application Server based on the SENDERID
keyword. It will check the corresponding SENDERID mapping with Corporate
Applications receive component ULR and invokes an http GET command with
the following details:
URL: http://123.123.123.123/checkmember.ext
Parameter:
msisdn= 628111987765

Telkomsels Direct Connection Server will expect an acknowlegment code 1 or 0 to be

returned by the application.
Value
Values & Description
1
MSSIDN is authorized. Server will proceed the second step to send the actual
message to Corporate Application.
0
MSSIDN in not authorized. Server will send SMS notification to mobile user
that he is not authorized to use the service.
Notification = Anda tidak terdaftar sebagai member SENDERID

After a successful authorization process, Telkomsels Direct Connection Server will

proceed to send the actual SMS message. Telkomsel will pass the request to the
Corporate Application with following parameters
Variable Name
Values & Description
msisdn
MSISDN of the sender. It includes the country code (CC)
and the network destination code (NDC) e.g.62811917676
msg
Message content sent from customer (URL-Encoded
content)
Note that the length of this message cannot exceed 160
characters. If a mobile user sends > 160 characters,
Telkomsel Direct Connection Server will discard it.
URL Example:
http://123.123.123.123/smsreceive.ext?msisdn=<msisdn_sender>&msg=<sms_content>
Example
Assuming the receive path of the Corporate Applications receive component is:
- http://123.123.123.123/smsreceive.ext
Mobile user send SMS to ADN CAM e.g. 9009 with the following format
- SENDERID#Test+Message.
Telkomsel Direct Connection Server receives incoming SMS and determines it
need to be routed to Coporate Application Server based on the SENDERID
keyword. It will check the corresponding SENDERID mapping with Corporate
Applications receive component ULR and invokes an http GET command with
the following details:
URL: http://123.123.123.123/smsreceive.ext
Parameter:
msisdn=628111987765
msg= SENDERID#Test+Message