Delegate a workflow task bizproc.task.delegate
Choose a tool for developing with an AI agent:
- use Alaio Vibecode to build an app for Bitrix24 from a task description without knowing any programming language. The agent writes the code and deploys the app to a server, with no manual hosting setup
- use the MCP server to develop a REST API integration in your own project. The agent refers to the official REST documentation
Scope:
bizprocWho can execute the method: any user responsible for the workflow task
This method delegates a workflow task. You can only delegate your own task.
User documentation
Method parameters
Required parameters are marked with *
|
Name |
Description |
|
TASK_IDS* |
List of task identifiers. You can obtain identifiers using the bizproc.task.list method. |
|
FROM_USER_ID* |
Identifier of the user from whom the tasks will be delegated. You can obtain the user identifier using the user.get method. |
|
TO_USER_ID* |
Identifier of the user to whom the tasks will be delegated. You can obtain the user identifier using the user.get method. Who you can delegate to depends on the task settings: only subordinates, all employees, or no one. |
Code examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"TASK_IDS":[1128,1129,1130],"FROM_USER_ID":15,"TO_USER_ID":37}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/bizproc.task.delegate
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"TASK_IDS":[1128,1129,1130],"FROM_USER_ID":15,"TO_USER_ID":37,"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/bizproc.task.delegate
try
{
const response = await $b24.callMethod(
'bizproc.task.delegate',
{
TASK_IDS: [1128, 1129, 1130],
FROM_USER_ID: 15,
TO_USER_ID: 37,
}
);
const result = response.getData().result;
console.log('Delegated tasks:', result);
}
catch( error )
{
console.error('Error:', error);
}
from b24pysdk.errors import BitrixAPIError, BitrixSDKException
try:
bitrix_response = client.bizproc.task.delegate(
task_ids=[
1128,
1129,
1130,
],
from_user_id=15,
to_user_id=37,
).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}")
try {
$response = $b24Service
->core
->call(
'bizproc.task.delegate',
[
'TASK_IDS' => [1128, 1129, 1130],
'FROM_USER_ID' => 15,
'TO_USER_ID' => 37,
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Success: ' . print_r($result, true);
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error delegating task: ' . $e->getMessage();
}
BX24.callMethod(
'bizproc.task.delegate',
{
'TASK_IDS': [1128, 1129, 1130],
'FROM_USER_ID': 15,
'TO_USER_ID': 37,
},
function(result)
{
if(result.error())
alert("Error: " + result.error());
else
console.log(result.data());
}
);
require_once('crest.php');
$result = CRest::call(
'bizproc.task.delegate',
[
'TASK_IDS' => [1128, 1129, 1130],
'FROM_USER_ID' => 15,
'TO_USER_ID' => 37
]
);
echo '<PRE>';
print_r($result);
echo '</PRE>';
// client and ctx are already created — see the Go SDK section
res, err := client.Core().Call(ctx, "bizproc.task.delegate", b24.Params{
"TASK_IDS": []int{1128, 1129, 1130},
"FROM_USER_ID": 15,
"TO_USER_ID": 37,
})
if err != nil {
return fmt.Errorf("bizproc.task.delegate: %w", err)
}
var ok bool
if err := json.Unmarshal(res.Result, &ok); err != nil {
return fmt.Errorf("parse response: %w", err)
}
fmt.Println("done:", ok)
Response handling
HTTP status: 200
{
"result": true,
"time": {
"start": 1748526089.625516,
"finish": 1748526089.656787,
"duration": 0.03127098083496094,
"processing": 0.008746147155761719,
"date_start": "2025-05-29T16:41:29+02:00",
"date_finish": "2025-05-29T16:41:29+02:00",
"operating_reset_at": 1748526689,
"operating": 0
}
}
Returned data
|
Name |
Description |
|
result |
Returns |
|
time |
Information about the request execution time. |
Error handling
HTTP status: 400
{
"error": "ERROR_INVALID_USER_ID",
"error_description": "Invalid FROM_USER_ID"
}
|
Name |
Description |
|
error |
String error code. It consists of digits, Latin letters, and underscores. It may arrive empty — in that case only |
|
error_description |
Error message for the developer. Do not show it to the end user without processing |
Possible error codes
|
Code |
Error message |
Description |
|
|
Invalid TASK_IDS |
Invalid task identifiers or the |
|
|
Invalid FROM_USER_ID |
Invalid or missing user identifier from whom the delegation is made. |
|
|
Invalid TO_USER_ID |
Invalid or missing user identifier to whom the delegation is made. |
|
|
User is not responsible for the task |
The user specified in the |
|
|
Task delegation is only available for intranet users |
The user specified in the |
|
|
List of errors separated by |
The method can accept multiple tasks. If errors occur in multiple tasks, they will be returned as a list separated by |
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 |
|
|
|
REST API access is not active for this account. In Bitrix24 Cloud, check the current plan or trial status: Vibe+ plans include REST API access, while Essentials plans do not. 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 |