Register an SMS Provider or Message Provider messageservice.sender.add
If you are developing integrations for Bitrix24 using AI tools (Codex, Claude Code, Cursor), connect to the MCP server so that the assistant can utilize the official REST documentation.
Scope:
messageserviceWho can execute the method: administrator
The method messageservice.sender.add registers a new message provider.
This method works only in the context of an application.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
CODE* |
Provider code. Allowed characters: |
|
TYPE* |
Provider type. Supported value: |
|
HANDLER* |
Application handler URL that is called when sending a message. The data that comes to the handler is described below |
|
NAME* |
Provider name. Can be a string or an associative array of localized strings like:
|
|
DESCRIPTION |
Provider description. Can be a string or an associative array of localized strings like:
|
What Comes to the Handler
|
Name |
Description |
|
module_id |
Module from which the message was sent. Possible values:
|
|
bindings |
Array of message bindings to CRM entities. Parameter comes if |
|
workflow_id |
Workflow identifier. Parameter comes if |
|
document_id |
Identifier of the workflow document. Parameter comes if |
|
document_type |
Type of the workflow document. Parameter comes if |
|
properties |
Object with message parameters |
|
type |
Provider type. Possible value: |
|
code |
Provider code |
|
message_id |
Unique message identifier. Use it in the messageservice.message.status.update method to update the message status |
|
message_to |
Recipient's message number |
|
message_body |
Message text |
|
ts |
Time of the request in Unix Timestamp format |
|
auth |
Application authorization data |
Properties Object
|
Name |
Description |
|
phone_number |
Recipient's message number |
|
message_text |
Message text |
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"CODE":"provider1","TYPE":"SMS","HANDLER":"https://provider.example/api/handler","NAME":"Provider 1","DESCRIPTION":"Main SMS provider","auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/messageservice.sender.add
try
{
const response = await $b24.callMethod(
'messageservice.sender.add',
{
CODE: 'provider1',
TYPE: 'SMS',
HANDLER: 'https://provider.example/api/handler',
NAME: 'Provider 1',
DESCRIPTION: 'Main SMS provider'
}
);
const result = response.getData().result;
console.log(result);
}
catch (error)
{
console.error('Error:', error);
}
try {
$response = $b24Service
->core
->call(
'messageservice.sender.add',
[
'CODE' => 'provider1',
'TYPE' => 'SMS',
'HANDLER' => 'https://provider.example/api/handler',
'NAME' => 'Provider 1',
'DESCRIPTION' => 'Main SMS provider',
]
);
$result = $response
->getResponseData()
->getResult();
print_r($result);
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error adding sender: ' . $e->getMessage();
}
BX24.callMethod(
'messageservice.sender.add',
{
CODE: 'provider1',
TYPE: 'SMS',
HANDLER: 'https://provider.example/api/handler',
NAME: 'Provider 1',
DESCRIPTION: 'Main SMS provider'
},
function(result)
{
if (result.error())
{
console.error(result.error(), result.error_description());
}
else
{
console.log(result.data());
}
}
);
require_once('crest.php');
$result = CRest::call(
'messageservice.sender.add',
[
'CODE' => 'provider1',
'TYPE' => 'SMS',
'HANDLER' => 'https://provider.example/api/handler',
'NAME' => 'Provider 1',
'DESCRIPTION' => 'Main SMS provider',
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Response Handling
HTTP status: 200
{
"result": true,
"time": {
"start": 1742895600,
"finish": 1742895600.845505,
"duration": 0.845505952835083,
"processing": 0,
"date_start": "2025-03-25T10:00:00+02:00",
"date_finish": "2025-03-25T10:00:00+02:00",
"operating_reset_at": 1742896200,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
|
|
time |
Information about the request execution time |
Error Handling
HTTP status: 400, 403
{
"error": "ERROR_SENDER_VALIDATION_FAILURE",
"error_description": "Empty sender code!"
}
|
Name |
Description |
|
error |
String error code. It may consist of digits, Latin letters, and underscores |
|
error_description |
Textual description of the error. The description is not intended to be shown to the end user in its raw form |
Possible Error Codes
|
Code |
Description |
Value |
|
|
|
Empty parameter set |
|
|
|
Required parameter |
|
|
|
|
|
|
|
Required parameter |
|
|
|
Required parameter |
|
|
|
Unsupported |
|
|
|
A provider with this |
|
|
|
Error saving the provider |
|
|
|
Method was invoked by a non-administrator |
|
|
|
Method called outside of application context |
Statuses and System Error Codes
HTTP Status: 20x, 40x, 50x
The errors described below may occur when calling any method.
|
Status |
Code |
Description |
|
|
|
An internal server error has occurred. Please contact the server administrator or Bitrix24 technical support |
|
|
|
An internal server error has occurred. Please contact the server administrator or Bitrix24 technical support |
|
|
|
The request intensity limit has been exceeded |
|
|
|
The current method is not permitted for calls using batch |
|
|
|
The maximum length of parameters passed to the batch method has been exceeded |
|
|
|
Invalid access token or webhook code |
|
|
|
The HTTPS protocol is required for method calls |
|
|
|
The REST API is blocked due to overload. This is a manual individual block; please contact Bitrix24 technical support to lift it |
|
|
|
The REST API is only available on commercial plans |
|
|
|
The user associated with the access token or webhook used to call the method lacks the necessary permissions |
|
|
|
The manifest is not available |
|
|
|
The request requires higher privileges than those provided by the webhook token |
|
|
|
The provided access token has expired |
|
|
|
The user does not have access to the application. This means that the application is installed, but the portal administrator has restricted access to this application to specific users only |
|
|
|
The public part of the site is closed. To open the public part of the site on an on-premise installation, disable the "Temporary closure of the public part of the site" option. Path to the setting: Desktop > Settings > Product Settings > Module Settings > Main Module > Temporary closure of the public part of the site |
Continue Learning
- Register an SMS Provider or Message Provider messageservice.sender.add
- Update Message Provider messageservice.sender.update
- Get a List of SMS Providers or Message Providers messageservice.sender.list
- Delete SMS Provider or Message Provider messageservice.sender.delete
- Update Message Delivery Status messageservice.message.status.update