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

”ѕ–ј¬Ћ≈Ќ»≈  ќЌ“ј “јћ»

CLIENT MANAGEMENT

MANAGING SENDER NAMES (SENDER ID)

GETTING DATA

VARIOUS

Managing sender names (Sender ID)

List of available operations with sender names

To manage the names of senders, you must call the appropriate address using the GET or POST method, specifying the required command and parameters.

To get a list of senders ' names registered in your personal account and approved by the moderator: https://smscentre.com/sys/senders.php?get=1&login=<login>&psw=<password>
To add a new sender name: https://smscentre.com/sys/senders.php?add=1&login=<login>&psw=<password>&sender=<sender>&cmt=<cmt>
To change the sender's name: https://smscentre.com/sys/senders.php?chg=1&login=<login>&psw=<password>&sender=<sender>&cmt=<cmt> or https://smscentre.com/sys/senders.php?chg=1&login=<login>&psw=<password>&id=<id>&cmt=<cmt>
Sending a confirmation code for the sender's digital name: https://smscentre.com/sys/senders.php?send_code=1&login=<login>&psw=<password>&sender=<sender>
Confirmation of the sender's digital name: https://smscentre.com/sys/senders.php?check_code=1&login=<login>&psw=<password>&sender=<sender>&code=<code>
To delete the sender's name: https://smscentre.com/sys/senders.php?del=1&login=<login>&psw=<password>&sender=<sender> or https://smscentre.com/sys/senders.php?del=1&login=<login>&psw=<password>&id=<id>
ѕри добавлении или изменении имени отправител€ в теле запроса можно передавать файл документа дл€ операторов (свидетельство на товарный знак, сертификат на домен) в формате jpg, tif, pdf, png, zip, rar. ћаксимальный размер передаваемого файла не должен превышать 3 ћб.  омментарий к документу может быть указан в дополнительном параметре doc_info.

Description of parameters

Description of the parameters passed to the Server:

OptionThe value
loginCustomer Login.
pswClient Password (you can add or change it on this page).
all0 (default) - get a list of activated sender names.
1 Ц get a complete list of sender names.
senderThe sender name that is being created or deleted.
mts_step1 Ц register a paid name with the MTS operator.
tele21 Ц register a name with the Tele2 operator at the tariff with free names.
mega_step1 Ц register a paid name with the Megafon operator.
bee_step1 Ц register a paid name with the Beeline operator.
motiv_step1 Ц register a paid name with the MOTIV operator.
tele2_step1 Ц register a paid name with a Tele2 operator.
mega_int1 Ц enable replacement with a common name for the Megafon operator.
motiv_int1 Ц enable replacement with a common name for the Motive operator.
mts_int1 Ц enable replacement with a common name for the MTS operator.
ua_reg1 Ц to register a name for Ukraine at a reduced rate of national traffic.
For this tariff, you must additionally pass the following parameters:
fio Ц legal name of the organization (LLC/SPD).
inn Ц EDRPOU/INN.
site Ц Site address (optional parameter).
email Ц E-mail for communication.
address Ц Actual address.
desc Ц Description of the services provided by the sender.
subj Ц Subject (purpose of informing).
ua_int1 Ц register a name for Ukraine at a higher rate for international traffic.
idID of the sender's name, assigned by the Server automatically when creating a new name.
cmtComment specified when creating the sender name.
mail1 Ц add the sender's e-mail address.
nameComment associated with the mail parameter (usually the name of the owner of the e-mail address).
codeCode for confirming the sender's digital name.
siteThe address of the site from which the codes will be sent to confirm the digital names of the senders. This parameter must have been previously added and activated as Sender ID. If omitted, messages will be sent as the sender by default.
site_nameThe site address specified in the text of the message with the confirmation code.
userThe user ID of the subclient to which you apply the specified command.
operators1 Ц add the status code of the sender's name from the operator to the response.
from_dateSelect the names of senders starting from the specified date, for which the name status of any of the operators has been changed. When this parameter is specified, the names are sorted in descending order of the date when the name statuses were changed. DD.MM.YYYY format.
prev_idA unique identifier of the sender's name that is assigned by the Server automatically when the name is created. Used to request a list of names created before the name with the specified ID.
cntThe number of sender names returned when requesting a list of names. The maximum value is 15000.
doc_infoIf a document file for operators is passed in the request body when creating or changing the sender's name, then you can specify a description for the passed file in this parameter.
charsetEncoding of transmitted parameters.

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> Ц код статуса имени отправител€ у соответствующего оператора (0 - ожидает регистрации, 1 - отправлено на регистрацию, 2 - допущено оператором, 3 - не прин€то оператором, 4 - временно отключено, 5 - недостаточно средств на счете, 8 - необходимы подтверждающие документы).
<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"
    }


Examples of actions with sender names

Examples:

Getting a list of sender names:

https://smscentre.com/sys/senders.php?get=1&login=alex&psw=123
Adding a new sender name:

https://smscentre.com/sys/senders.php?add=1&login=alex&psw=123&sender=my_shop&cmt=test
Sending a confirmation code for the sender's digital name:

https://smscentre.com/sys/senders.php?send_code=1&login=alex&psw=123&sender=79999999999
Sending confirmation code to the digital sender name for subclient "subalex" on behalf of "mysite.ru":

https://smscentre.com/sys/senders.php?send_code=1&login=alex&psw=123&sender=79999999999&user=subalex&site=mysite.ru
Confirmation of the sender's digital name:

https://smscentre.com/sys/senders.php?check_code=1&login=alex&psw=123&sender=79999999999&code=338824
Deleting the sender's name:

https://smscentre.com/sys/senders.php?del=1&login=alex&psw=123&sender=my_shop

The server does not accept more than three identical requests within a minute to get a list of available sender names and five requests to create a new sender name to reduce the load and protect against errors and loops in the Client-side program.




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