API Reference

The reference is generated from three independently verified source surfaces and committed so changes remain reviewable. Use the language and kind filters in search to move between public Python APIs, native Rust internals exposed through the extension boundary, and the pinned Telegram layer.

Reference families

• Python API documents maintained modules, classes, methods, functions, attributes, and type aliases from static Griffe analysis. Explicitly exported aliases point back to their canonical pages.
• Rust API documents the maintained native crate from pinned-nightly rustdoc JSON and cargo-docs-md, including PyO3 binding names where applicable.
• Telegram raw API documents generated functions, types, RPC errors, result families, and constructor relationships from the pinned layer inputs without importing generated Python modules.

Reading generated pages

Every generated page identifies its language, reference kind, qualified name, and source provenance in frontmatter and searchable metadata. Python and Rust parameter descriptions come from maintained docstrings or doc comments. Telegram parameter and result descriptions come from the pinned schema and project-owned relationship manifest; they do not invent behavioral guarantees absent from Telegram’s definitions.

The checked-in reference manifest records page counts, routes, source paths, and content hashes. Run miniproto-docs --check to prove the committed reference still matches the source and pinned toolchain.