## Delete requisite

`DELETE /v1/requisites/:id`

Deletes a requisite by ID. Addresses and bank details bound to the requisite are deleted together with it on the Bitrix24 side.

## Parameters

| Parameter | Type | Required | Description |
|----------|-----|:-----:|---------|
| `id` (path) | number | yes | Requisite ID |

## Examples

### curl — personal key

```bash
curl -X DELETE "https://vibecode.bitrix24.com/v1/requisites/42" \
  -H "X-Api-Key: YOUR_API_KEY"
```

### curl — OAuth app

```bash
curl -X DELETE "https://vibecode.bitrix24.com/v1/requisites/42" \
  -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/requisites/42', {
  method: 'DELETE',
  headers: {
    'X-Api-Key': 'YOUR_API_KEY',
  },
})

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

### JavaScript — OAuth app

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

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

## Response

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

## Response example

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

## Error response example

404 — requisite not found:

```json
{
  "success": false,
  "error": {
    "code": "ENTITY_NOT_FOUND",
    "message": "The Requisite with ID '999999999' is not found"
  }
}
```

## Errors

| HTTP | Code | Description |
|------|-----|---------|
| 404 | `ENTITY_NOT_FOUND` | No requisite with that ID found |
| 403 | `ACCESS_DENIED` | No access to the parent entity |
| 403 | `SCOPE_DENIED` | API key does not have the `crm` scope |
| 401 | `TOKEN_MISSING` | API key has no configured tokens |

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

## Known specifics

**Deletion is cascading.** Addresses and bank details bound to the requisite are deleted together with it — this is Bitrix24 behavior, it is not configurable.

**No soft delete.** After deletion a requisite cannot be restored — create a new one. If you need to temporarily stop using it, set the `active: false` field via [update](/docs/entities/requisites/update).

## See also

- [List requisites](/docs/entities/requisites/list) — find a requisite before deleting
- [Get requisite](/docs/entities/requisites/get) — view the data before deleting
- [Update requisite](/docs/entities/requisites/update) — deactivate instead of deleting (`active: false`)
- [Batch](/docs/batch) — bulk deletion
- [Limits and optimization](/docs/optimization) — rate limits