Для AI-агентов: markdown этой страницы — /docs/schema-4fff85570d7119a3227c715880cd0f4b2179370507d0b324a126ca523588aa44.mdиндекс документации — /llms.txt
Схема: ButtonCallback
Обновлено
| Поле | Значение |
|---|---|
| properties.callback_data.description | "An integration mechanism of an ExternalApp key: when the user taps the button, the value is delivered by the button.clicked webhook to the server of the app that sent the push, so the app must have been subscribed to the button.clicked webhook when it was provisioned, otherwise the button is refused with INVALID_BUTTON_CONFIG. Sent with any other credential (an OAuth grant or an M2M credential) a callback button is refused with INVALID_BUTTON_CONFIG; the MCP send_notification tool carries url buttons only. The platform prefixes it with ext:{app}:, and the prefixed value must fit 64 bytes. Answered only for a Telegram user: for a MAX or VK user a callback button is refused with INVALID_BUTTON_CONFIG — use a url button." |
| properties.callback_data.maxLength | 64 |
| properties.callback_data.type | "string" |
| properties.text.maxLength | 30 |
| properties.text.type | "string" |
| properties.type.enum | ["callback"] |
| properties.type.type | "string" |
| required | ["text","type","callback_data"] |
| type | "object" |