定制 yabx/telegram 二次开发

按需修改功能、优化性能、对接业务系统,提供一站式技术支持

邮箱:yvsm@zunyunkeji.com | QQ:316430983 | 微信:yvsm316

yabx/telegram

Composer 安装命令:

composer require yabx/telegram

包简介

Telegram Bot API SDK for PHP 8.1+

README 文档

README

PHP SDK for the Telegram Bot API. Typed request/response objects, Guzzle HTTP client, and coverage aligned with Bot API 10.2 (July 2026).

Requirements

  • PHP >= 8.1
  • Extensions: json, curl
  • Composer dependencies: guzzlehttp/guzzle ^7.9, psr/log ^3.0

Installation

composer require yabx/telegram

Features

  • Strongly typed Yabx\Telegram\Objects\* models for available types
  • One method per Bot API method on Yabx\Telegram\BotApi, matching available methods
  • request() for direct API calls when you need maximum flexibility
  • Optional PSR-3 logging and custom Guzzle / base URL for tests or proxies
  • Webhook parsing from raw JSON or php://input
  • getUpdates long polling support

Quick start

use Yabx\Telegram\BotApi;

$token = getenv('TELEGRAM_BOT_TOKEN');
$bot = new BotApi($token);

$me = $bot->getMe();
$chatId = 123456789; // Telegram user/group/channel id from an allowed update context
$sent = $bot->sendMessage($chatId, 'Bot is up. Connected as @' . ($me->getUsername() ?? 'bot'));

Client options

use GuzzleHttp\RequestOptions;
use Psr\Log\LoggerInterface;
use Yabx\Telegram\BotApi;

/** @var LoggerInterface $logger e.g. Monolog, Symfony Bridge, … */
$bot = new BotApi(
    $token,
    [
        RequestOptions::TIMEOUT => 30,
        RequestOptions::VERIFY => true,
    ],
    $logger,
    'https://api.telegram.org', // optional custom API host
);

Send messages (text, parse mode, reply)

use Yabx\Telegram\Objects\ReplyParameters;

$bot->sendMessage(
    chatId: $chatId,
    text: 'Hello, <b>world</b>',
    parseMode: 'HTML',
);

$bot->sendMessage(
    chatId: $chatId,
    text: 'Replying…',
    replyParameters: new ReplyParameters(messageId: $originalMessageId),
);

Inline keyboard

use Yabx\Telegram\Objects\InlineKeyboardButton;
use Yabx\Telegram\Objects\InlineKeyboardMarkup;

$keyboard = new InlineKeyboardMarkup([
    [
        new InlineKeyboardButton('Docs', url: 'https://core.telegram.org/bots/api'),
        new InlineKeyboardButton('Tap me', callbackData: 'demo:1'),
    ],
]);

$bot->sendMessage($chatId, 'Pick an action:', replyMarkup: $keyboard);

Reply keyboard (custom keyboard)

use Yabx\Telegram\Objects\KeyboardButton;
use Yabx\Telegram\Objects\ReplyKeyboardMarkup;

$markup = new ReplyKeyboardMarkup(
    keyboard: [
        [new KeyboardButton('Yes'), new KeyboardButton('No')],
        [new KeyboardButton('Cancel')],
    ],
    resizeKeyboard: true,
    oneTimeKeyboard: true,
);

$bot->sendMessage($chatId, 'Your choice?', replyMarkup: $markup);

Photo from disk (multipart upload)

If the path exists on disk, the client opens the file and sends it as multipart automatically:

$bot->sendPhoto(
    chatId: $chatId,
    photo: '/tmp/snapshot.jpg',
    caption: 'Snapshot',
    parseMode: 'HTML',
);

Webhooks

Register and inspect the webhook:

$bot->setWebhook(
    url: 'https://example.com/telegram/webhook',
    allowedUpdates: ['message', 'callback_query'],
    secretToken: getenv('WEBHOOK_SECRET'),
);

$info = $bot->getWebhookInfo();

Handle an incoming POST body (typical PHP endpoint):

use Yabx\Telegram\BotApi;

// Reads php://input and builds an Update (throws if body is empty / invalid JSON)
$update = BotApi::getUpdateFromRequest();

// Or parse a string you already have:
$update = BotApi::getUpdateFromJson($requestBody);

Then branch on the update payload:

