#List servers

GET /v1/infra/servers

Returns the servers managed by the current API key. Deleted servers (status: "deleted") are not included by default — pass ?includeDeleted=true to see them. Servers of other keys are not visible, even within the same Bitrix24 account. To view all servers of a Bitrix24 account, use the administrator panel in the dashboard.

#Query parameters

Why this exists: sources outlive their server. Once you delete a server you can still list, untag, download or clean up its source versions — but that needs its id, and there is nowhere else to get it. The sources contract lives on the Source storage page.

#Examples

#curl — personal key

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

#curl — OAuth application

curl -H "X-Api-Key: YOUR_APP_KEY" \
  -H "Authorization: Bearer USER_SESSION_TOKEN" \
  https://vibecode.bitrix24.com/v1/infra/servers

#JavaScript — personal key

const res = await fetch('https://vibecode.bitrix24.com/v1/infra/servers', {
  headers: { 'X-Api-Key': 'YOUR_API_KEY' },
})
const { data: servers } = await res.json()

servers.forEach(s => {
  const ready = s.status === 'running' && s.blackholeStatus === 'CONNECTED'
  console.log(`${s.name}: ${ready ? '✓ ready' : s.status} — ${s.appUrl}`)
})

#JavaScript — OAuth application

const res = await fetch('https://vibecode.bitrix24.com/v1/infra/servers', {
  headers: {
    'X-Api-Key': 'YOUR_APP_KEY',
    'Authorization': 'Bearer USER_SESSION_TOKEN',
  },
})
const { data: servers } = await res.json()

#Response fields

#Response example

{
  "success": true,
  "data": [
    {
      "id": "e765edfc-ba0a-43de-b8ea-838dd872c522",
      "status": "running",
      "provider": "bitrix-cloud",
      "kind": "STANDALONE",
      "galaxyId": null,
      "appCount": null,
      "name": "vibe-server-pd9l",
      "displayName": "vibe-server-pd9l",
      "description": null,
      "ip": "111.88.251.211",
      "ssh": {
        "user": "ubuntu",
        "port": 22,
        "hasPassword": true
      },
      "plan": "bc-small",
      "region": "bc-eu-central",
      "image": "ubuntu-2404-lts",
      "monthlyCost": "24",
      "mode": "OPEN",
      "createdVia": "ui",
      "subdomain": "app-05b67cf7",
      "blackholeStatus": "CONNECTED",
      "accessPolicy": "OWNER_ONLY",
      "runtimeId": null,
      "runtimeStatus": null,
      "appUrl": "https://app-05b67cf7.vibecode.bitrix24.com",
      "sleepAfterMinutes": null,
      "provisionError": null,
      "provisionErrorCode": null,
      "provisionReason": null,
      "createdAt": "2026-04-03T13:30:25.819Z"
    }
  ]
}

#Error response example

401 — no API key passed:

{
  "success": false,
  "error": {
    "code": "MISSING_API_KEY",
    "message": "API key required. Pass via X-Api-Key header."
  }
}

#Errors

The full list of common API errors — Errors.

#Known specifics

• An empty array while servers are running means the current key does not manage them. The output is limited to the servers of the current key. After the previous key expires or is revoked, the server stays bound to it. If the previous key is deleted, the server is left without a managing key. In both cases a new key returns an empty data while the servers keep running and remain visible in the dashboard. How to restore access — Server access recovery.
• Even a Bitrix24 account administrator sees only their own servers. For an account-wide picture, use the administrator panel in the dashboard — the API-key restriction cannot be changed.
• Servers of Bitrix24 accounts marked as deleted are hidden automatically. The platform checks account availability daily: if an account responds with 410/403 three days in a row, it is marked as deleted and its servers stop being displayed.
• The response is not paginated — all of the key's servers are returned in a single array.
• includeDeleted=true does not surface servers of deleted Bitrix24 accounts. The account-level hiding above applies whatever the parameter says: the account is gone, so a call against those servers is meaningless.

#See also

• Create a server
• Get a server
• Update name and description
• Delete a server
• Lifecycle
• Server access recovery