# Stickers

Read the user's sticker packs and manage them: the pack list and a single pack, renaming and deleting your own packs, adding other users' packs, deleting stickers from a pack and the recent stickers list.

**Scope:** `im` | **Base URL:** `https://vibecode.bitrix24.com/v1` | **Authorization:** `X-Api-Key`

## Operations

- [List of packs](./stickers/packs.md) — `GET /v1/chats/stickers/packs`
- [Sticker pack](./stickers/pack.md) — `GET`, `PATCH`, `DELETE /v1/chats/stickers/packs/:packId`
- [Add and remove a pack](./stickers/link.md) — `POST`, `DELETE /v1/chats/stickers/packs/:packId/link`
- [Delete stickers from a pack](./stickers/pack-stickers.md) — `DELETE /v1/chats/stickers/packs/:packId/stickers`
- [Recent stickers](./stickers/recent.md) — `DELETE /v1/chats/stickers/recent`, `DELETE /v1/chats/stickers/recent/:stickerId`

## Two kinds of packs

- `vendor` — built-in Bitrix24 packs. They can be read but cannot be renamed, deleted or removed from the list.
- `custom` — packs uploaded by users. Only the author can rename or delete a pack; another user's pack can be added to your own list.

The two kinds are numbered independently: a built-in pack and a user pack may share the same `id`. That is why a pack is always addressed by a pair — `packId` in the path and `packType` in the query parameters.

You cannot create a pack or add stickers to it through the API: sticker images are accepted only by the Bitrix24 file uploader, which has no REST method.

## See also

- [Chats and messages](/docs/chats)
- [Messages](/docs/chats/messages)