Interact with the 'Telegram' 'MTProto' API
Overview
Provides a full-featured client for the 'Telegram' 'MTProto' protocol (https://core.telegram.org/api), enabling programmatic access to 'Telegram' chats, channels, messages, media, and stories. Implements binary encoding and decoding of the 'Telegram' 'TL' (Type Language) schema, authentication (including two-factor), encrypted transport, and high-level helpers for downloading channel history and reactions at scale. Intended for social-science research and data collection tasks that require direct API access rather than the 'Bot API'.
- Removed unused sample video files from
inst/extdata, shrinking the source tarball to ~3.4Mb (under CRAN's 5Mb guideline). - Exported
TelegramClient, the high-level client class, soTelegramClient$new()works afterlibrary(telegramR)(its@exporthad been in a comment that roxygen ignored, leaving it inaccessible). - Synced the bundled 'Telegram' TL schema to layer 229 and regenerated all TL type and request classes, fixing dialog and message parsing against current 'Telegram' servers.
- Reworked the schema code-generation tooling in
data-raw/entirely in R (generate_tl.R,overwrite_stale.R,dedupe_types.R,emit_missing.R, and theregenerate.Rpipeline), replacing the previous scripts. The pipeline is idempotent and documents every generated class with roxygen.
Show all changes in 0.0.2Hide the rest of the changes in 0.0.2
- Fixed serialisation of 64-bit integers and byte fields, and the send-media chain.
- Fixed the asynchronous test helpers to resolve
promisesobjects, and a latent unqualifiedopenssl::rand_bytes()call in the obfuscated transport.
From NEWS.md in the release
Install
Health
- OK13 OKNow
- OK12 OK, 1 FAILURE2026-10-01
- NOTE11 OK, 2 NOTE2026-06-30
- ERROR11 OK, 1 NOTE, 1 ERROR2026-06-23
- NOTE11 OK, 2 NOTE2026-06-07
- ERROR5 OK, 1 NOTE, 1 ERROR2026-06-03
Documentation
- Help pages
- 32
- Examples that run
- 0%1 never run
- Exported functions with examples
- 3%
- Documented parameters
- 95%
- Return-value docs
- 100%
- Help pages citing references
- 0%
Downloads
Repository
- PRs merged (all time)
- 100%
- Median days to close, 50 most recently updated closed issues
- not measured
- Median days to close, 50 most recently updated closed PRs
- not measured
PRs over time
11 development-tooling and community-health practices detected across 7 families in the upstream repository
Checks run against github.com/romankyrychenko/telegramr on 2026-10-11.
The R CMD check workflow runs on Linux, macOS and Windows, and on R-devel
GitHub Pages site last deployed 2026-10-09 · The repository has a site deploy workflow
pkgdown site last built 2026-10-09
Show all practicesHide 3 practices
This repository shows signs of AI coding tools.
- Claude Codefirst seen on or before 2026-05-01Named in .Rbuildignore: .claudePull request it wrote: opened by a project memberCommits: 19 by its own account · at least 43 crediting it in the message
- GitHub Copilotfirst seen on or before 2026-05-05Commits: at least 22 crediting it in the message
- Claude Opus 5.519 commits · Oct 2026
- Claude Opus 4.815 commits · Sep 2026
- Claude Opus 4.79 commits · May 2026
Dependencies
Code & Tests
Datasets
People & History
Pick two releases to compare their code metrics.
- 0.0.2Latest
- 0.0.12026-06-02
- RR 4.6.0 released · 2026-04-24
Package metadata
- First published
- 2026-06-02
- Total releases
- 2 / 1 yrs
- License
- MIT + file LICENSE OSI
- Minimum R
- ≥ 3.5.0
- Download size
- 3.3 MB
Cite
Cite this package
Run in R for the authors' preferred citation:
citation("telegramR")The package provides a citation file that builds its entry when R runs it. Run citation() to see it.
The repository also keeps a CITATION.cff.
Cite the R Observatory
For a number measured here: a download total, a coverage figure, an archival date.
From data release v2026-10-18, which the citation names so these numbers can be found later. More on citing and the projects behind them.