Developer documentation

Telegram voice, video and group calls

Separate signaling, media engines and encryption across one-to-one calls, livestreams and conferences.

GetTGAPI editorial teamUpdated
Documentation notesReviewed

Based on official sources and independently maintained by GetTGAPI. Documentation and glossary →

On this page
  1. Accepted signaling is not connected media
  2. Group calls have several modes
  3. Verify encryption alongside the media implementation
  4. Test recommendations

Accepted signaling is not connected media

One-to-one calls involve requesting, accepting, checking keys, confirming and ending the call, followed by media-engine handling. Multiple receiving devices must converge on the device that accepted.

Group calls have several modes

Video chats, channel livestreams and conferences have different contexts. Some playback switches to streaming; RTMP publishing is not equivalent to WebRTC. Recording and encryption properties depend on the mode, so do not make one blanket end-to-end-security claim for every group call.

Verify encryption alongside the media implementation

Official references provide separate one-to-one and group encryption specifications. Successful signaling alone does not prove key checks or media encryption. Match the media library, negotiated capabilities and protocol version.

Test recommendations

Exercise permission denial, camera switching, headset changes, interruptions, backgrounding and network changes. Retain sanitized state and latency diagnostics, not raw media or keys. Verify resource and session cleanup when the call ends.