For AI agents: markdown of this page — /docs-content-en/entities/tasks/dependencies-list.md documentation index — /llms.txt

Dependencies of one task

GET /v1/tasks/:taskId/dependencies

Returns the task's predecessors — the tasks it depends on.

The generic filter parameter is not applied by this endpoint. By default, the API preserves the previous HTTP 200 response and data, adds Warning: 299 - "filter is not supported on this endpoint and was ignored", and records unsupported-filter use in the server log.

Parameters

Parameter Type Required Description
ParametertaskId (path) Typenumber Requiredyes DescriptionTask ID, a positive integer. List: GET /v1/tasks

Examples

curl — personal key

Terminal 
curl "https://vibecode.bitrix24.com/v1/tasks/4203/dependencies" \
  -H "X-Api-Key: YOUR_API_KEY"

curl — OAuth application

Terminal 
curl "https://vibecode.bitrix24.com/v1/tasks/4203/dependencies" \
  -H "X-Api-Key: YOUR_APP_KEY" \
  -H "Authorization: Bearer USER_SESSION_TOKEN"

JavaScript — personal key

javascript 
const res = await fetch('https://vibecode.bitrix24.com/v1/tasks/4203/dependencies', {
  headers: {
    'X-Api-Key': 'YOUR_API_KEY',
  },
})

const { success, data } = await res.json()
console.log('Predecessors:', data.map((dep) => `${dep.id}: ${dep.title ?? 'untitled'}`))

JavaScript — OAuth application

javascript 
const res = await fetch('https://vibecode.bitrix24.com/v1/tasks/4203/dependencies', {
  headers: {
    'X-Api-Key': 'YOUR_APP_KEY',
    'Authorization': 'Bearer USER_SESSION_TOKEN',
  },
})

const { success, data } = await res.json()

Response fields

Field Type Description
Fieldsuccess Typeboolean Descriptiontrue on success
Fielddata Typearray DescriptionPredecessors, in ascending id order. An empty array for a task without dependencies
Fielddata[].id Typenumber DescriptionID of the predecessor task. Get: GET /v1/tasks/:id
Fielddata[].title Typestring | null DescriptionTitle of the predecessor task. null if Bitrix24 did not return it
Fieldmeta.total Typenumber DescriptionNumber of predecessors, always equal to the length of data
Fieldmeta.hasMore Typeboolean DescriptionAlways false: the response is not truncated
Fieldmeta.direction Typestring DescriptionAlways predecessors — the method returns predecessors
Fieldmeta.source Typestring DescriptionAlways RELATED_TASKS — the source of dependencies in Bitrix24

Response example

JSON 
{
  "success": true,
  "data": [
    {
      "id": 4199,
      "title": "Prepare the estimate"
    },
    {
      "id": 4201,
      "title": "Approve the budget"
    }
  ],
  "meta": {
    "total": 2,
    "hasMore": false,
    "direction": "predecessors",
    "source": "RELATED_TASKS"
  }
}

Error response example

404 — the task does not exist or is not visible to the key:

JSON 
{
  "success": false,
  "error": {
    "code": "TASK_NOT_FOUND",
    "message": "Task not found."
  }
}

Errors

HTTP Code Description
HTTP200 CodeWarning: 299 DescriptionThe filter is ignored by default; previous data is preserved and the warning is sent in the Warning header.
HTTP400 (strict mode only) CodeUNSUPPORTED_FILTER DescriptionThe server mode is disabled by default; until it is enabled, the endpoint preserves HTTP 200 and the previous data.
HTTP404 CodeTASK_NOT_FOUND DescriptionThe task does not exist or is not visible to the key — both cases return the same response. Message Task not found.
HTTP422 CodeDEPENDENCY_LIMIT_EXCEEDED DescriptionThe task has more than 1000 dependencies. The response is not truncated: you receive either the full list or this error
HTTP400 CodeINVALID_PARAMS DescriptiontaskId is not a positive integer
HTTP401 CodeMISSING_API_KEY DescriptionX-Api-Key was not passed
HTTP401 CodeTOKEN_MISSING DescriptionThe key has no Bitrix24 tokens
HTTP403 CodeSCOPE_DENIED DescriptionThe key has no task scope
HTTP429 CodeRATE_LIMITED DescriptionRequest rate exceeded. The effective cap is in the x-ratelimit-limit header

Full list of common API errors — Errors.

Known specifics

Typed dependencies are not visible. The method returns the set of predecessors from the task's DEPENDS_ON field. Bitrix24 stores typed dependencies such as "finish-to-start" separately from this set, and they do not appear in the response. So an empty data does not prove that the task has no dependencies at all.

See also