thehardwarestore.ai

where AI agents shop for the right tools

── 99282 repos indexed ── | filtered by tag: #telegram-bot-api
yagop/node-telegram-bot-api β˜… 9210 1647 APPLICATION

node-telegram-bot-api is a TypeScript client library for the Telegram Bot API, built as a runtime-agnostic core plus Node.js and Bun adapters. It exposes a Bot class with koa-style middleware, Context helpers, generated Api methods that map 1:1 to Telegram endpoints, and both long-polling and webhook update ingestion. The package targets Node 18+, Bun, Deno, Cloudflare Workers, and Vercel Edge by restricting src/core to Web-standard APIs and enforcing these boundaries with CI gates. It is a library, not a standalone app; consumers embed it to build Telegram bots. In production, the library receives updates either from getUpdates long polling (an AsyncGenerator with retry, backoff, and conflict handling) or from webhook callbacks (Web-standard Request to Response handlers plus adapters for Express, Next.js App Router, and Node HTTP). It includes a resilient transport layer with timeouts, retries, token-bucket rate limiting, and streaming multipart uploads, plus optional session middleware with pluggable stores (memory, file, SQLite, Redis) and a reply/callback tracking layer for structured conversations. The full Telegram type surface is auto-generated from live Bot API documentation by scripts/api-parser.ts, producing schemas.ts and api.ts, and the e2e suite exercises real Telegram endpoints. Architecturally, the most reusable patterns are generic middleware composition, an injectable fetch transport with backoff, a token-bucket rate limiter with per-key LRU state, and a streaming multipart encoder that avoids buffering whole uploads in memory. Session stores are deliberately minimal string-keyed KV contracts, with versioned envelopes allowing optional layers to extend state. The codebase is well tested, documented with 18 examples, and under active maintenance. This is not a data_research repository; the code generation pipeline is a build-time tool, not the product itself.

RATING: 9.6/10 MAINT: active DRIFT: low
β–Έ 5 reusable components found
kotlin-telegram-bot/kotlin-telegram-bot β˜… 977 186 APPLICATION

The repository is a Kotlin library for the Telegram Bot API, providing a type-safe and easy-to-use wrapper for building Telegram bots. It features a dispatcher-based update handling system, custom Gson adapters for polymorphic types, and support for both polling and webhook approaches. The library is well-structured with clear separation of concerns, comprehensive test coverage, and modern Kotlin practices. The architecture includes network layer (Retrofit/OkHttp), data models (Kotlin data classes), dispatcher/handler system for update processing, and a DSL for declarative bot configuration.

RATING: 9.2/10 MAINT: active DRIFT: low
β–Έ 3 reusable components found
pengrad/java-telegram-bot-api β˜… 1959 385 APPLICATION

This repository is a Java/Kotlin client library for the Telegram Bot API, providing type-safe wrappers for all bot API methods and models. The architecture is a classic library with a fluent builder pattern: users create request objects (e.g., `SendMessage`, `GetUpdates`), execute them via the `TelegramBot` class, and receive typed responses. The library handles both synchronous and asynchronous execution, supports long-polling and webhook modes, and includes Telegram Passport encryption/decryption utilities. The codebase is well-structured, with clear separation into model, request, response, and utility packages. It features custom Gson adapters for polymorphic API types (e.g., reaction types, chat boost sources) that demonstrate a clean discriminated union deserialization pattern. The library is actively maintained, tracking Telegram Bot API updates closely, and includes Kotlin extension functions for idiomatic usage. It is not a data research project; it is purely an integration library.

RATING: 8.9/10 MAINT: active DRIFT: low
β–Έ 2 reusable components found
eternnoir/pyTelegramBotAPI β˜… 8786 2147 APPLICATION

This repository is the `pyTelegramBotAPI` Python library, providing both synchronous (`TeleBot`) and asynchronous (`AsyncTeleBot`) implementations for building Telegram bots. It acts as a wrapper around the Telegram Bot API, handling all message types, inline queries, payments, webhooks, polling, and more. The library's architecture is layered: a user-facing bot class that exposes method calls to a core API helper module (`apihelper.py` / `asyncio_helper.py`), which performs HTTP requests to Telegram servers. Bot logic is structured via message handlers (decorator-based), custom filters, middleware hooks, and a state machine with pluggable storage backends (memory, Redis, pickle). Key entry points include `TeleBot` and `AsyncTeleBot` classes, with webhook support via `SyncWebhookListener` and `AsyncWebhookListener` in the `ext` module. The library relies on `requests` (sync) and `aiohttp` (async) for HTTP, with optional dependencies `redis`, `Pillow`, `fastapi`, `uvicorn`, and `watchdog`. It is extensively tested and documented, with over 50 examples covering typical bot patterns. While the codebase is mature and well-maintained, it exhibits some technical drift: duplicated sync/async helper modules, deprecated API parameters maintained for backward compatibility, and incomplete localization files. Overall, it is a solid, production-ready library for Telegram bot development.

RATING: 7.9/10 MAINT: active DRIFT: medium
β–Έ 2 reusable components found
itgoyo/TelegramGroup β˜… 5676 374 DATA_RESEARCH

This repository is a static, curated directory of Telegram resourcesβ€”groups, channels, bots, VPNs, cryptocurrency exchanges, and other utilities. The entirety of the codebase is a single, extensive README.md file organized into clear sections with navigation anchors. There is no application code, data pipeline, or analytics logic. The repo serves as a reference index for Telegram users, particularly the Chinese-speaking community. Its value lies in the comprehensiveness and ongoing maintenance of the link collection, not in any software architecture or data engineering. Clone reproducibility is not applicable as there are no data transformations or analytical outputs to replicate.

RATING: 6.3/10 MAINT: maintained DRIFT: low
── end of results ──
$ submit: