> ## Documentation Index
> Fetch the complete documentation index at: https://docs.yo-lead.com/llms.txt
> Use this file to discover all available pages before exploring further.

# VK

> Understand VK community conversations, history, and external video links.

Connected VK communities use `ticket.channel.type: "vk"` in webhooks. Contact identities use `vk_user_id`. Connections and provider permissions are managed in the YoLead UI.

## Messages and sending

Employees can send text replies in existing chats. Starting an outbound conversation with a VK user requires permission for the community to message that user, employee access, and outbound chat initiation on the company's plan. In Embed, existing-chat sending requires `showSendInput`; starting a new conversation requires `startOutboundChat`.

Outgoing attachment sending is currently unavailable. Incoming attachments can still appear in Public API history and message webhooks.

## History and attachments

Newly stored messages use the common [attachment descriptor](https://docs.yo-lead.com/concepts/message-attachments.md). Older tickets whose history is read from VK can use a separate format with `source: "vk"`, opaque attachment identifiers, and optional provider URLs.

Stored history remains readable after disconnection, subject to company access and plan restrictions. History read from VK requires an available channel and usable provider access.

Stored VK video attachments can have `accessMode: "external"`. Use [Get attachment external URL](https://docs.yo-lead.com/api-reference/attachments/get-attachment-external-url.md) to request a viewing link. This endpoint accepts YoLead attachment ObjectIds, not opaque identifiers from provider-history descriptors.

## Attribution

An incoming message can supply `ref` and `ref_source` when it creates a ticket. These values appear in `ticket.attribution` in Public API history and webhook Ticket objects. See [Ticket attribution](https://docs.yo-lead.com/concepts/ticket-attribution.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.