Reference
Archive / unarchive
Move the chat to (or out of) Telegram's Archive folder for this account.
View MarkdownThis page is generated from the source code on every release.
Move the chat to (or out of) Telegram's Archive folder for this account.
Overview
| Name | Value |
|---|---|
| Code | conversations.archive |
| Scope needed | messages.manage |
| 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.15 |
| In the app | Inbox → chat menu → Archive |
Input fields
| Field | Type | Required | Description |
|---|---|---|---|
conversationId |
uuid |
Yes | |
archived |
true/false |
Yes |
Example request
curl -X POST https://tlg.builera.app/api/public/v2/ops/conversations.archive \
-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","archived":true}'Output fields (data)
| Field | Type | Required |
|---|---|---|
ok |
true |
Yes |
jobId |
text |
Yes |
Example answer
{
"data": {
"ok": true,
"jobId": "00000000-0000-4000-8000-000000000000"
}
}Using it over MCP
Not listed on any profile: call tools_describe then tools_run with code: "conversations.archive". Tool name when listed: conversations_archive.