Pricing plans  Services  API  Partners  About the service  Contacts 
8 (800) 700 7672
Free in Russia
 

Integration with the service (API)

The API allows you to send messages through your projects and services over the HTTP/HTTPS, SMTP, and SMPP protocols. Ready-made libraries in different programming languages connect to your project and help you send messages from anywhere with a single command.


HTTP/HTTPS SMTP SMPP SOAP OMS SMS Commands Libraries and code examples

SENDING MESSAGES

MANAGING MAILING LISTS

MESSAGE STATUSES

CHECKING THE BALANCE STATUS

CONTACT MANAGEMENT

CLIENT MANAGEMENT

MANAGING SENDER NAMES (SENDER ID)

GETTING DATA

VARIOUS

Server response and error codes

If an error occurs, the Server returns the following string:
  • ERROR = N (description)

  • When fmt = 1:
    0,-N

  • When fmt = 2:
    <result>
    <error>description</error>
    <error_code>N</error_code>
    </result>

  • When fmt = 3:
    {
    "error": "description",
    "error_code": N
    }
N Ц error number, can take the following values:

The valueDescription
1Error in parameters.
2Invalid username or password. Also occurs when trying to send a message from an IP address that is not included in the list of allowed by the Client (if such a list was previously configured by the Client).
3Sender name not found.
4The IP address is temporarily blocked.
5Error saving or deleting the sender's name.
7Invalid number format.
8The confirmation code cannot be delivered to the specified number.
9Attempt to send more than three identical requests to get a list of available sender names or five requests to create a new sender name within a minute.
This error also occurs when you try to send fifteen or more requests simultaneously from different connections under the same username (too many concurrent requests).
10The code has already been sent to the specified number. Retry is possible after 8 hours.
11Invalid confirmation code.

If the request is successful, the Server returns a response in the form of a string.

When requesting a list of sender names:
  • when fmt = 0 and all = 0:
    name = <sender>, id = <id>
    ...

  • when fmt = 1 and all = 0:
    <sender>,<id>
    ...

  • when fmt = 2 and all = 0:
    <list>
    <sender id="<id>">sender</sender>
    ...
    </list>

  • when fmt = 3 and all = 0:
    [{
    "sender": "<sender>",
    "id": <id>
    },
    ...]

  • when fmt = 0 and all = 1:
    name = <sender>, status = <status>, id = <id>
    ...

  • when fmt = 1 and all = 1:
    <sender>,<status>,<id>
    ...

  • when fmt = 2 and all = 1:
    <list>
    <sender status="<status>" id="<id>">sender</sender>
    ...
    </list>

  • when fmt = 3 and all = 1:
    [{
    "sender": "<sender>",
    "status": <status>,
    "id": <id>
    },
    ...]

  • with fmt = 0 and operators = 1:
    name = <sender>, mega_step = <mega_step_status>, bee_step = <bee_step_status>, motiv_step = <motiv_step_status>, mts_step = <mts_step_status>, tele2_step = <tele2_step_status>, tele2 = <tele2_status>, ua_reg = <ua_reg_status>, ua_int = <ua_int_status>, mega_int = <mega_int_status>, motiv_int = <motiv_int_status>, mts_int = <mts_int_status>, id = <id>
    ...

  • with fmt = 2 and operators = 1:
    <list>
    <sender mega_step="<mega_step_status>" mega_int="<mega_int_status>" bee_step="<bee_step_status>" motiv_step="<motiv_step_status>" motiv_int="<motiv_int_status>" mts_step="<mts_step_status>" mts_int="<mts_int_status>" tele2_step="<tele2_step_status>" tele2="<tele2_status>" ua_reg="<ua_reg_status>" ua_int="<ua_int_status>" id="<id>">sender</sender>
    ...
    </list>

  • with fmt = 3 and operators = 1:
    [{
    "sender": "<sender>",
    "mega_step": "<mega_step_status>",
    "mega_int": "<mega_int_status>",
    "bee_step": "<bee_step_status>",
    "motiv_step": "<motiv_step_status>",
    "motiv_int": "<motiv_int_status>",
    "mts_step": "<mts_step_status>",
    "mts_int": "<mts_int_status>",
    "tele2_step": "<tele2_step_status>",
    "tele2": "<tele2_status>",
    "ua_reg": "<ua_reg_status>",
    "ua_int": "<ua_int_status>",
    "id": "<id>"
    },
    ...]

Where:
<sender> Ц registered and approved sender name.
<mega_status>(up to 01.01.2022), <mts_status>(up to 01.12.2017), <mega_step_status>, <mega_int_status>, <bee_step_status>, <motiv_step_status>, <motiv_int_status>, <mts_step_status>, <mts_int_status>, <tele2_step_status>, <tele2_status>, <ua_reg_status>, <ua_int_status> status code name of the sender have corresponding (0 - awaiting registration, 1 - sent for registration, 2 - tolerated by the operator, 3 - it is not accepted by the operator, 4 - temporarily disabled 5 - insufficient funds in the account, 6 - take another name (conflict), 8 - required documents).
<status> Ц sender Name status (0-waiting for moderation, 1-allowed to use, 2-disabled).
<id> Ц unique identifier of the sender's name (assigned by the Server automatically when creating a name).

If the sender's name has a replacement analog for any operator, then with operators = 1 and fmt = 0,2,3, this replacement will be additionally included in the server response.

When adding a new sender name:
  • when fmt = 0: ID = <id>

  • when fmt = 1: <id>

  • when fmt = 2:
    <sender>
    <id>id</id>
    </sender>

  • when fmt = 3:
    {
    "sender": <id>
    }

Where:
<id> Ц the sender name ID assigned by the Server automatically.

When changing the sender's name, sending the code, confirming and deleting the sender's name:
  • when fmt = 0, 1: OK

  • when fmt = 2:
    <result>OK</result>

  • when fmt = 3:
    {
    "result": "OK"
    }





© 2003Ц2023 SMS Center LLC
License no. 166255
support@smscentre.com
Contacts
Design Ч Artemy Lebedev Studio
Site Information
SMS Center for Android Yandex. Metrica