General Information#
Types of Messages#
Types of messages supported in the API.
Type of message |
REST |
HTTP |
SMPP |
REST_BATCH |
FTP |
|---|---|---|---|---|---|
SMS |
✔ |
✔ |
✔ |
✔ |
✔ |
PUSH |
✔ |
✔ |
✔ |
✖ |
✖ |
VK |
✔ |
✔ |
✔ |
✖ |
✖ |
VIBER |
✔ |
✔ |
✔ |
✖ |
✖ |
FLASHINGCALL (VOICECODE) |
✔ |
✔ |
✔ |
✖ |
✖ |
✔ |
✔ |
✖ |
✖ |
✖ |
|
CARDSMOBILE |
✔ |
✖ |
✖ |
✖ |
✖ |
TELEGRAM |
✔ |
✖ |
✖ |
✖ |
✖ |
TGCODE |
✔ |
✖ |
✖ |
✖ |
✖ |
Important
Note on Telegram Code Delivery
Currently, the implementation supports sending digital authorization codes to subscribers via the Telegram messenger using the HTTP and SMPP protocols. In such requests, the message type must be specified as SMS only. The messages will then be converted to the TG format during processing and delivered to Telegram via Telegram Gateway.
Due to limitations in status processing, this sending method is not recommended.
For sending Telegram codes and flexible verification management, the Partner is advised to use the REST API with the TGCODE type.
Cascading Message Sending#
Types of messages allowed in the cascading message sending.
Type of message |
REST |
HTTP |
SMPP |
REST_BATCH |
FTP |
|---|---|---|---|---|---|
SMS |
✔ |
✔ |
✔ |
✖ |
✖ |
PUSH |
✔ |
✔ |
✔ |
✖ |
✖ |
VK |
✔ |
✔ |
✔ |
✖ |
✖ |
VIBER |
✔ |
✔ |
✔ |
✖ |
✖ |
FLASHINGCALL |
✔ |
✔ |
✔ |
✖ |
✖ |
✔ |
✔ |
✖ |
✖ |
✖ |
|
CARDSMOBILE |
✔ |
✖ |
✖ |
✖ |
✖ |
TELEGRAM |
✔ |
✖ |
✖ |
✖ |
✖ |
TGCODE* |
✔ |
✖ |
✖ |
✖ |
✖ |
Tip
Cascading Message Sending Recommendation
Use the REST API with the TGCODE type for Telegram codes in cascading message sending. The sequence of message types can be configured in any order.