Guides

Each guide is one task from start to finish, with every step shown in Python, Node and Rust. Where an ecosystem has no equivalent, its tab says what to use instead. The concepts explain the ideas behind the steps; the reference for Python, Node and Rust lists every name they use.

tdata folders, session strings, .session files and auth keys are logged-in accounts. Work on copies, never share them and keep them out of logs, issues and commits.

Sessions from tdata

tdata to Telethon

A Telethon string session, or a .session file and its .json companion, from a Telegram Desktop folder.

Python · Node · Rust tdata to mtcute

An mtcute v3 string session, the Telegram Desktop initConnectionOptions and the crypto provider on the core.

Node · Python · Rust tdata to grammers

grammers 0.11 SessionData and connection params, then a live client with the client feature.

Rust

Pairs and the way back

Telethon .session + .json

Write and read the pair many tools store accounts in, and what every key of the companion holds.

Python · Node · Rust Client session to tdata

A new session by QR login with 2FA on a generated device, or the current session offline, saved as a tdata folder.

Python · Node · Rust

Fingerprints and checks

Validate a fingerprint

Build a profile, validate its initConnection parameters, read the issues, tz_offset, msg_id offsets and the transport.

Python · Node · Rust Consistency and sessions

Run the seven consistency checks on a live session, then list, print and terminate the account’s sessions.

Python · Node · Rust Live client versions

Fetch the current client and browser versions, apply a patch, or stay on the built-in set offline.

Python · Node · Rust Browser fingerprints

Headers and full fingerprints with options, screen constraints and seeds, handed to a browser automation tool as plain data.

Python · Node · Rust

Before you start

Install the package for your ecosystem: see Installation.
The examples load a folder called tdata next to the script. Copy the folder of a logged-in Telegram Desktop there; never point a script at the folder Telegram Desktop itself is using.
Python examples import opentele2, which fetches the current client versions once at import. Set OPENTELE_NO_FETCH=1 to stay offline; see Live client versions.