Reference
Can this chat be called
Whether a call to this private chat would ring now, and if not why (calls_disabled, not_private_chat, account_unavailable, proxy_no_udp, worker_outdated, peer_opted_out, account_busy, node_calls_full, audio_endpoint_required). Limits and pacing are still decided by the gate when the job is claimed.
View MarkdownThis page is generated from the source code on every release.
Whether a call to this private chat would ring now, and if not why (calls_disabled, not_private_chat, account_unavailable, proxy_no_udp, worker_outdated, peer_opted_out, account_busy, node_calls_full, audio_endpoint_required). Limits and pacing are still decided by the gate when the job is claimed.
Overview
| Name | Value |
|---|---|
| Code | calls.readiness |
| Scope needed | messages.read |
| Risk | Read |
| May need confirmation | No |
| Runs as | Answers right away |
Needs Idempotency-Key |
No |
| Member roles allowed | owner, manager, agent |
| In the app | Inbox → private chat → Call button |
Input fields
| Field | Type | Required | Description |
|---|---|---|---|
conversationId |
uuid |
Yes |
Example request
curl -X POST https://tlg.builera.app/api/public/v2/ops/calls.readiness \
-H "Authorization: Bearer $TELEGRAM_AUTO_API_KEY" \
-H "Content-Type: application/json" \
-d '{"conversationId":"00000000-0000-0000-0000-000000000000"}'Output fields (data)
| Field | Type | Required |
|---|---|---|
ok |
true |
Yes |
ready |
false |
Yes |
reason |
"calls_disabled" | "not_private_chat" | "account_unavailable" | "proxy_no_udp" | "worker_outdated" | "peer_opted_out" | "account_busy" | "node_calls_full" | "audio_endpoint_required" | "call_not_found" | "forbidden" |
Yes |
message |
text |
Yes |
Example answer
{
"data": {
"ok": true,
"ready": false,
"reason": "calls_disabled",
"message": "text"
}
}Using it over MCP
Not listed on any profile: call tools_describe then tools_run with code: "calls.readiness". Tool name when listed: calls_readiness.