Reference
Answer Telegram's terms of service
Accept or decline Telegram's new terms of service (declining pauses the account).
View MarkdownThis page is generated from the source code on every release.
Accept or decline Telegram's new terms of service (declining pauses the account).
Overview
| Name | Value |
|---|---|
| Code | accounts.answer_tos |
| Scope needed | accounts.manage |
| Risk | Write |
| May need confirmation | No |
| Runs as | Queues work for a node |
Needs Idempotency-Key |
Yes |
| Member roles allowed | owner, manager |
| In the app | Accounts → Terms |
Input fields
| Field | Type | Required | Description |
|---|---|---|---|
accountId |
uuid |
Yes | |
accept |
true/false |
Yes | |
tosId |
text |
No |
Example request
curl -X POST https://tlg.builera.app/api/public/v2/ops/accounts.answer_tos \
-H "Authorization: Bearer $TELEGRAM_AUTO_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: <unique key per operation>" \
-d '{"accountId":"00000000-0000-0000-0000-000000000000","accept":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: "accounts.answer_tos". Tool name when listed: accounts_answer_tos.