## Delete an activity

`DELETE /v1/bizproc-activities/:code`

Deletes a business process activity by code. A deleted activity cannot be restored via the API — register a new one if needed. Can only be called with an authorization key together with the `Authorization: Bearer` header.

## Parameters

| Parameter | Type | Required | Description |
|----------|-----|:-----:|---------|
| `code` (path) | string | Yes | Activity string code |

## 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 -X DELETE "https://vibecode.bitrix24.com/v1/bizproc-activities/notify_manager" \
  -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/notify_manager', {
  method: 'DELETE',
  headers: {
    'X-Api-Key': 'YOUR_APP_KEY',
    'Authorization': 'Bearer USER_SESSION_TOKEN',
  },
})

if (res.status === 204) {
  console.log('Activity deleted')
}
```

## Response

On successful deletion, HTTP status `204 No Content` with an empty body is returned — success is checked by the status.

## Response example

```http
HTTP/1.1 204 No Content
```

## Error response example

422 — no activity with the given code was found:

```json
{
  "success": false,
  "error": {
    "code": "BITRIX_ERROR",
    "message": "Activity or Robot not found!"
  }
}
```

## Errors

| HTTP | Code | Description |
|------|-----|----------|
| 403 | `OAUTH_REQUIRED` | The request was sent with an API key. Only an authorization key can delete activities |
| 401 | `TOKEN_MISSING` | The authorization key was sent without the `Authorization: Bearer` 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 |
| 422 | `BITRIX_ERROR` | Bitrix24 did not find an activity with the given code or rejected the deletion — the reason is in `error.message` |

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

## See also

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