HTTP Configuration

Class Location Configuration of the vendor on B-Pal
1) GET:
Class Location = SMSGatewayProvider.Http.GlobalHttpVendorSmsProvider
2) POST:
Class Location = SMSGatewayProvider.Http.GlobalPostHttpVendorSmsProvider
First, we need to check the API documentation of vendor:
We have two method
1) GET
2) POST
1) In case of GET:
The API will contains all the details (Username, Password, Sender, Content, destination).
Just we need to configure the API of client into the system in section Http Submit Url
For example:
We have the below URL API shared by vendor (API documentation)
http://202.43.173.178/smsotp/v4/sendSMS/?username=xxxxx&password=xxxxxxx&destination=xxxx&s
ource=xxxxxx&text=xxxxxx
Just we need to fill our variable into the API URL to make sure that they will sync as well
http://202.43.173.178/smsotp/v4/sendSMS/?username=[Username]&password=[Password]&destinati
on=[Destination]&source=[Source]&text=[Content]
Postman Test:
1) Choice Get Method
2) Put the API

3) We need to fill the parameters with its related value then press send.
2) In case of POST
The section of Http Submit Url will contain only the API shared by vendor without any other details.
The request Body will contains all the parameters (Username, Password, Sender, Content, destination).
For get
http://202.43.173.178/smsotp/v7/sendSMS/index.php?username=[Usernamdestination=[Destination]&
source=[Source]&e]&password=[Password]&text=[Content]
For example:
1) We have the below URL API shared by vendor (API documentation)
http://sms.sahridaya.id/api/apisms
2) Just we need to fill our variable into the Body shared by vendor.
{"username":"xxxxxx","password":"xxxxxx","msisdn":" xxxxxx ","message":" xxxxxx ","sender":" xxxxxx "}
But for body our gateway use PHP language then the variable will be as show below:
{"username":"$username$","password":"$password$","msisdn":"$destination$","message":"$content
$","sender":"$source$"}
Note: The body will be different from vendor to other and maybe will have another variable.
In this case, we need to check with Team Leader.
3) In POST case the postman test will be the main part of the configuration of the account for the below
sections:
1. Success Response
2. Terminator MessageId Regex
3. DLR Terminator MessageId Regex
Please follow the above highlighted steps in order to test using postman.
3) In addition to postman we need to use this website https://regex101.com/ in order to configure the
regex sections (Match the MSG ID)
In this case, the regex match different from vendor to other so we need to check with team leader.
But for this example the we can fill the sections as shown below:
Success Response: "ErrorCode":0 (It’s different from vendor and other and we can put
"Description":"Ok")
The terminator MSGID Regex below means that we have match first group “Id": and to take it’s value
by this regex (.\d*)
Terminator MessageId Regex: "Id":(.\d*)
DLR Message State Regex: 2
And the below have the samle value of the terminator msgid regex
DLR Terminator MessageId Regex:"Id":(.\d*)
Once all the above steps are done we can test using the prefix of vendor by our testing tool
And if all are correct the message status will be sent and if not the Status will be Rejected.
Note: if the Status are Rejected, Please contact the Team leader in order to check further).
4) Now, we need to share our API of DLR to let the supplier return the DLR of the SMS and they already
included in our API documentation
We have two type of DLR and we can use one of them:
1) DLR Normal Listener API
Primary:
https://httpsmsc.montymobile.com/HTTP/api/Vendor/DLRListener?username=XXXX&password=XXXX&
sender=XXXX&destination=XXXXXXXXXX&messageId=14fce738-d50a-46b6-
9e8a4b83444bae6e&deliveryStatus=2&dateReceived=2/26/2019%2012:00:00%20AM&description=Deli
vered
GR:
https://httpsmsc02.montymobile.com/HTTP/api/Vendor/DLRListener?username=XXXX&password=XXX
X&sender=XXXX&destination=XXXXXXXXXX&messageId=14fce738-d50a-46b6-
9e8a4b83444bae6e&deliveryStatus=2&dateReceived=2/26/2019%2012:00:00%20AM&description=Deli
vered
2) DLR Listener Basic
In this API we need to open SMS Gateway Monitor in order to get the ID of the created vendor.
For example:
We need to put the ID in the below URLS and share them with the vendor:
Primary:
https://httpsmsc.montymobile.com/HTTP/api/Vendor/DLRListenerBasic?ConnectionId=
6312&MessageId=VyPpdRas4wJo5&Status=2
GR:
https://httpsmsc02.montymobile.com/HTTP/api/Vendor/DLRListenerBasic?ConnectionId=
4658&MessageId=VyPpdRas4wJo5&Status=2

HTTP Configuration

Uploaded by

Copyright:

Available Formats

HTTP Configuration

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HTTP Configuration

Uploaded by

Copyright:

Available Formats

Class Location Configuration of the vendor on B-Pal

Class Location = SMSGatewayProvider.Http.GlobalHttpVendorSmsProvider

Class Location = SMSGatewayProvider.Http.GlobalPostHttpVendorSmsProvider

First, we need to check the API documentation of vendor:

We have two method

We have the below URL API shared by vendor (API documentation)

1) Choice Get Method

2) Put the API

1) We have the below URL API shared by vendor (API documentation)

{"username":"xxxxxx","password":"xxxxxx","msisdn":" xxxxxx ","message":" xxxxxx ","sender":" xxxxxx "}

In this case, we need to check with Team Leader.

Terminator MessageId Regex: "Id":(.\d*)

DLR Message State Regex: 2

DLR Terminator MessageId Regex:"Id":(.\d*)

We have two type of DLR and we can use one of them:

1) DLR Normal Listener API

You might also like