Set Access Codes for Role landing.role.setAccessCodes
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:
landingWho can execute the method: administrator or user with "full access" permission to the "Sites and Stores" section.
The method landing.role.setAccessCodes specifies to whom the role is assigned: users, groups, or departments. After invocation, the method reapplies the already saved permissions of this role for the sites.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
id* |
Role identifier. You can obtain the identifier using the method landing.role.getList |
|
codes |
The final list of access codes for the role. The method completely replaces the previously saved list and does not merge it with the current one. Access code options:
More details about access codes and their usage rules can be found in the description of the method landing.site.setRights. The method does not check each access code individually. If there is an unsupported or non-existent code in the list, there will be no separate error. If the After changing the access codes, the system recalculates not only the permissions for the sites but also the additional permissions of the role: the ability to create sites, view the "Sites and Stores" section in the menu, and administer the section. You cannot retrieve the saved list of access codes via REST. The method landing.role.getList returns only the identifier, name, and If the |
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-d '{
"id": 11,
"codes": [
"U45",
"DR7",
"SG3_A"
]
}' \
"https://**put.your-domain-here**/rest/**user_id**/**webhook_code**/landing.role.setAccessCodes.json"
curl -X POST \
-H "Content-Type: application/json" \
-d '{
"id": 11,
"codes": [
"U45",
"DR7",
"SG3_A"
],
"auth": "**put_access_token_here**"
}' \
"https://**put.your-domain-here**/rest/landing.role.setAccessCodes.json"
try
{
const response = await $b24.callMethod(
'landing.role.setAccessCodes',
{
id: 11,
codes: [
'U45',
'DR7',
'SG3_A'
]
}
);
const result = response.getData().result;
console.info(result);
}
catch (error)
{
console.error(error);
}
try {
$response = $b24Service
->core
->call(
'landing.role.setAccessCodes',
[
'id' => 11,
'codes' => [
'U45',
'DR7',
'SG3_A',
],
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Success: ' . print_r($result, true);
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error setting role access codes: ' . $e->getMessage();
}
BX24.callMethod(
'landing.role.setAccessCodes',
{
id: 11,
codes: [
'U45',
'DR7',
'SG3_A'
]
},
function(result)
{
if (result.error())
{
console.error(result.error());
}
else
{
console.info(result.data());
}
}
);
require_once('crest.php');
$result = CRest::call(
'landing.role.setAccessCodes',
[
'id' => 11,
'codes' => [
'U45',
'DR7',
'SG3_A',
],
]
);
if (isset($result['error']))
{
echo 'Error: ' . $result['error_description'];
}
else
{
echo '<pre>';
print_r($result['result']);
echo '</pre>';
}
Response Handling
HTTP status: 200
{
"result": true,
"time": {
"start": 1775067129,
"finish": 1775067129.196438,
"duration": 0.19643807411193848,
"processing": 0,
"date_start": "2026-04-01T21:12:09+02:00",
"date_finish": "2026-04-01T21:12:09+02:00",
"operating_reset_at": 1775067729,
"operating": 0
}
}
Returned Data
|
Name |
Description |
|
result |
Call result The method returns The value After invocation, check the result in the interface. You can additionally verify which permissions of the role are applied to the sites via the method landing.role.getRights, but this method does not return the final list of access codes. |
|
time |
Information about the request execution time |
Error Handling
HTTP status: 400
{
"error": "MISSING_PARAMS",
"error_description": "Not enough call parameters, missing: id"
}
|
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 |
|
|
Insufficient permissions to work with the "Sites and Stores" section. |
|
|
The method requires administrator rights or "full access" permission to the "Sites and Stores" section. |
|
|
Managing permissions in the "Sites and Stores" section is not available on the current plan. |
|
|
The required parameter |
|
|
The |
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
- Get the List of Roles landing.role.getList
- Get Role Rights with landing.role.getRights
- Set Role Permissions for the Site List landing.role.setRights