teleproto.dev valid
teleproto
Telegram MTProto API client library written in TypeScript. Documentation for userbots, automation, sessions, events, and the raw TL surface.
- Authority
- 45 reach 0 · trust 5 · quality 25 · freshness 15
- Tier
- listed
- llms.txt
- https://docs.teleproto.dev/llms.txt
- llms-full.txt
- https://docs.teleproto.dev/llms-full.txt
- Sections
- 7
- Links
- 23
- Size
- 4967 bytes
- Country
- United States Hosting inference
- Hosting country
- United States Hosting inference
- Country evidence
- No published address evidence collected yet
- For agents
- Documentation: developer or product docs worth reading, nothing to call
- First seen
- 2026-10-27T10:03:09.583Z
- Last checked
- 2026-10-27T10:03:10.978Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-27T10:03:09.588Z. Cached copy · Source on teleproto.dev
# teleproto
> Telegram MTProto API client library written in TypeScript. Documentation for userbots, automation, sessions, events, and the raw TL surface.
teleproto is a Telegram MTProto API client library written in TypeScript for Node.js. It is ideologically inspired by GramJS and remains GramJS-compatible for most public API. Source: https://github.com/sanyok12345/teleproto. Package on npm: `teleproto` (current version 1.232.0, published 2026-10-22). Full API reference: https://ref.teleproto.dev.
## Getting Started
- [Introduction](https://docs.teleproto.dev/)
- [Installation](https://docs.teleproto.dev/installation)
- [Quick Start](https://docs.teleproto.dev/quick-start)
- [Authentication](https://docs.teleproto.dev/authentication)
- [Sessions](https://docs.teleproto.dev/sessions)
- [Migrating from GramJS](https://docs.teleproto.dev/migrating-from-gramjs)
- [FAQ](https://docs.teleproto.dev/faq)
## Concepts
- [Entities & Peers](https://docs.teleproto.dev/concepts/entities)
- [Updates & Events](https://docs.teleproto.dev/concepts/updates)
- [Errors & FloodWait](https://docs.teleproto.dev/concepts/errors)
- [Raw TL API](https://docs.teleproto.dev/concepts/raw-api)
- [Bot API vs MTProto](https://docs.teleproto.dev/concepts/bot-api-vs-mtproto)
## Guides
- [Messages](https://docs.teleproto.dev/guides/messages)
- [Media](https://docs.teleproto.dev/guides/media)
- [Chats & Channels](https://docs.teleproto.dev/guides/chats)
- [Events](https://docs.teleproto.dev/guides/events)
## Operations
- [Production](https://docs.teleproto.dev/production)
## Internals
- [Connection lifecycle](https://docs.teleproto.dev/internals/connection)
- [Auth keys & encryption](https://docs.teleproto.dev/internals/auth-keys)
- [Entity cache](https://docs.teleproto.dev/internals/entity-cache)
- [File transfer](https://docs.teleproto.dev/internals/file-transfer)
- [Update pipeline](https://docs.teleproto.dev/internals/updates)
## Reference
- [API Reference ↗](https://ref.teleproto.dev)
## Key facts for code generation
- Package name on npm: `teleproto` (current version 1.232.0). Server-side Node.js today (uses `node-localstorage`, `socks`); no browser/Deno/Bun build yet — browser support is a possible future direction.
- Install: `npm install teleproto`. Subpath imports: `teleproto`, `teleproto/sessions`, `teleproto/events`, `teleproto/errors`, `teleproto/tl`.
- Entry class: `TelegramClient` from `teleproto`. Constructor: `new TelegramClient(session, apiId, apiHash, params)`.
- Sessions: `StringSession`, `StoreSession`, `MemorySession` from `teleproto/sessions`. Use `new StringSession("")` for fresh login.
- Auth: `await client.start({ phoneNumber, phoneCode, password?, onError })` for users, `await client.start({ botAuthToken })` for bots.
- Events: `client.addEventHandler(callback, new NewMessage({...}))`. Builders from `teleproto/events`: NewMessage, EditedMessage, DeletedMessage, CallbackQuery, InlineQuery, Album, ChatAction, MessageRead, UserUpdate, Raw.
-
…Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| telegram.org | Telegram Core | interface APIs and SDKs Communications | — | 72 | ✓ | ||
| talkjs.com | TalkJS | interface APIs and SDKs Communications +1 | — | 60 | ✓ | ✓ | |
| wasenderapi.com | WasenderApi | interface Communications APIs and SDKs | — | 50 | ✓ | ||
| chat-sdk.dev | Chat SDK Documentation | documentation Developer tools APIs and SDKs +1 | US | 48 | ✓ | ✓ | |
| zapo.to | Zapo | documentation APIs and SDKs | — | 46 | ✓ | ✓ | |
| teletonagent.dev | Teleton Plugin SDK | interface Developer tools APIs and SDKs +1 | DE | 45 | ✓ | ✓ | |
| mtproto.cloud | mtproto.cloud | documentation Infrastructure | — | 48 | ✓ | ||
| tganalytics.xyz | Telegram Mini Apps Analytics SDK | interface APIs and SDKs Data and analytics +1 | — | 52 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=teleproto.dev · GET /v1/domain/teleproto.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage teleproto.dev, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for teleproto.dev:
1. POST https://agentwebmap.com/v1/sites/teleproto.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://teleproto.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/teleproto.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/teleproto.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.