SMS HTTP API

Request format

GET — HTTP

http://smpp.scarpeltele.com:8001/api?username=<username>&password=<password>&ani=<ani>&dnis=<dnis>&message=<message>&command=submit&serviceType=<serviceType>&longMessageMode=<longMessageMode>

GET — HTTPS

https://smpp.scarpeltele.com:8002/api?username=<username>&password=<password>&ani=<ani>&dnis=<dnis>&message=<message>&command=submit&serviceType=<serviceType>&longMessageMode=<longMessageMode>

POST — credentials in the URL query string

curl -H 'Content-Type: application/json' -X POST \ -d '{"ani":"ani","dnis":"dnis","message":"test"}' \ 'http://smpp.scarpeltele.com:8001/api?command=submit&username=username&password=password'

POST — credentials in the JSON body

curl -H 'Content-Type: application/json' -X POST \   -d '{"username":"username","password":"password","command":"submit","ani":"ani","dnis":"dnis","message":"test"}' \ 'http://smpp.scarpeltele.com:8001/api?'

NOTE: To send multiple SMS messages, add several comma-separated DNIS values to the dnis field.

Response format

In case of successful processing, the status in the header of the HTTP response is 200 OK. Response body contains the message_id.

Single DNIS — success

HTTP/1.1 200 OK
Content-Type: application/json

{"message_id":"alss-a1b2c3d4-e5f67890"}

When the request contains more than one DNIS (comma-separated) or longMessageMode=split/split_sar with a message longer than 160 / 70 symbols (GSM / Unicode), the response will look as follows:
Multiple DNIS or long message split — success

HTTP/1.1 200 OK
Content-Type: application/json
[ {"dnis":"34511121","message_id":"5b4c46a8-8dc9-44b4-f55f-3bef56819305", "segment_num":"1"}, {"dnis":"34511121", "message_id":"5b4c46a8-46bc-7ee6-4a16-7d4e5a0d14af","segment_num":"2"} ]

400 Bad Request — no routes

HTTP/1.1 400 Bad Request
Content-Type: text/html; charset=UTF-8

NO ROUTES

401 Unauthorized

HTTP/1.1 401 Unauthorized
Content-Type: text/html; charset=UTF-8

not authorized (check login and password)

400 Bad Request — invalid service type

HTTP/1.1 400 Bad request
Content-Type: text/html; charset=UTF-8

Service type is invalid

508 Loop Detected

HTTP/1.1 508 Loop Detected
Content-Type: text/html; charset=UTF-8

loop detected

SMS status request

The links below are intended for request of delivery reports over HTTP from the client side.

Request format

http://smpp.scarpeltele.com:8001/api?username=<username>&password=<password>&messageId=<messageId>&command=query

https://smpp.scarpeltele.com:8002/api?username=<username>&password=<password>&messageId=<messageId>&command=query

All parameters are required.

Status Values

Response sample — success

HTTP/1.1 200 OK
Content-Type: application/json

{"status":"DELIVRD","delivery_time":"20210922093309","mccmnc":"214099","error_code":"000","system_delivery_time":"210922093309"}

Where: delivery_time — done date from the vendor (empty if not received); mccmnc — E212 code;error_code — delivery error code; system_delivery_time — delivery report receipt time by the system (format: YYMMDDHHMMSS).

The status can be requested within 24 hours after the message submission.

Response sample — message ID not found

HTTP/1.1 200 OK
Content-Type: application/json

{"status": "UNKNOWN","delivery_time": "","mccmnc": ""}

401 Unauthorized

HTTP/1.1 401 Unauthorized
Content-Type: text/html; charset=UTF-8

not authorized (check login and password)

Allowed marker names for outgoing HTTP callbacks

This section contains allowed marker names for outgoing HTTP callbacks (sending of delivery reports with the help of cURL in a generated script).

It is possible to specify the _noencode suffix for markers to transmit text without URL encoding. Example:

curl

'http://smpp.scarpeltele.com/api/callback/api?msgid=$message_id$&state=$delivery_status$&reasoncode=$result_code$&to=$dnis$&time=$done_date_noencode$&msgid=$messageId$&mcc=$mcc$&mnc=$mnc$'

Deliver markers

Last updated: 23 April 2026