Reference

Check @SpamBot

Ask Telegram's @SpamBot whether the account is restricted. Follow the operation for the answer.

View MarkdownThis page is generated from the source code on every release.

Ask Telegram's @SpamBot whether the account is restricted. Follow the operation for the answer.

Overview

Name	Value
Code	`accounts.check_spambot`
Scope needed	`accounts.read`
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 → Safety

Input fields

Field	Type	Required	Description
`accountId`	`uuid`	Yes

Example request

curl -X POST https://tlg.builera.app/api/public/v2/ops/accounts.check_spambot \
  -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"}'

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.check_spambot". Tool name when listed: accounts_check_spambot.

Check @SpamBot

#Overview

#Input fields

#Example request

#Output fields (data)

#Example answer