# Saved blocks

Block templates in the "My blocks" section of the catalog: a configured page block saved as a template that every editor of the Bitrix24 account can add to their pages.

Bitrix24 API: `landing.landing.favoriteBlock`, `landing.landing.unFavoriteBlock`
Scope: `landing`

## Operations

- [Save a block to "My blocks"](/docs/entities/pages/favorite) — `POST /v1/pages/:pageId/blocks/:blockId/favorite`
- [Delete a template from "My blocks"](/docs/entities/block-repository/favorites/delete) — `DELETE /v1/block-repository/favorites/:blockId`

## Key fields

| Field | Description |
|------|----------|
| `blockId` | Template ID in "My blocks". Returned in the response of [saving a block](/docs/entities/pages/favorite) and differs from the ID of the source page block |
| `code` | Template code in the form `sourceCode@blockId`, for example `01.big_with_text@29417`. The template appears under this code in the [block catalog](/docs/entities/pages/catalog) |
| `name` | Template name. Passed when saving the block |
| `sections` | Catalog sections the template goes into. Passed when saving the block. Without the field, the template goes into the section of the source block |

## Before you start

1. **A template is shared across the account.** Every editor of the Bitrix24 account sees a saved block in the catalog. It is not a personal bookmark.
2. **The template ID and the page block ID are different numbers.** Deletion accepts only the `blockId` from the save response. The ID of a regular page block returns `404 ENTITY_NOT_FOUND`.
3. **You can delete only your own template.** Only a template saved by the same Bitrix24 user the key was issued for can be deleted.
4. **Deletion is irreversible and does not touch the page.** The template disappears from the catalog and cannot be restored — save the block again. The source block on the page stays unchanged after the template is deleted.

## Typical scenario

1. Find the block on the page: [`GET /v1/pages/:pageId/blocks`](/docs/entities/pages/blocks/list).
2. Save it to "My blocks": [`POST /v1/pages/:pageId/blocks/:blockId/favorite`](/docs/entities/pages/favorite) with `{"name": "Promo cover"}`. The response contains the template `blockId` and `code`.
3. Find the template in the catalog by `code`: [`GET /v1/block-repository`](/docs/entities/pages/catalog).
4. Delete a template you no longer need: [`DELETE /v1/block-repository/favorites/:blockId`](/docs/entities/block-repository/favorites/delete).

## Limits

| Limit | Value |
|-------|----------|
| Templates per call | one: saving and deletion work with a single block |
| Rate limit | shared across the Vibecode API — see [Limits and optimization](/docs/optimization) |

## See also

- [Block catalog](/docs/entities/pages/catalog)
- [Page block list](/docs/entities/pages/blocks/list)
- [Pages](/docs/entities/pages)