Create a link between tasks task.dependence.add
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:
taskWho can execute the method: any user
This method creates a dependency of one task on another.
Method Parameters
Required parameters are marked with *
|
Name |
Description |
|
taskIdFrom* |
The identifier of the task from which the dependency is created |
|
taskIdTo* |
The identifier of the task for which the dependency is created |
|
linkType* |
Type of dependency:
|
The task identifier can be obtained when creating a new task or by using the getting the list of tasks method.
Code Examples
How to Use Examples in Documentation
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"taskIdFrom":100,"taskIdTo":101,"linkType":0}' \
https://**put_your_bitrix24_address**/rest/**put_your_user_id_here**/**put_your_webhook_here**/task.dependence.add
curl -X POST \
-H "Content-Type: application/json" \
-H "Accept: application/json" \
-d '{"taskIdFrom":100,"taskIdTo":101,"linkType":0,"auth":"**put_access_token_here**"}' \
https://**put_your_bitrix24_address**/rest/task.dependence.add
try
{
const response = await $b24.callMethod(
'task.dependence.add', {
"taskIdFrom": 100,
"taskIdTo": 101,
"linkType": 0
}
);
const result = response.getData().result;
console.info(result);
}
catch( error )
{
console.error(error);
}
try {
$response = $b24Service
->core
->call(
'task.dependence.add',
[
'taskIdFrom' => 100,
'taskIdTo' => 101,
'linkType' => 0,
]
);
$result = $response
->getResponseData()
->getResult();
echo 'Success: ' . print_r($result, true);
// Your logic for processing data
processData($result);
} catch (Throwable $e) {
error_log($e->getMessage());
echo 'Error adding task dependence: ' . $e->getMessage();
}
BX24.callMethod(
'task.dependence.add', {
"taskIdFrom":100,
"taskIdTo":101,
"linkType":0
},
function(result) {
if (result.error()) {
console.error(result.error());
} else {
console.info(result.data());
}
}
);
require_once('crest.php');
$result = CRest::call('task.dependence.add', [
'taskIdFrom' => 100,
'taskIdTo' => 101,
'linkType' => 0,
]);
echo '<PRE>';
print_r($result);
echo '</PRE>';
Response Handling
HTTP status: 200
Example of a successfully executed request
{
"result": {
[]
},
"time": {
"start": 1712137817.343984,
"finish": 1712137817.605804,
"duration": 0.26182007789611816,
"processing": 0.018325090408325195,
"date_start": "2024-04-03T12:50:17+02:00",
"date_finish": "2024-04-03T12:50:17+02:00"
}
}
Returned Data
|
Name |
Description |
|
result |
In case of success, contains an empty array |
|
time |
Information about the execution time of the request |
Error Handling
HTTP status: 400
{
"error": "ILLEGAL_NEW_LINK",
"error_description": "A link between tasks already exists"
}
|
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 |
|
|
A link between tasks already exists |
|
|
Unable to add a link between tasks |
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 |