# Read the kanban sorting permission

`GET /v1/tasks/stages/:entityId/can-move`

Reports whether the key's user can move tasks between the stages of a workgroup kanban. Use it to decide whether to enable card drag-and-drop before calling the move method.

## Parameters

| Parameter | Type | Required | Description |
|----------|-----|:-----:|----------|
| `entityId` (path) | number | yes | Workgroup ID, or `0` for the key owner's "My Plan". Group list: [`GET /v1/workgroups`](/docs/entities/workgroups/list) |

The method takes no query parameters: any of them is rejected with `400 INVALID_PARAMS`.

## Examples

### curl — personal key

```bash
curl "https://vibecode.bitrix24.com/v1/tasks/stages/155/can-move" \
  -H "X-Api-Key: YOUR_API_KEY"
```

### curl — OAuth application

```bash
curl "https://vibecode.bitrix24.com/v1/tasks/stages/155/can-move" \
  -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/stages/155/can-move', {
  headers: { 'X-Api-Key': 'YOUR_API_KEY' },
})

const { success, data } = await res.json()
console.log(data.canMove)
```

### JavaScript — OAuth application

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

const { success, data } = await res.json()
console.log(data.canMove)
```

## Response fields

| Field | Type | Description |
|------|-----|----------|
| `success` | boolean | Always `true` on success |
| `data` | object | Check result |
| `data.canMove` | boolean | `true` — the key's user can move tasks in the kanban, `false` — cannot |

## Response example

```json
{
  "success": true,
  "data": {
    "canMove": true
  }
}
```

## Error response example

400 — `entityId` is not a non-negative integer, or a query parameter was passed:

```json
{
  "success": false,
  "error": {
    "code": "INVALID_PARAMS",
    "message": "entityId must be non-negative; query parameters are not supported"
  }
}
```

## Errors

| HTTP | Code | Description |
|------|-----|----------|
| 400 | `INVALID_PARAMS` | `entityId` is not a non-negative integer, or a query parameter was passed |
| 401 | `MISSING_API_KEY` | The `X-Api-Key` header is missing |
| 401 | `TOKEN_MISSING` | The key has no valid Bitrix24 token |
| 403 | `SCOPE_DENIED` | The key has neither the `task` nor the `tasks` scope |
| 422 | `BITRIX_ERROR` | Bitrix24 rejected the request, details in `message` |
| 502 | `BITRIX_ERROR` | Bitrix24 returned a response with an unexpected structure: `Invalid can-move response` |

Full list of common API errors — [Errors](/docs/errors).

## Known specifics

- **Permission for the whole board, not for a task.** The response says whether tasks can be moved in the group kanban at all. It does not check permissions on a specific task: moving someone else's task can still be refused.
- **For "My Plan" the response is always `true`.** With `entityId: 0` the method does not call Bitrix24.
- **A nonexistent group does not cause an error.** For a group that does not exist on the Bitrix24 account, the response is `200` with `canMove: false`.
- **A read-only key works.** The method changes nothing.

## See also

- [Tasks: kanban, "My Plan" and day plan](/docs/tasks)
- [Move a task with ordering](/docs/tasks/move-stage)
- [Task kanban stages](/docs/task-stages)
- [Workgroups](/docs/entities/workgroups)