# Service methods

Messenger methods that do not belong to a single section: the forms for creating a task or a flow from a chat, context for chat bots, a Zoom meeting, the update state and counters, plan restrictions, promo hints, the user's department and the desktop app logout.

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

## Operations

- [Task form](./service/task-form.md) — `GET /v1/chats/:dialogId/task-form`, `POST /v1/chats/messages/:messageId/task-form`
- [Flow form](./service/flow-form.md) — `GET /v1/chats/:dialogId/flow-form`
- [Context for bots](./service/bot-context.md) — `POST /v1/chats/:dialogId/bot-context`
- [Zoom meeting](./service/zoom.md) — `POST /v1/chats/:dialogId/zoom`
- [Update state](./service/state.md) — `GET /v1/chats/state`
- [Plan restrictions](./service/tariff-restrictions.md) — `GET /v1/chats/tariff-restrictions`
- [Promo hints](./service/promotions.md) — `GET /v1/chats/promotions`
- [User department](./service/department.md) — `GET /v1/chats/users/:userId/department`
- [Desktop app logout](./service/desktop-logout.md) — `POST /v1/chats/desktop/logout`

## Reads that change state

The task and flow forms return data, but in doing so Bitrix24 may add the caller to a chat that allows auto-join — just as opening the chat in the interface does. A read-only key therefore gets `403 WRITE_BLOCKED_READONLY_KEY` for them before any call to Bitrix24. Details — [Access rights](/docs/access-rights).

A read-only key also cannot call the other operations that change something: context for bots, Zoom, the desktop app logout and the task form for a message.

## See also

- [Chats and messages](/docs/chats)
- [Messenger settings](/docs/chats/settings)