Send an e-mail mail.message.send
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:
Who can execute the method: a user who has access to the mailbox
The mail.message.send method sends a new e-mail on behalf of an available sender.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
from* |
Sender's e-mail. Available addresses can be obtained using the mail.mailbox.senders method. |
|
to* |
Array of recipient e-mail addresses |
|
subject* |
E-mail subject |
|
body* |
E-mail body: plain text or basic HTML |
|
cc |
Array of CC recipient e-mail addresses |
|
bcc |
Array of BCC recipient e-mail addresses |
Code Examples
How to Use Examples in Documentation
The new API call differs by adding the /api/ parameter to the request:
https://{installation_address}/rest/api/{user_id}/{webhook_token}/mail.message.send
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"from":"user@example.com","to":["client@example.com"],"subject":"Business Proposal","body":"Hello. I am sending the materials."}' \
https://**put_your_bitrix24_address**/rest/api/**put_your_user_id_here**/**put_your_webhook_here**/mail.message.send
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"from":"user@example.com","to":["client@example.com"],"subject":"Business Proposal","body":"Hello. I am sending the materials.","auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/api/mail.message.send
SDKs do not yet support the /rest/api/ address in calls. Use direct HTTP requests, for example, via curl, fetch.
try
{
const response = await $b24.callMethod(
'mail.message.send',
{
from: 'user@example.com',
to: ['client@example.com'],
subject: 'Business Proposal',
body: 'Hello. I am sending the materials.'
}
);
const result = response.getData().result;
console.log('Success:', result);
}
catch( error )
{
console.error('Error:', error);
}
SDKs do not yet support the /rest/api/ address in calls. Use direct HTTP requests, for example, via curl, fetch.
try {
$response = $b24Service
->core
->call(
'mail.message.send',
[
'from' => 'user@example.com',
'to' => ['client@example.com'],
'subject' => 'Business Proposal',
'body' => 'Hello. I am sending the materials.'
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Success: ' . print_r($result, true);
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error: ' . $e->getMessage();
}
SDKs do not yet support the /rest/api/ address in calls. Use direct HTTP requests, for example, via curl, fetch.
BX24.callMethod(
'mail.message.send',
{
from: 'user@example.com',
to: ['client@example.com'],
subject: 'Business Proposal',
body: 'Hello. I am sending the materials.'
},
function(result){
console.info(result.data());
console.log(result);
}
);
SDKs do not yet support the /rest/api/ address in calls. Use direct HTTP requests, for example, via curl, fetch.
require_once('crest.php');
$result = CRest::call(
'mail.message.send',
[
'from' => 'user@example.com',
'to' => ['client@example.com'],
'subject' => 'Business Proposal',
'body' => 'Hello. I am sending the materials.'
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Response Handling
HTTP status: 200
{
"result": {
"success": true,
"to": [
"client@example.com"
]
},
"time": {
"start": 1779819678,
"finish": 1779819678.84803,
"duration": 0.8480300903320312,
"processing": 0,
"date_start": "2026-05-26T21:21:18+03:00",
"date_finish": "2026-05-26T21:21:18+03:00",
"operating_reset_at": 1779820278,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
Object with the sending result |
|
success |
Success flag |
|
to |
Recipients to whom the e-mail was sent |
|
time |
Request execution time information |
Error Handling
HTTP status: 400
{
"error": {
"code": "BITRIX_REST_V3_EXCEPTION_VALIDATION_REQUESTVALIDATIONEXCEPTION",
"message": "Error validating request object",
"validation": [
{
"message": "Mandatory field is missing",
"field": "from"
}
]
}
}
|
Name |
Description |
|
error.code |
String error code. Use it to identify the type of exception |
|
error.message |
Text description of the error |
|
error.validation |
Array with error details. Present only in data validation errors |
|
error.validation[].field |
Name of the field where the validation error occurred |
|
error.validation[].message |
Description of the error related to the specified field |
Possible Error Codes
Request Validation Errors
Error code: BITRIX_REST_V3_EXCEPTION_VALIDATION_REQUESTVALIDATIONEXCEPTION
|
Field |
Error description |
How to fix |
|
|
Required field is not specified |
Pass |
|
|
Required field |
Pass |
|
|
Required field |
Pass |
|
|
Required field |
Pass |
|
|
MESSAGE_SEND_FAILED |
Check the sender availability and the correctness of the request parameters |
|
|
NO_RECIPIENTS |
Check that the |
|
|
RESOLVE_RECIPIENTS_ERROR |
Check the value format and recipient availability in |
Access Errors
Error code: BITRIX_REST_V3_EXCEPTION_ACCESSDENIEDEXCEPTION
|
Field |
Error description |
How to fix |
|
|
Access denied |
Check user permissions and |
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
- Reply to e-mail mail.message.reply
- Forward e-mail mail.message.forward
- Get senders mail.mailbox.senders