Layout templates

Requires the landing key scope. Every route accepts optional query scope=KNOWLEDGE, GROUP or MAINPAGE; omit it for ordinary sites. All IDs are positive safe integers. Writes with READONLY keys are refused before any portal call.

Stable code comes from XML_ID; title is localized by the portal. No CONTENT HTML is exposed. areaCount is the number of layout areas.

Operations

• GET /v1/site-templates — landing.template.getlist.

Example

curl -X GET "https://vibecode.bitrix24.com/v1/site-templates" -H "X-Api-Key: YOUR_API_KEY"

Response

{
  "success": true,
  "data": [
    {
      "id": 7,
      "code": "header_footer",
      "title": "Header and footer",
      "areaCount": 2,
      "active": true,
      "sort": 100
    }
  ]
}

Empty bindings return []; empty areas return {areas:{}}. Writes return the persisted state. Bitrix24 true is insufficient: a mismatched reread returns 422 BITRIX_ERROR.

Errors

400 INVALID_PARAMS / INVALID_SCOPE / MISSING_REQUIRED_FIELDS; 401 TOKEN_MISSING; 403 SCOPE_DENIED / BITRIX_ACCESS_DENIED / WRITE_BLOCKED_READONLY_KEY; 404 ENTITY_NOT_FOUND; 409 PORTAL_ADDRESS_CHANGED / LANDING_MODULE_NOT_ENABLED / TEMPLATE_AREAS_BUSY; 422 BITRIX_ERROR; 429 rate limits; 502 / 503 transport failures.