# List tasks

`GET /v1/bizproc-tasks`

One Bitrix24 page of tasks. Ordinary users default to their own tasks. An administrator without a filter may see every user's tasks: supply `filter={"userId":1373}` to select your own. Bitrix24 checks manager and administrator rights.

Bitrix24 API: `bizproc.task.list`
Scope: `bizproc`

## Parameters

| Field | Type | Required | Description |
|---|---|---|---|
| `select` | string | No | Comma-separated camelCase or native names; defaults to ID, WORKFLOW_ID, DOCUMENT_NAME, NAME |
| `filter` | string | No | JSON object. Prefixes =, !, !=, <, <=, >, >=; scalar or non-empty scalar array values |
| `order` | string | No | JSON object: field names mapped to ASC or DESC; default ID DESC |
| `start` | integer | No | Nonnegative B24 offset, default 0; use meta.next |

## Response fields

| Field | Type | Description |
|---|---|---|
| `success` | boolean | true |
| `data` | object[] | Task rows; camelCase names, values retain Bitrix24 types |
| `meta.start` | integer | Requested B24 offset |
| `meta.total` | integer | Upstream total, omitted if unavailable |
| `meta.next` | integer | Upstream next offset, omitted at the end |

Available fields: `id`, `activity`, `activityName`, `workflowId`, `documentName`, `description`, `name`, `modified`, `workflowStarted`, `workflowStartedBy`, `overdueDate`, `workflowTemplateId`, `workflowTemplateName`, `workflowState`, `status`, `userId`, `userStatus`, `moduleId`, `entity`, `documentId`, `parameters`, `documentUrl`. `parameters` describes the task form. Field-code values are preserved. Secret-bearing URLs are replaced with `[REDACTED]`.

## Examples

### cURL API key

```bash
curl -X GET "https://vibecode.bitrix24.com/v1/bizproc-tasks" \
  -H "X-Api-Key: YOUR_API_KEY"
```

### cURL OAuth

```bash
curl -X GET "https://vibecode.bitrix24.com/v1/bizproc-tasks" \
  -H "X-Api-Key: YOUR_APP_KEY" \
  -H "Authorization: Bearer YOUR_SESSION_TOKEN"
```

### JavaScript API key

```javascript
const response = await fetch("https://vibecode.bitrix24.com/v1/bizproc-tasks", {
  method: "GET",
  headers: { "X-Api-Key": "YOUR_API_KEY" }
});
console.log(await response.json());
```

### JavaScript OAuth

```javascript
const response = await fetch("https://vibecode.bitrix24.com/v1/bizproc-tasks", {
  method: "GET",
  headers: { "X-Api-Key": "YOUR_APP_KEY", "Authorization": "Bearer YOUR_SESSION_TOKEN" }
});
console.log(await response.json());
```

## Response example

Empty list on the test account.

```json
{"success":true,"data":[],"meta":{"start":0,"total":0}}
```

Invalid parameters are refused before calling Bitrix24:

```json
{"success":false,"error":{"code":"INVALID_PARAMS","message":"Invalid request parameters"}}
```

## Errors

| HTTP | Code | Condition |
|---|---|---|
| 400 | `INVALID_PARAMS` | Malformed or missing parameters |
| 401 | `TOKEN_MISSING` | No Bitrix24 credentials |
| 403 | `SCOPE_DENIED` | Missing bizproc scope |
| 403 | `BITRIX_ACCESS_DENIED` | Bitrix24 denies access |
| 422 | `BITRIX_ERROR` | Bitrix24 business refusal; original sanitized message |
| 502 | `BITRIX_RESPONSE_INVALID` | Unexpected response shape or action result |

Common refusals and limits: [API errors](/docs/errors).

## See also

- [Business-process tasks](/docs/automation/bizproc-tasks)
- [Workflow instances](/docs/automation/workflows)