Page Entity Fields

Method	Description	Read	Write
ID	Landing page ID. Created automatically and is unique within database.	Yes	No
CODE	Unique symbol code for the landing page. Added to the website address, if it is not the main page. Required fields.	Yes	Yes
RULE	Regular expression to display landing page as per mask. For example, the rule `section/([\d]+)` for the landing page in the site root responds to all landing page type `/section/<n>/`, where <n> - any number.	Yes	No
ACTIVE	Landing page active status: Y / N.	Yes	Yes
DELETED	The flag of deleted landing page Entities marked as deleted are not available in any query. The system will not identify them. You can access such entities via REST only by directly specifying in filtration DELETED=Y. : Y / N.	Yes	Yes
TITLE	Landing page name. Required field.	Yes	Yes
XML_ID	External key for developer needs. Not used by the service.	Yes	Yes
DESCRIPTION	Unspecified landing page description. Displayed in the list of landing pages.	Yes	Yes
SITE_ID	ID for the site, to which the page is attached. Required field.	Yes	Yes
CREATED_BY_ID	ID for the user who created landing page.	Yes	No
MODIFIED_BY_ID	ID of the user who modified landing page.	Yes	No
DATE_CREATE	Creation date.	Yes	No
DATE_MODIFY	Modification date.	Yes	No
SITEMAP	Landing page is available in sitemap (`/sitemap.xml`), Y / N.	Yes	Yes
FOLDER	Flag that specifies page as folder (Y / N). Page-folder fully behaves as a standard page except it can contain other pages. Subfolders folders are not allowed.	Yes	Yes
FOLDER_ID	ID of the folder that contains the landing page. Subfolders folders are not allowed.	Yes	Yes
TPL_ID	ID of the page view template.	Yes	Yes
TPL_CODE	ID of the third-party partner's solution, based on which the site was created. For example, bitrix.eshop.	Yes	No