Delete access entry

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

Deletes an access entry — a user or a department — from a BLACKHOLE server's access list. The endpoint handles both kinds of entry: an accessId can refer to either a user (BlackHoleAccess) or a department (BlackHoleDepartment) — the platform looks in the first table, then in the second. After deletion, the entry disappears from GET /access.

Parameters

Examples

curl — personal key

curl -X DELETE -H "X-Api-Key: YOUR_API_KEY" \
  https://vibecode.bitrix24.com/v1/infra/servers/SERVER_ID/access/ACCESS_ID

curl — OAuth application

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

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

const res = 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',
    },
  }
)
const { success } = await res.json()
if (success) console.log('Entry deleted')

Response fields

Response example

{ "success": true }

Error response example

404 — entry not found (already deleted, wrong accessId, or an accessId that belongs to another server):

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

Errors

The full list of common API errors — Errors.

Known specifics

• Wider access requires approval. If restoring other grants after deletion would widen the audience, the request returns 409 AUDIENCE_APPROVAL_REQUIRED and leaves the entry in place. After human approval, retry the same DELETE for the same id and accessId, using the original credential and ?approvalId=APPROVAL_ID. No approval is needed when the platform can prove that access only narrows. Check or cancel your own request.
• Hard delete, not soft delete. The entry is erased from the database. It cannot be restored — you will have to call POST /access again.
• Deletion also closes sessions that are already open. If deleting the entry takes away the user's access, the application becomes unavailable to them within a minute, even in a tab opened earlier.
• share-url links do not depend on the list. They are revoked separately — Revoke a token.
• accessId is bound to the server. An attempt to delete another server's access entry (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 under 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.
• 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
• Add user/department
• Access policy