if ($message = $update->getMessage()) {
    $chatId = $message->getChat()->getId();
    $text = $message->getText();
    $photos = $message->getPhotos();
    $video = $message->getVideo();
    $document = $message->getDocument();
    // … same pattern for stickers, polls, forwarded messages, etc.
}

if ($callback = $update->getCallbackQuery()) {
    $bot->answerCallbackQuery($callback->getId(), text: 'OK');
}

Long polling (getUpdates)

$offset = 0;

while (true) {
    $updates = $bot->getUpdates(offset: $offset, timeout: 50);

    foreach ($updates as $update) {
        $offset = $update->getUpdateId() + 1;

        if ($msg = $update->getMessage()) {
            $bot->sendMessage($msg->getChat()->getId(), 'Echo: ' . ($msg->getText() ?? ''));
        }
    }
}

Low-level request()

Useful for new API parameters before a dedicated method exists, or rare calls:

$result = $bot->request('getChat', ['chat_id' => $chatId]);

Objects with a toArray() method are normalized automatically. Upload methods on BotApi already set multipart where needed.

Last raw API response

After each call, the decoded JSON envelope (including ok, result, description, etc.) is available:

$bot->sendMessage($chatId, 'Hi');
$envelope = $bot->getLastResponse();

Error handling

Failed Bot API responses throw Yabx\Telegram\Exception with Telegram’s error_code as the exception code when present:

use Yabx\Telegram\Exception as TelegramApiException;

try {
    $bot->sendMessage($chatId, 'Ping');
} catch (TelegramApiException $e) {
    // $e->getCode() often matches Telegram's error_code
    error_log($e->getMessage());
}

Project layout

Path Role
src/BotApi.php Client: all Bot API methods + request()
src/Objects/ Telegram types (Message, Update, keyboards, …)
src/Enum/ Helpers such as ChatAction, etc.
tests/ PHPUnit test suite and JSON fixtures

Testing

composer install
composer test

Optional coverage report (requires the PCOV extension locally):

# Ubuntu/Debian — match your PHP version (php -v)
sudo apt install php8.3-pcov   # or php8.5-pcov, php8.2-pcov, …

composer test:coverage

HTML report in build/coverage/:

composer test:coverage-html

If PCOV is not installed, composer test:coverage prints installation hints instead of a cryptic PHPUnit error. CI collects coverage with PCOV on PHP 8.3 (job coverage in .github/workflows/tests.yml).

Tests use PHPUnit 10.5+ (PHP 8.1) or 11+ (PHP 8.2+) with Guzzle MockHandler for HTTP integration tests. Fixtures live in tests/Fixtures/.

Coverage phases

Phase Scope Status
1 Infrastructure, Utils, BotApi, core objects done
2 All RichText / RichBlock types, update variants done
3 Polymorphic dispatchers (ChatMember, MessageOrigin, …) done
4 Round-trip manifest (tests/Fixtures/roundtrip/) done — 331 leaf classes (~93%); dispatchers tested separately
5 Composite variant tests (ChatFullInfo, Message, ExternalReplyInfo) done
6 All Update webhook variants done — 22 fixtures
7 BotApi integration (request serialization, response parsing) done — 57 tests
8 Composite variants (Message quote/forward, ExternalReplyInfo media) done
9 API response snapshots (tests/Fixtures/api_responses/) done — 7 fixtures
10 Shared MocksBotApi trait, multipart uploads, forum topic variants done
11 Media send methods, payments, ChatFullInfo private, service messages done
12 Location/contact/video note, stars, migration/members, getUpdatefromRequest done
13 Paid media, batch delete/copy, ChatBoostSource dispatcher, chat service messages done
14 Chat actions, reactions, join requests, sticker set snapshot, chat event messages done
15 Live location, menu button, custom emoji, invite link snapshot, Update round-trip done
16 Live photo, forum topics, games, restrict member, service message variants done — 79 BotApi tests, 13 snapshots
17 Chat admin, forum/general topics, stickers, bot profile/commands, join-query done — 113 BotApi tests, ~69% BotApi.php lines
18 Business, stories, gifts/stars, payments, verification, managed bot, downloadFile done — 127 BotApi tests, ~99% BotApi.php lines
19 Deep Message / ChatFullInfo / Update variants done — 42 message fixtures, Message ~67% lines
20 BotApi edge cases: multipart, downloadFile, logging, transport errors done — BotApiEdgeCasesTest
21 API snapshots: business, gifts, boosts, invoice, extended chat done — 18 snapshots
22 Polymorphic dispatch + sendPoll / InputPollMedia contract done
23 PHPStan level 2, coverage threshold 57%, CI static analysis done — composer phpstan
24 CHANGELOG.md, README examples for Bot API 10.2 features done

