Get a list of e-mails mail.message.list
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: any user
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.list method returns a list of e-mails based on specified conditions.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
mailboxId |
Mailbox identifier. The identifier can be obtained using the mail.mailbox.list |
|
searchQuery |
A string for searching e-mails by content and e-mail metadata |
|
dateFrom |
The start of the e-mail selection period in ISO 8601 format, for example |
|
dateTo |
The end of the e-mail selection period in ISO 8601 format, for example |
|
isSeen |
Filter by e-mail read status. Possible values:
|
|
hasAttachments |
Filter by attachment presence. Possible values:
|
|
folder |
Mail folder name or path |
|
pagination |
Pagination parameters:
|
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.list
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"mailboxId":1,"searchQuery":"contract","hasAttachments":true,"pagination":{"page":1,"limit":20,"offset":0}}' \
https://**put_your_bitrix24_address**/rest/api/**put_your_user_id_here**/**put_your_webhook_here**/mail.message.list
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"mailboxId":1,"searchQuery":"contract","hasAttachments":true,"pagination":{"page":1,"limit":20,"offset":0},"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/api/mail.message.list
// 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, ISODate } from '@bitrix24/b24jssdk'
declare const $b24: B24Frame
// Shape of the payload returned in result (match the "response handling" section of the page)
type MailMessageListResult = {
items: MailMessageItem[]
}
type MailMessageItem = {
id: number
mailboxId: number
mailboxEmail: string
subject: string
from: string
to: string
cc: string
date: ISODate | null
isSeen: boolean
hasAttachments: boolean
url: string
bindings: unknown[]
body: string
}
try {
// mail.message.list returns a single page (default 25, max 200 records). For the whole result set
// use a list helper: $b24.actions.v3.callList.make() returns every record as one
// array, $b24.actions.v3.fetchList.make() yields them in chunks (async generator).
// NOTE: the list helpers do not accept `order` (it is excluded from their params, so
// passing it is a TS error) — keep this call.make + `pagination` variant when sort matters.
const response = await $b24.actions.v3.call.make<MailMessageListResult>({
method: 'mail.message.list',
params: {
mailboxId: 1,
searchQuery: 'contract',
hasAttachments: true,
pagination: {
page: 1,
limit: 20,
offset: 0,
},
},
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('Messages fetched:', result.items.length, result.items[0])
}
} 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 fetchMessageList() {
try {
// Initialize the SDK inside a Bitrix24 frame
const $b24 = await B24Js.initializeB24Frame()
// mail.message.list returns a single page (default 25, max 200 records). For the whole result set
// use a list helper: $b24.actions.v3.callList.make() returns every record as one
// array, $b24.actions.v3.fetchList.make() yields them in chunks (async generator).
// NOTE: the list helpers do not accept `order` (it is excluded from their params, so
// passing it is a TS error) — keep this call.make + `pagination` variant when sort matters.
const response = await $b24.actions.v3.call.make({
method: 'mail.message.list',
params: {
mailboxId: 1,
searchQuery: 'contract',
hasAttachments: true,
pagination: {
page: 1,
limit: 20,
offset: 0,
},
},
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('Messages fetched:', result.items.length, result.items[0])
} catch (error) {
// Thrown on transport or SDK failures (AjaxError, SdkError, etc.)
console.error(error)
}
}
document.addEventListener('DOMContentLoaded', fetchMessageList)
</script>
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.list',
[
'mailboxId' => 1,
'searchQuery' => 'contract',
'hasAttachments' => true,
'pagination' => [
'page' => 1,
'limit' => 20,
'offset' => 0
]
]
);
$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.list',
{
mailboxId: 1,
searchQuery: 'contract',
hasAttachments: true,
pagination: {
page: 1,
limit: 20,
offset: 0
}
},
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.list',
[
'mailboxId' => 1,
'searchQuery' => 'contract',
'hasAttachments' => true,
'pagination' => [
'page' => 1,
'limit' => 20,
'offset' => 0
]
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Response Handling
HTTP status: 200
{
"result": {
"items": [
{
"id": 15,
"mailboxId": 1,
"mailboxEmail": "user@example.com",
"subject": "Contract",
"from": "client@example.com",
"to": "user@example.com",
"cc": "",
"date": "2026-05-25T10:00:00+03:00",
"isSeen": true,
"hasAttachments": true,
"url": "https://example.bitrix24.com/mail/message/15/",
"bindings": [],
"body": "Letter text"
}
]
},
"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 |
Response data object |
|
items |
Array of e-mail objects |
|
items[] |
E-mail object |
|
id |
E-mail identifier |
|
mailboxId |
Mailbox identifier |
|
mailboxEmail |
Mailbox e-mail address |
|
subject |
E-mail subject |
|
from |
E-mail sender |
|
to |
E-mail recipients |
|
cc |
E-mail CC |
|
date |
E-mail date and time |
|
isSeen |
E-mail read status |
|
hasAttachments |
Attachment presence indicator |
|
url |
Link to the e-mail |
|
bindings |
E-mail relations to objects |
|
body |
E-mail body |
|
time |
Request execution time information |
Error Handling
HTTP status: 400
{
"error": {
"code": "BITRIX_REST_V3_EXCEPTION_INVALIDPAGINATIONEXCEPTION",
"message": "Unable to recognize pagination parameter `{\"limit\":\"abc\"}`"
}
}
|
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
Access Errors
Error code: BITRIX_REST_V3_EXCEPTION_ACCESSDENIEDEXCEPTION
|
Field |
Error description |
How to fix |
|
|
Access denied |
Check user permissions and scope |
Pagination Errors
Error code: BITRIX_REST_V3_EXCEPTION_INVALIDPAGINATIONEXCEPTION
|
Field |
Error description |
How to fix |
|
|
Unable to recognize pagination parameter |
Provide numeric values. |
Request Validation Errors
Error code: BITRIX_REST_V3_EXCEPTION_VALIDATION_REQUESTVALIDATIONEXCEPTION
|
Field |
Error description |
How to fix |
|
|
Parameter |
Provide the date in ISO 8601 format |
|
|
Parameter |
Provide the date in ISO 8601 format |
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 |