For AI agents: markdown of this page — /docs-content-en/entities/tasks/pin.md documentation index — /llms.txt
Pin a task
POST /v1/tasks/:taskId/pin
Pins a task to the top of the personal task list of the user the key acts on behalf of. The action is available to a participant with view access to the task — edit rights on the task are not required, unlike PATCH /v1/tasks/:id.
Parameters
| Parameter | In | Type | Req. | Description |
|---|---|---|---|---|
taskId |
path | integer | yes | Task ID. List: GET /v1/tasks |
The request body is empty.
Examples
curl — personal key
curl -X POST -H "X-Api-Key: YOUR_API_KEY" \
https://vibecode.bitrix24.com/v1/tasks/289/pin
curl — OAuth application
curl -X POST -H "X-Api-Key: YOUR_APP_KEY" \
-H "Authorization: Bearer USER_SESSION_TOKEN" \
https://vibecode.bitrix24.com/v1/tasks/289/pin
JavaScript — personal key
const res = await fetch(
`https://vibecode.bitrix24.com/v1/tasks/${taskId}/pin`,
{ method: 'POST', headers: { 'X-Api-Key': 'YOUR_API_KEY' } }
)
const body = await res.json()
console.log(body.data.pinned) // true
JavaScript — OAuth application
const res = await fetch(
`https://vibecode.bitrix24.com/v1/tasks/${taskId}/pin`,
{
method: 'POST',
headers: {
'X-Api-Key': 'YOUR_APP_KEY',
'Authorization': 'Bearer USER_SESSION_TOKEN',
},
}
)
Response fields
| Field | Type | Description |
|---|---|---|
success |
boolean | true on successful pin |
data.taskId |
integer | Task ID |
data.pinned |
boolean | true — the task is pinned |
Response example
{
"success": true,
"data": {
"taskId": 289,
"pinned": true
}
}
Error response example
404 — task not found or not accessible:
{
"success": false,
"error": {
"code": "TASK_NOT_FOUND",
"message": "Task 99999999 not found or not accessible."
}
}
Errors
| HTTP | Code | Description |
|---|---|---|
| 400 | INVALID_PARAMS |
taskId in the path is not a positive integer |
| 401 | MISSING_API_KEY |
The X-Api-Key header was not provided |
| 401 | INVALID_API_KEY |
Invalid or expired key |
| 401 | TOKEN_MISSING |
The key has no linked authorization tokens |
| 403 | SCOPE_DENIED |
The key is missing the task scope |
| 403 | WRITE_BLOCKED_READONLY_KEY |
The key is read-only — the action changes data and is blocked |
| 404 | TASK_NOT_FOUND |
No task with the given taskId exists or it is not accessible to the user |
Full list of common API errors — Errors.
Known specifics
- The response is a short confirmation, not a task card. Read the full task fields via
GET /v1/tasks/:id.