For AI agents: markdown of this page — /docs-content-en/entities/crm-card-layouts.md documentation index — /llms.txt

These methods are rolling out — introduced in crm 26.1700.0. Cloud availability also depends on Bitrix24 enabling this capability. Until it is enabled for your Bitrix24 account, the API returns 422 METHOD_NOT_YET_AVAILABLE with error.release.

Named CRM card layouts

Keep several sets of card sections and fields, and select the current layout for an employee.

Bitrix24 API: crm.<entity>.detailpagelayout.* Scope: crm

Operations

Key fields

Field Description
Fieldid DescriptionOpaque string from the layout list, including system IDs.
Fieldname DescriptionName. May be null for system layouts.
Fieldconfiguration DescriptionSections with names and arrays of elements.
Fieldaudience DescriptionEmployees and access groups. May be null.

Before you start

  1. entityType: company, contact, deal, lead, quote, smartinvoice, smartprocess<N>. Get the SPA number from the SPA list.
  2. Every request requires a category. Source: GET /v1/categories, 0 is accepted.
  3. Creation returns a numeric ID. Convert it to a string for subsequent requests.
  4. Bitrix24 checks access to the audience, target employee and system layout. Writes require READWRITE.
  5. The current card configuration has a separate section: CRM card layout.

Typical workflow

  1. List CRM card layouts.
  2. Create a CRM card layout.
  3. Update a CRM card layout.
  4. Select the current CRM layout.
  5. Delete a CRM card layout.

Limits

The list reads one page using limit and offset. There is no total or hasMore. Bitrix24 checks accepted values and field limits. Empty arrays may be refused as missing fields. Updating an array replaces it in full.

See also