> ## 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.

# Avito

> Understand Avito conversations, listing context, and supported messages.

YoLead supports connected Avito accounts as company channels. Webhook Ticket objects use `channel.type: "avito"`. Connecting and managing an account is done in the YoLead UI.

## Contacts and replies

Avito contact identities use `avito_user_id` in the form `<accountId>:<buyerId>`. Both parts contain 1–128 letters, digits, underscores, or hyphens. Preserve the account prefix: the same buyer identifier in another account is a different identity.

Employees can reply to an existing Avito chat, including through Embed with `showSendInput`. Starting a new conversation from a contact identity is unavailable. Text is limited to 1000 characters. One JPEG/PNG photo of up to 10 MiB can be sent without a caption; document sending is unavailable. Storage settings can lower the file limit.

## Listing context

Messages in Public API ticket history and incoming-message webhooks can include optional `context`:

```json theme={null}
{
  "type": "listing",
  "id": "123456789",
  "title": "Bicycle",
  "price": "15000 RUB",
  "url": "https://www.avito.ru/items/123456789"
}
```

Only `type` and `id` are required when context is present. `title`, `price`, and the HTTPS `url` are optional. Price is display text, not a numeric amount. Different messages in one chat can refer to different listings. Context is separate from [ticket attribution](https://docs.yo-lead.com/concepts/ticket-attribution.md); do not assume it is available for every historical message.

## History, attachments, and read status

YoLead can import up to 50 available earlier messages into a linked inactive ticket. Provider history limits can prevent a complete import. Incoming images and voice messages use the existing attachment descriptors. Imported history does not automatically download old attachment bytes, and unsupported content can appear as a text placeholder.

YoLead synchronizes available provider messages and read status in the background. Loading history does not mark the conversation as read; an explicit read action in the app or iframe does. Already stored history remains readable after disconnection, subject to company access and plan restrictions.


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