# Configurable activities

A configurable activity is a record in the timeline of a CRM entity with its own styling: an icon, a title, body blocks, and buttons. The `layout` structure defines its appearance. It suits integrations that show a card for a call, request, delivery, or other external event in the timeline of a deal, lead, contact, or company.

Bitrix24 API: `crm.activity.configurable.*`
Scope: `crm`

Deleting and listing configurable activities go through the common activities API: [`DELETE /v1/activities/:id`](/docs/entities/activities/delete) and [`GET /v1/activities`](/docs/entities/activities/list).

## Operations

- [Create activity](./configurable/create.md) — `POST /v1/activity-configurable`
- [Get activity](./configurable/get.md) — `GET /v1/activity-configurable/:id`
- [Update activity](./configurable/update.md) — `PATCH /v1/activity-configurable/:id`

## When to use

- A call from external telephony appears in a deal's timeline as a card with an action button.
- A request from an external service is shown with "Confirm" and "Reject" actions.
- A delivery or external event appears in a lead's card with its own icon and link.

## OAuth application requirements

Create and update work only in the context of an application: a `vibe_app_*` authorization key with a session token in the `Authorization: Bearer` header is required. A request with a `vibe_api_*` personal key returns `422 BITRIX_ERROR`, with `ERROR_WRONG_CONTEXT` in the `b24Code` field of the response. Reading an activity works with both key types. Only the application that created an activity can modify it.

A custom activity type is registered in Bitrix24 as configurable in the context of the same application. Without a custom type, an activity is created with the `CONFIGURABLE` type.

## See also

- [Activities](/docs/entities/activities)
- [Activity bindings](/docs/entities/activities/bindings)
- [CRM Timeline](/docs/timeline-logs)
- [Keys and authorization](/docs/keys-auth)