## Activity list

`GET /v1/bizproc-activities`

Returns the list of business process activity codes registered on the Bitrix24 account. Each response element is a string activity code used in the update and delete paths.

The method works only with an authorization key.

## Parameters

| Parameter | Type | Default | Description |
|----------|-----|-----------|---------|
| `limit` | number | `50` | Maximum number of codes in the response |

## Examples

The session token is issued by OAuth authorization, is valid for 24 hours, and cannot be renewed — [Passing the key](/docs/keys-auth#passing-the-key).

### curl — authorization key

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

### JavaScript — authorization key

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

const { success, data, meta } = await res.json()
console.log(`Registered activities: ${meta.total}`)
```

## Response fields

| Field | Type | Description |
|------|-----|---------|
| `success` | boolean | Always `true` on success |
| `data` | array | Array of strings — the codes of registered activities |
| `meta.total` | number | Number of codes in the response |
| `meta.hasMore` | boolean | Whether there are more records beyond `limit` |

## Response example

```json
{
  "success": true,
  "data": [
    "notify_manager",
    "sync_status"
  ],
  "meta": {
    "total": 2,
    "hasMore": false
  }
}
```

## Error response example

403 — the request was sent with an API key on a method that requires an authorization key:

```json
{
  "success": false,
  "error": {
    "code": "OAUTH_REQUIRED",
    "message": "bizproc-activities require an OAuth app key (vibe_app_*) with an Authorization: Bearer session — a personal vibe_api_* key lacks the per-user OAuth context Bitrix24 needs for these methods. Create an OAuth app (POST /v1/apps) and retry with its key. On this 403 switch keys — do NOT delete or recreate the app (that discards anything already registered under it, e.g. a bizproc robot you just registered)."
  }
}
```

## Errors

| HTTP | Code | Description |
|------|-----|---------|
| 403 | `OAUTH_REQUIRED` | Called with an API key. The method is available only to an authorization key |
| 401 | `TOKEN_MISSING` | The authorization key was sent without the `Authorization: Bearer <session>` header |
| 401 | `WRONG_AUTH_SCHEME` | The authorization key was sent in the `Authorization: Bearer` header. The key goes in `X-Api-Key`, while `Authorization: Bearer` carries the session token |
| 401 | `INVALID_SESSION` | The session token has expired or is invalid — authorize again |
| 403 | `SCOPE_DENIED` | The key lacks the `bizproc` scope |

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

## Known specifics

**An empty list is a successful response.** Until at least one activity is registered on the Bitrix24 account, `data` comes back as an empty array with code `200`. The absence of activities is not an error.

## See also

- [Register an activity](/docs/entities/bizproc-activities/create)
- [Keys and authorization](/docs/keys-auth)
- [Errors](/docs/errors)