InputPollMedia / InputPollOptionMedia are PHP interfaces; implementing classes (InputMediaPhoto, InputMediaLink, …) are covered in the round-trip manifest and via sendPoll contract tests.

Static analysis and coverage gate

composer phpstan          # PHPStan level 2 on src/
composer test:coverage    # fails if line coverage drops below 57%

Bot API 10.2 examples

Ephemeral messages

$bot->sendMessage($chatId, 'Only you can see this', receiverUserId: $userId, callbackQueryId: $queryId);
$bot->editEphemeralMessageText($chatId, $userId, $ephemeralMessageId, 'Updated');
$bot->deleteEphemeralMessage($chatId, $userId, $ephemeralMessageId);

Rich message blocks

use Yabx\Telegram\Objects\InputRichBlockParagraph;
use Yabx\Telegram\Objects\InputRichMessage;

$bot->sendRichMessage($chatId, new InputRichMessage(
    blocks: [new InputRichBlockParagraph(text: 'Hello')],
));

Bot API 10.1 examples

Business connection

$connection = $bot->getBusinessConnection('bc-1');
$bot->readBusinessMessage('bc-1', $chatId, $messageId);

Stories (managed business account)

use Yabx\Telegram\Objects\InputStoryContentPhoto;

$bot->postStory(
    businessConnectionId: 'bc-1',
    content: new InputStoryContentPhoto(type: 'photo', photo: '/tmp/story.jpg'),
    activePeriod: 86400,
    caption: 'News',
);

Gifts and Stars

$gifts = $bot->getAvailableGifts();
$bot->sendGift($userId, 'gift-id', text: 'Enjoy!');
$balance = $bot->getMyStarBalance();

Rich messages

use Yabx\Telegram\Objects\InputRichMessage;

$bot->sendRichMessage($chatId, new InputRichMessage(html: '<b>Hello</b>'));

To add coverage for a new object, append an entry to the appropriate file under tests/Fixtures/roundtrip/ (merged by roundtrip.php):

SomeObject::class => ['field' => 'value'],

License

MIT (see composer.json).

See also

yabx/telegram 适用场景与选型建议

yabx/telegram 是一款 基于 PHP 开发的 Composer 扩展包,目前已累计 3.11k 次下载、GitHub Stars 达 1, 最近一次更新时间为 2023 年 03 月 28 日, 在 PHP 生态内属于活跃度较高的组件。

它主要适用于以下技术方向: 「api」 「sdk」 「bot」 「telegram」 「telegram bot」 「telegram bot api」 等业务场景。在实际项目中,围绕这些方向常见需要落地的问题包括:接口对接、性能调优、并发安全、与既有框架(Laravel / ThinkPHP / Yii / Webman 等)的兼容适配,以及生产环境的日志埋点与稳定性保障。

我们在过去多个企业项目中使用过 yabx/telegram 或与其功能相近的方案,如果你在选型或落地过程中遇到问题,例如 版本兼容、二次改造、私有化封装、与内部系统对接、生产 BUG 排查,欢迎联系我们协助评估。

围绕 yabx/telegram 我们能提供哪些服务?
定制开发 / 二次开发

基于 yabx/telegram 在你已有业务上做功能扩展、字段裁剪、UI 适配、与内部账号 / 权限 / 日志系统的深度对接。

BUG 修复 & 性能优化

线上偶发问题、内存泄漏、慢查询、并发异常等排查修复;针对高流量场景做缓存、队列、索引层面的调优。

项目外包 & 长期维护

承接完整的项目从需求 → 设计 → 开发 → 上线 → 长期运维;也可按月提供技术保姆服务。

yvsm@zunyunkeji.com QQ:316430983 微信:yvsm316 西安尊云信息科技 · 专注 PHP / Go / 分布式系统研发

统计信息

  • 总下载量: 3.11k
  • 月度下载量: 0
  • 日度下载量: 0
  • 收藏数: 2
  • 点击次数: 0
  • 依赖项目数: 1
  • 推荐数: 0

GitHub 信息

  • Stars: 1
  • Watchers: 1
  • Forks: 0
  • 开发语言: PHP

其他信息

  • 授权协议: MIT
  • 更新时间: 2023-03-28