Get Mail Service Fields mailservice.fields
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:
mailserviceWho can execute the method: any user
The method mailservice.fields returns localized names of the mail service fields.
Method Parameters
No parameters.
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/mailservice.fields
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"auth": "**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/mailservice.fields
try
{
const response = await $b24.callMethod('mailservice.fields', {});
console.log(response.getData().result);
}
catch (error)
{
console.error(error);
}
try {
$response = $b24Service
->core
->call('mailservice.fields', []);
$result = $response->getResponseData()->getResult();
print_r($result);
} catch (Throwable $e) {
echo $e->getMessage();
}
BX24.callMethod(
'mailservice.fields',
{},
function(result)
{
if (result.error())
{
console.error(result.error());
}
else
{
console.log(result.data());
}
}
);
require_once('crest.php');
$result = CRest::call('mailservice.fields', []);
print_r($result);
Response Handling
HTTP status: 200
{
"result": {
"ID": "ID",
"SITE_ID": "Site",
"ACTIVE": "Activity",
"NAME": "Name",
"SERVER": "Server Address",
"PORT": "Port",
"ENCRYPTION": "Secure Connection",
"LINK": "Web Interface Address",
"ICON": "Logo",
"SORT": "Sorting"
},
"time": {
"start": 1710000500.123,
"finish": 1710000500.200,
"duration": 0.077,
"processing": 0.020,
"date_start": "2024-03-09T10:08:20+02:00",
"date_finish": "2024-03-09T10:08:20+02:00",
"operating_reset_at": 1710003600,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
Object with field names. The structure of the object is described in detail below |
|
time |
Information about the request execution time |
Result Object
|
Name |
Description |
|
ID |
Name of the identifier field |
|
SITE_ID |
Name of the site field |
|
ACTIVE |
Name of the activity field |
|
NAME |
Name of the service field |
|
SERVER |
Name of the server address field |
|
PORT |
Name of the port field |
|
ENCRYPTION |
Name of the secure connection field |
|
LINK |
Name of the web interface address field |
|
ICON |
Name of the logo field |
|
SORT |
Name of the sorting field |
Error Handling
|
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 |
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
- Create Mail Service mailservice.add
- Update Mail Service mailservice.update
- Get the mailservice.get method
- Get the list of mail services mailservice.list
- Delete Mail Service mailservice.delete