For AI agents: markdown of this page — /docs-content-en/lists/lists/type.md documentation index — /llms.txt

Infoblock type

GET /v1/lists/:iblockId/type

Determines the infoblock type from the list ID or symbolic code. The iblockTypeId and socnetGroupId parameters are not required.

Parameters

Parameter Type Required Description
iblockId (path) string yes The numeric ID or symbolic CODE of the list from List of lists

Examples

curl — personal key

Terminal
curl https://vibecode.bitrix24.com/v1/lists/121/type \
  -H "X-Api-Key: YOUR_API_KEY"

curl — OAuth application

Terminal
curl https://vibecode.bitrix24.com/v1/lists/121/type \
  -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/lists/121/type', {
  headers: { 'X-Api-Key': 'YOUR_API_KEY' },
})
const { data } = await res.json()
console.log('Infoblock type:', data.iblockTypeId)

JavaScript — OAuth application

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

Response fields

HTTP 200.

Field Type Description
success boolean Always true on success
data object Object containing the infoblock type
data.iblockTypeId string Infoblock type identifier. Examples:
lists — regular lists
lists_socnet — workgroup lists
bitrix_processes — internal workflows
structure — company structure type (contains the absence infoblock for the absence calendar)

Response example

JSON
{
  "success": true,
  "data": {
    "iblockTypeId": "lists"
  }
}

Error response example

404 — list not found:

JSON
{
  "success": false,
  "error": {
    "code": "LIST_NOT_FOUND",
    "message": "List not found"
  }
}

Errors

HTTP Code Description
404 LIST_NOT_FOUND The list was not found among those accessible to the user
403 BITRIX_ACCESS_DENIED Bitrix24 denied access to the list
409 LISTS_MODULE_NOT_ENABLED The Lists module is not enabled on the portal
403 SCOPE_DENIED The API key lacks the lists scope
401 TOKEN_MISSING The API key has no configured tokens

The full list of common API errors — Errors.

See also