Receive MO SMS / Send free or billed MT SMS
Endpoint URL
Client has to provide URLWorkflow
1. myPAY sends MO SMS JSON object to client as HTTP/S request2. Client responses with MT SMS JSON object back immediately
Sequence Diagram
1. MO SMS JSON request
{
"mosms": {
"id": 123,
"message": "Test",
"gtw_type": 23106,
"src_no": "+421903123456",
"dst_no": "8877",
"hash": "xxx"
}
}
| Parameter | Required | Type | Description |
|---|---|---|---|
id |
required | int32 | Unique ID of MO SMS. Client has to check for duplicity. In case of duplicate request, client has to respond with correct MT SMS JSON response |
message |
required | string | Text of SMS, UTF-8 encoded. Multipart SMS are concatenated. |
gtw_type |
required | int32 | Operator code. (e.g. 23101 - Orange SK, 23102 - Telekom SK, 23103 - Swan SK, 23106 - O2 SK) |
src_no |
required | string(32) | MSISDN in international format, e.g. +421... |
dst_no |
required | string(32) | Destination number, e.g. 8877, 8811, ... |
hash |
required | string(40) | Hex (lowercase) encoded SHA1 HMAC from (id + src_no + dst_no + gtw_type + message) |
2.1 MT SMS JSON response
{
"status":"ok",
"mtsms": {
"id": 123,
"message": "test mt sms",
"bill_key": "MYPAY-00-00",
"hash": "xxx"
}
}
2.2 MT SMS JSON error response
{
"status":"error",
"mtsms":null
}
| Parameter | Required | Type | Description |
|---|---|---|---|
status |
required | string(5) |
Status of SMS processing.
ok - MT SMS with data from mtsms will be used error - Request will be repeated again in 1 minute anything else - the same as error |
message |
required | string(160) | Text message, max. 160 characters, GSM7 alphabet ASCII encoded |
bill_key |
required | string(20) | Dedicated billing code, e.g. MYPAY-00-00 |
hash |
required | string(40) | Hex (lowercase) encoded SHA1 HMAC from (id + message + bill_key) |