Reply to e-mail mail.message.reply
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 with access to the mailbox where the e-mail is located
This method belongs to REST 3.0. The call specifics and response format of the new API version are described in the REST 3.0 overview.
The mail.message.reply method sends a reply to an e-mail.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
replyToMessageId* |
The e-mail identifier that needs to be replied to. The identifier can be obtained using the mail.message.list method. |
|
from* |
Sender's e-mail. Available addresses can be obtained using the mail.mailbox.senders method. |
|
to* |
An array of recipient e-mail addresses |
|
subject* |
E-mail subject |
|
body* |
E-mail text: plain text or basic HTML |
|
cc |
An array of CC recipient e-mail addresses |
|
bcc |
An array of BCC recipient e-mail addresses |
Code Examples
How to Use Examples in Documentation
The new API call differs by adding the /api/ segment to the request URL:
https://{installation_address}/rest/api/{user_id}/{webhook_token}/mail.message.reply
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"replyToMessageId":15,"from":"user@example.com","to":["client@example.com"],"subject":"Re: Agreement","body":"Thank you, received."}' \
https://**put_your_bitrix24_address**/rest/api/**put_your_user_id_here**/**put_your_webhook_here**/mail.message.reply
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"replyToMessageId":15,"from":"user@example.com","to":["client@example.com"],"subject":"Re: Agreement","body":"Thank you, received.","auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/api/mail.message.reply
// This snippet is an ES module: top-level await requires type="module" or a bundler.
// $b24 is an already-initialized SDK instance (see the SDK "Get started" guide).
import { Text } from '@bitrix24/b24jssdk'
import type { B24Frame } from '@bitrix24/b24jssdk'
declare const $b24: B24Frame
// Shape of the payload returned in result (match the "response handling" section of the page)
type ReplyResult = {
success: boolean
to: string[]
}
try {
const response = await $b24.actions.v3.call.make<ReplyResult>({
method: 'mail.message.reply',
params: {
replyToMessageId: 15,
from: 'user@example.com',
to: ['client@example.com'],
subject: 'Re: Contract',
body: 'Thank you, received.',
},
requestId: Text.getUuidRfc4122()
})
// The payload is available only on a successful response
if (!response.isSuccess) {
console.error(response.getErrorMessages().join('; '))
} else {
const result = response.getData()!.result
console.info('Reply sent:', result.success, 'Recipients:', result.to)
}
} catch (error) {
// Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
console.error(error)
}
<!-- Load the SDK (UMD build); it is exposed as the global B24Js -->
<script src="https://unpkg.com/@bitrix24/b24jssdk@1/dist/umd/index.min.js"></script>
<script>
async function sendReply() {
try {
// Initialize the SDK inside a Bitrix24 frame
const $b24 = await B24Js.initializeB24Frame()
const response = await $b24.actions.v3.call.make({
method: 'mail.message.reply',
params: {
replyToMessageId: 15,
from: 'user@example.com',
to: ['client@example.com'],
subject: 'Re: Contract',
body: 'Thank you, received.',
},
requestId: B24Js.Text.getUuidRfc4122()
})
// The payload is available only on a successful response
if (!response.isSuccess) {
console.error(response.getErrorMessages().join('; '))
return
}
const result = response.getData().result
console.info('Reply sent:', result.success, 'Recipients:', result.to)
} catch (error) {
// Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
console.error(error)
}
}
document.addEventListener('DOMContentLoaded', sendReply)
</script>
from b24pysdk.errors import BitrixAPIError, BitrixSDKException
to = [
"client@example.com",
]
try:
bitrix_response = client.mail.message.reply(
reply_to_message_id=15,
from_='user@example.com',
to=to,
subject='Re: Contract',
body='Thank you, received.',
).response
result = bitrix_response.result
print(result)
except BitrixAPIError as error:
print(
"Bitrix API error",
f"error: {error.error}",
f"error_description: {error.error_description}",
sep="\n",
)
except BitrixSDKException as error:
print(f"Bitrix SDK error: {error.message}")
except Exception as error:
print(f"Unexpected error: {error}")
SDKs do not yet support the /rest/api/ address in calls. Use direct HTTP requests, for example, via curl or fetch.
try {
$response = $b24Service
->core
->call(
'mail.message.reply',
[
'replyToMessageId' => 15,
'from' => 'user@example.com',
'to' => ['client@example.com'],
'subject' => 'Re: Agreement',
'body' => 'Thank you, received.'
]
);
$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 or fetch.
BX24.callMethod(
'mail.message.reply',
{
replyToMessageId: 15,
from: 'user@example.com',
to: ['client@example.com'],
subject: 'Re: Agreement',
body: 'Thank you, received.'
},
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 or fetch.
require_once('crest.php');
$result = CRest::call(
'mail.message.reply',
[
'replyToMessageId' => 15,
'from' => 'user@example.com',
'to' => ['client@example.com'],
'subject' => 'Re: Agreement',
'body' => 'Thank you, received.'
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
// client and ctx are already created — see the Go SDK section
res, err := client.Core().Call(ctx, "mail.message.reply", b24.Params{
"replyToMessageId": 15,
"from": "user@example.com",
"to": []string{"client@example.com"},
"subject": "Re: Agreement",
"body": "Thank you, received.",
})
if err != nil {
return fmt.Errorf("mail.message.reply: %w", err)
}
var item struct {
Success bool `json:"success"`
}
if err := json.Unmarshal(res.Result, &item); err != nil {
return fmt.Errorf("parse response: %w", err)
}
fmt.Println(item.Success)
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 during request object validation",
"validation": [
{
"message": "Mandatory field is missing",
"field": "replyToMessageId"
}
]
}
}
|
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 |
|
|
Mandatory field is not specified |
Pass |
|
|
Mandatory field |
Pass |
|
|
Mandatory field |
Pass |
|
|
Mandatory field |
Pass |
|
|
Mandatory field |
Pass |
|
|
MESSAGE_REPLY_FAILED |
Check the existence of the e-mail, access to it, and the correctness of the e-mail data |
|
|
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: 4xx, 5xx
The errors described below are returned by the REST API itself, not by the logic of a specific method. They can arrive in response to any method.
|
Status |
Code |
Description |
|
|
|
An internal server error has occurred. Retry the call, and if the error persists, contact the server administrator or Bitrix24 technical support |
|
|
|
The server returned an unexpected response. Retry the call, and if the error persists, contact the server administrator or Bitrix24 technical support |
|
|
|
The request intensity limit has been exceeded |
|
|
|
The method is blocked because the request resource intensity limit has been exceeded. The block is lifted automatically once the accumulated execution time of the method no longer exceeds the limit |
|
|
|
The request contains no authorization data: neither an access token nor a webhook code was passed |
|
|
|
Methods are called over the HTTPS protocol only |
|
|
|
The REST API is blocked due to overload. This is a manual individual block. To have it lifted, contact Bitrix24 technical support |
|
|
|
The REST API is available only on commercial plans. A webhook receives a different error message — |
|
|
|
No active webhook with the specified user identifier and secret code was found |
|
|
|
No method with this name was found. The name is misspelled, the method does not exist in the REST API, or it is unavailable without the required scope |
|
|
|
The request requires broader permissions than the token has: for a webhook these are the permissions granted to it, for an application it is the scope. For an application, the error message ends with |
|
|
|
The access token has expired |
|
|
|
The application is installed, but the Bitrix24 administrator has granted access to it only to specific users |
|
|
|
The public part of the site is closed. To open it 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 |