Reference
Send a sticker / GIF
Send a sticker or GIF from `stickers.list` into a chat: `item: { id, kind }` (the server fills Telegram's handle from the latest listing). Same lock, limits and order as a text send.
View MarkdownThis page is generated from the source code on every release.
Send a sticker or GIF from stickers.list into a chat: item: { id, kind } (the server fills Telegram's handle from the latest listing). Same lock, limits and order as a text send.
Overview
| Name | Value |
|---|---|
| Code | stickers.send |
| Scope needed | messages.send |
| Risk | Write |
| May need confirmation | No |
| Runs as | Queues work for a node |
Needs Idempotency-Key |
Yes |
| Member roles allowed | owner, manager, agent |
| Needs a worker from version | 1.0.19 |
| In the app | Inbox → sticker / GIF panel |
Input fields
| Field | Type | Required | Description |
|---|---|---|---|
conversationId |
uuid |
Yes | |
item |
object |
Yes | |
replyToMessageId |
integer |
No | |
topicId |
integer |
No | |
inReplyToEventId |
text |
No | |
ifLastMessageId |
uuid |
No |
Example request
curl -X POST https://tlg.builera.app/api/public/v2/ops/stickers.send \
-H "Authorization: Bearer $TELEGRAM_AUTO_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: <unique key per operation>" \
-d '{"conversationId":"00000000-0000-0000-0000-000000000000","item":"…"}'Output fields (data)
| Field | Type | Required |
|---|---|---|
ok |
true |
Yes |
messageId |
text |
Yes |
jobId |
text |
Yes |
Example answer
{
"data": {
"ok": true,
"messageId": "00000000-0000-4000-8000-000000000000",
"jobId": "00000000-0000-4000-8000-000000000000"
}
}Using it over MCP
Not listed on any profile: call tools_describe then tools_run with code: "stickers.send". Tool name when listed: stickers_send.