Reference
Mark as read
Mark the chat as read on Telegram (the customer sees the read ticks).
View MarkdownThis page is generated from the source code on every release.
Mark the chat as read on Telegram (the customer sees the read ticks).
Overview
| Name | Value |
|---|---|
| Code | conversations.mark_read |
| 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 |
| In the app | Inbox → open a chat |
Input fields
| Field | Type | Required | Description |
|---|---|---|---|
conversationId |
uuid |
Yes | |
topicIds |
integer[] |
No |
Example request
curl -X POST https://tlg.builera.app/api/public/v2/ops/conversations.mark_read \
-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"}'Output fields (data)
| Field | Type | Required |
|---|---|---|
ok |
true |
Yes |
changed |
false |
Yes |
Example answer
{
"data": {
"ok": true,
"changed": false
}
}Using it over MCP
Tool conversations_mark_read is listed on the profiles: Real-time operations (realtime), Automation setup (setup), Discover (prospecting), Reports (reports), Administration (admin), Full (full). On other profiles, find it with tools_search and run it with tools_run.