System pages

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.

Types: mainpage, catalog, personal, cart, order, payment, compare, feedback. Unknown types are rejected before Bitrix24. PUT requires pageId from the same site: an absent page is 404 and a page from another site is 400. DELETE removes bindings, never the pages themselves. Removing one absent role is 404. Site DELETE clears every role on that site. Page DELETE removes that page from roles on all sites, then verifies its own site. active=true filters out inactive and deleted bound pages; default false includes them. URL read returns {url}; absent binding is 404 and additional query parameters are rejected.

Operations

• DELETE /v1/pages/:id/system-pages — landing.syspage.deleteForLanding.

Example

curl -X DELETE "https://vibecode.bitrix24.com/v1/pages/42/system-pages" -H "X-Api-Key: YOUR_API_KEY"

Response

{
  "success": true,
  "data": [
    {
      "type": "cart",
      "pageId": 614,
      "title": "Cart",
      "deleted": false,
      "active": false
    }
  ]
}

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.

If no own-site role existed before the call, the removal still reaches Bitrix24 but V1 returns 422 BITRIX_ERROR: it cannot verify cross-site-only roles. A successful acknowledgment alone is not proof of removal.