## Delete access entry

`DELETE /v1/infra/servers/:id/access/:accessId`

Deletes an access entry — a user or a department — from a BLACKHOLE server's list. The endpoint is universal: the same `accessId` may refer to either a user (`BlackHoleAccess`) or a department (`BlackHoleDepartment`) — the platform first looks in the first table, then in the second. After deletion, the entry disappears from [`GET /access`](./access-list.md).

## Parameters

| Parameter | In | Type | Req. | Description |
|----------|---|-----|:-----:|----------|
| `id` | path | string (UUID) | yes | BLACKHOLE server ID |
| `accessId` | path | string (UUID) | yes | Access entry ID from [`GET /access`](./access-list.md) or [`POST /access`](./access-add.md) |

## Examples

### curl — personal key

```bash
curl -X DELETE -H "X-Api-Key: YOUR_API_KEY" \
  https://vibecode.bitrix24.com/v1/infra/servers/SERVER_ID/access/b3a6f8d1-3c2a-4e17-9f0b-1a7c2d4e5f60
```

### curl — OAuth application

```bash
curl -X DELETE -H "X-Api-Key: YOUR_APP_KEY" \
  -H "Authorization: Bearer USER_SESSION_TOKEN" \
  https://vibecode.bitrix24.com/v1/infra/servers/SERVER_ID/access/ACCESS_ID
```

### JavaScript — personal key

```javascript
const res = await fetch(
  `https://vibecode.bitrix24.com/v1/infra/servers/${serverId}/access/${accessId}`,
  {
    method: 'DELETE',
    headers: { 'X-Api-Key': 'YOUR_API_KEY' },
  }
)
const { success } = await res.json()
if (success) console.log('Entry deleted')
```

### JavaScript — OAuth application

```javascript
await fetch(
  `https://vibecode.bitrix24.com/v1/infra/servers/${serverId}/access/${accessId}`,
  {
    method: 'DELETE',
    headers: {
      'X-Api-Key': 'YOUR_APP_KEY',
      'Authorization': 'Bearer USER_SESSION_TOKEN',
    },
  }
)
```

## Response fields

| Field | Type | Description |
|------|-----|----------|
| `success` | boolean | `true` on successful deletion |

## Response example

```json
{ "success": true }
```

## Error response example

404 — entry not found (already deleted, wrong accessId, or accessId of another server):

```json
{
  "success": false,
  "error": {
    "code": "NOT_FOUND",
    "message": "Access entry not found"
  }
}
```

## Errors

| HTTP | Code | Description |
|------|-----|----------|
| 400 | `BLACKHOLE_ONLY` | The server is in OPEN mode |
| 401 | `MISSING_API_KEY` | The `X-Api-Key` header was not provided |
| 401 | `INVALID_API_KEY` | Invalid or expired API key |
| 404 | `NOT_FOUND` | The server does not exist; or the entry was not found (wrong `accessId`, already deleted, or belongs to another server) |
| 429 | `RATE_LIMITED` | The platform's overall request limit was exceeded |

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

## Known specifics

- **Physical deletion, not soft-delete.** The entry is erased from the database. It cannot be restored — you will have to call [`POST /access`](./access-add.md) again.
- **`accessId` is bound to the server.** An attempt to delete an access entry of another server (correct `accessId` but wrong `:id` in the path) returns 404 `NOT_FOUND`. The platform deliberately does not reveal the existence of other servers' entries.
- **Deletion does not change the policy.** If you delete all users while `accessPolicy: "NAMED_USERS"`, the policy stays `NAMED_USERS` (and the application becomes inaccessible to everyone except the key owner). To "fully restore privacy", switch the policy back to `OWNER_ONLY` via [`PATCH /access-policy`](./access-policy.md).
- **The key owner cannot be deleted.** The owner always has access, even if they are not in the list. To revoke your own access, you need a different API key.

## See also

- [Access list](./access-list.md) — get the `accessId` to delete.
- [Add user/department](./access-add.md) — `POST /v1/infra/servers/:id/access`.
- [Access policy](./access-policy.md) — `PATCH /v1/infra/servers/:id/access-policy`.