messages[].attachmentsfromGET /v1/tickets/{ticketId}/history;data.message.attachmentsinticket.createdandmessage.incomingwebhooks.
Only
id and kind are guaranteed. Integrations must tolerate missing optional metadata and attachment kinds added in future versions.
Standard descriptors do not include provider identifiers, temporary provider URLs, credentials, storage paths, or storage state.
VK provider-history descriptors
VK history read from the source channel can contain a separate descriptor format identified bysource: "vk". Its id is an opaque string rather than a YoLead attachment ObjectId. In addition to kind and the optional metadata above, this format can include contentUrl, previewUrl, and externalUrl supplied by VK. These URLs are optional and their availability can change.
The source and URL fields belong to this separate format; accessMode belongs to the standard descriptor. Neither format includes YoLead storage details or authentication credentials. Treat attachment identifiers as opaque values.
Telegram albums
Telegram sends each album item as a separate message. Ticket history can include the same optionalmediaGroupId on those messages so an integration can group them. Each Telegram message contains at most one attachment descriptor.
mediaGroupId is currently part of Public API ticket history messages; it is not included in message webhook objects.
Availability and history
Existing stored messages are not automatically backfilled, so older messages can have an emptyattachments array even when the original provider message contained a file. Imported Telegram Account history can include attachment metadata, and VK provider history can include the separate descriptors described above. Metadata availability in imported history depends on the channel.
New WhatsApp messages support images, documents, video, audio, voice messages, and stickers. Avito supports incoming images and voice messages; unsupported content can be represented by a text placeholder. Imported Avito history does not automatically download old attachment bytes. WhatsApp files follow local retention and quota rules and cannot be refetched on demand after eviction.
The Public API exposes attachment metadata but does not provide an API-key-authenticated endpoint for downloading attachment bytes. YoLead’s authenticated application and embedded iframe can display or download files when they are still available. Do not construct a download URL from the attachment id.
External VK video links
For a stored VK video attachment,GET /v1/attachments/{attachmentId}/external-url returns an external viewing URL using the normal Public API HMAC authentication and read scope:
accessMode: "external". Opaque IDs from the separate VK provider-history format cannot be used with this endpoint. The response is JSON, not file bytes or an HTTP redirect, and includes Cache-Control: no-store. An active VK channel and usable provider access are required. Missing or unsupported attachments return 404; unavailable provider access can return 503. Treat the URL as temporary provider data rather than a permanent file address.