voice-control
voice-control

Get Resumable Call

Was this thread's call moved to the operator's own Telegram client?

Telegram allows one session per user per call, so answering on a phone evicts our leg. The call itself keeps running, and the operator would otherwise have to hunt down the original t.me/call link to get it back into the inbox.

We do NOT require metadata.end_reason='moved_to_device'. That tag is only set when a detector positively identified the eviction, and on real sessions it is usually absent (checked against the live DB 2026-08-06: every recent completed session had an empty end_reason) — gating on it meant the chip essentially never appeared. Any recently ended call with a Telegram identity and no live session is offered back; if it is really over, /calls/resume fails loudly.

The window is 12 hours, not minutes: a call left running on a phone routinely outlives any short window, and the operator asked for the way back to stay visible. If the call did end meanwhile, /calls/resume fails loudly and the chip clears — better than hiding the only route back into a call that is still running.

get/api/voice/threads/resumable-call

Request

  • Base URL: https://api.dialogbrain.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.dialogbrain.com/api/voice/threads/resumable-call
  • Auth: none declared

Query parameters

channel_refstring required

thread.channel_ref

Response

Successful Response

call_idstring nullable
tg_call_idstring nullable
ended_atstring nullable
call_linkstring nullable
end_reasonstring nullable

Changes

No recorded changes to this operation across all 5 revisions of this API.