expertsystemsau/transmitsms-php-client
Composer 安装命令:
composer require expertsystemsau/transmitsms-php-client
包简介
Framework-agnostic PHP client for the TransmitSMS API
README 文档
README
A framework-agnostic PHP client for the TransmitSMS API.
Installation
composer require expertsystemsau/transmitsms-php-client
Usage
The client is resource-based. SMS operations live on $client->sms(), account
operations on $client->account(), reporting on $client->reporting(), and
contact lists on $client->lists().
use ExpertSystems\TransmitSms\TransmitSmsClient; use ExpertSystems\TransmitSms\Requests\SendSmsRequest; $client = new TransmitSmsClient('your-api-key', 'your-api-secret'); // Send an SMS — send(string $message, string $to, ?string $from = null, ?callable $configure = null) $sms = $client->sms()->send('Hello from TransmitSMS!', '+61400000000'); $messageId = $sms->messageId; // Send to multiple recipients (comma-separated, up to 500) $client->sms()->send('Bulk message', '+61400000000,+61400000001'); // Extra options (replies-to-email, callbacks, scheduling, validity) — pass a // configure closure. Connector defaults still apply, unlike sendRequest(). $client->sms()->send('Hello!', '+61400000000', configure: fn (SendSmsRequest $r) => $r->repliesToEmail('inbox@example.com')->validity(60) ); // Full control with no connector defaults applied — build a request yourself $request = (new SendSmsRequest('Scheduled message')) ->to('+61400000000') ->from('MySenderID') ->scheduledAt('2026-12-25 09:00:00'); $client->sms()->sendRequest($request); // Check a message's status / delivery stats $message = $client->reporting()->getMessage($messageId); $stats = $client->reporting()->getStats($messageId); // Get account balance $balance = $client->account()->getBalance(); // Get SMS replies (responses) $replies = $client->sms()->getAllResponses(); // Manage contact lists $lists = $client->lists()->all(); $client->lists()->addContact(123, '+61400000000', firstName: 'John');
Pagination
List endpoints (numbers()->all(), lists()->all(), keywords()->all(),
reporting()->getSent(), reporting()->getUserSent(), lists()->getContacts(),
sms()->getResponses()/getAllResponses()) return a paginator that lazily walks
every page. Use items() to iterate individual records:
foreach ($client->numbers()->all()->items() as $number) { echo $number['number'].PHP_EOL; } // Or collect across pages, tuning page size and page count $members = $client->lists()->getContacts($listId) ->setPerPageLimit(100) ->setMaxPages(5) ->collect() ->all();
Each endpoint's response envelope uses a different item key (numbers, lists,
recipients, messages, members, responses, …); the paginator resolves the
correct key per request automatically.
Sender IDs
The from value (per-message, or the connector default via setDefaultFrom()) is the
sender ID recipients see. It can be:
- A dedicated virtual number (VMN) in international format, e.g.
61412345678— supports two-way messaging (recipients can reply). - An alphanumeric sender ID ("alpha tag") such as
MyBrand— max 11 characters, letters and digits only, no spaces (validate with$client->sms()->isValidSenderId()). One-way only; recipients cannot reply. - Omitted — TransmitSMS falls back to a shared number for the destination country.
There is no from argument on the constructor. Set it one of two ways:
$client = new TransmitSmsClient('your-api-key', 'your-api-secret'); // 1. Per message — the third argument to send() overrides any default. // send(string $message, string $to, ?string $from = null, ?callable $configure = null) $client->sms()->send('Hello!', '+61400000000', 'MyBrand'); // 2. A default sender ID applied to every send()/sendToList() call, set on // the connector. Optionally set a default country code used to normalise // local numbers before sending. $client->connector()->setDefaultFrom('MyBrand'); $client->connector()->setDefaultCountryCode('AU'); $client->sms()->send('Hello!', '+61400000000'); // uses "MyBrand" // Validate a value before you rely on it if (! $client->sms()->isValidSenderId('MyBrand')) { // reject / fall back to a shared number }
Note:
$client->sms()->sendRequest(SendSmsRequest $request)does not apply these connector defaults — setfromon the request yourself when using it.
⚠️ Alpha tags must be registered and approved before you can send with them. For messages to Australian numbers, alphanumeric sender IDs must be listed on the ACMA SMS Sender ID Register (enforced from 1 July 2026) — an unregistered sender ID is replaced with "Unverified" on the recipient's device. Registration requires your registered entity name, ABN, and an authorised contact. Register your sender IDs through the TransmitSMS dashboard before using an alpha tag; otherwise omit
fromto send from a shared number.
DLR & Reply Callbacks
The client provides utilities for handling DLR (Delivery Receipt) and Reply callbacks with signed URLs.
Setting Up Callback URLs
use ExpertSystems\TransmitSms\TransmitSmsConnector; use ExpertSystems\TransmitSms\TransmitSmsClient; use ExpertSystems\TransmitSms\Requests\SendSmsRequest; use ExpertSystems\TransmitSms\Callbacks\CallbackUrlBuilder; use ExpertSystems\TransmitSms\Callbacks\CallbackType; // Create connector and client $connector = new TransmitSmsConnector( apiKey: 'your-api-key', apiSecret: 'your-api-secret' ); $client = new TransmitSmsClient($connector); // Create URL builder with your webhook base URL and signing key $urlBuilder = new CallbackUrlBuilder( baseUrl: 'https://myapp.com/webhooks/sms', signingKey: 'your-secret-signing-key' ); // Send SMS with callbacks $request = (new SendSmsRequest('Your order has shipped!')) ->to('61400000000') ->from('MYSTORE') ->dlrCallback( $urlBuilder->build( type: CallbackType::DLR, handler: 'App\\Webhooks\\OrderDlrHandler', context: ['order_id' => 123] ) ) ->replyCallback( $urlBuilder->build( type: CallbackType::REPLY, handler: 'App\\Webhooks\\OrderReplyHandler', context: ['order_id' => 123] ) ); $result = $client->sms()->sendRequest($request);
Handling Incoming Callbacks
In your webhook endpoint, parse and verify the callback:
use ExpertSystems\TransmitSms\Callbacks\CallbackUrlParser; use ExpertSystems\TransmitSms\Data\DlrCallbackData; use ExpertSystems\TransmitSms\Data\ReplyCallbackData; use ExpertSystems\TransmitSms\Exceptions\InvalidSignatureException; $parser = new CallbackUrlParser('your-secret-signing-key'); try { // Parse and verify signature $parsed = $parser->parse($_GET); // Create DTO from callback data $dlr = DlrCallbackData::fromRequest($_GET); // Access handler and context $handlerClass = $parsed['handler']; // 'App\Webhooks\OrderDlrHandler' $context = $parsed['context']; // ['order_id' => 123] // Call your handler $handler = new $handlerClass(); $handler->handle($dlr, $context); http_response_code(200); echo 'OK'; } catch (InvalidSignatureException $e) { http_response_code(403); echo 'Invalid signature'; }
Callback Data DTOs
DlrCallbackData - Delivery receipt information:
$dlr = DlrCallbackData::fromRequest($data); $dlr->messageId; // int - The message ID $dlr->mobile; // string - Recipient phone number $dlr->status; // string - 'delivered', 'failed', 'pending' $dlr->datetime; // ?string - Delivery timestamp $dlr->errorCode; // ?string - Error code if failed $dlr->errorDescription; // ?string - Error description if failed $dlr->isDelivered(); // bool - Check if delivered $dlr->isFailed(); // bool - Check if failed $dlr->isPending(); // bool - Check if pending
ReplyCallbackData - Reply message information:
$reply = ReplyCallbackData::fromRequest($data); $reply->messageId; // int - Original message ID $reply->mobile; // string - Sender phone number $reply->message; // string - Reply message text $reply->receivedAt; // string - Timestamp when received $reply->responseId; // ?int - Reply ID $reply->longcode; // ?string - Number replied to
LinkHitCallbackData - Link click information:
$linkHit = LinkHitCallbackData::fromRequest($data); $linkHit->messageId; // int - Message ID $linkHit->mobile; // string - Recipient phone number $linkHit->url; // string - URL that was clicked $linkHit->clickedAt; // string - Click timestamp $linkHit->userAgent; // ?string - Browser user agent $linkHit->ipAddress; // ?string - IP address
Laravel Integration
For Laravel projects, use expertsystemsau/transmitsms-laravel which provides:
- Service provider with automatic configuration
- Facade for convenient access
- Notification channel integration
- Automatic webhook handling with job dispatching
- Event-driven callback processing
License
The MIT License (MIT). Please see License File for more information.
expertsystemsau/transmitsms-php-client 适用场景与选型建议
expertsystemsau/transmitsms-php-client 是一款 基于 PHP 开发的 Composer 扩展包,目前已累计 35 次下载、GitHub Stars 达 0, 最近一次更新时间为 2025 年 12 月 09 日, 在 PHP 生态内属于活跃度较高的组件。
它主要适用于以下技术方向: 「sms」 「API-Client」 「transmitsms」 「ExpertSystems」 等业务场景。在实际项目中,围绕这些方向常见需要落地的问题包括:接口对接、性能调优、并发安全、与既有框架(Laravel / ThinkPHP / Yii / Webman 等)的兼容适配,以及生产环境的日志埋点与稳定性保障。
我们在过去多个企业项目中使用过 expertsystemsau/transmitsms-php-client 或与其功能相近的方案,如果你在选型或落地过程中遇到问题,例如 版本兼容、二次改造、私有化封装、与内部系统对接、生产 BUG 排查,欢迎联系我们协助评估。
基于 expertsystemsau/transmitsms-php-client 在你已有业务上做功能扩展、字段裁剪、UI 适配、与内部账号 / 权限 / 日志系统的深度对接。
线上偶发问题、内存泄漏、慢查询、并发异常等排查修复;针对高流量场景做缓存、队列、索引层面的调优。
承接完整的项目从需求 → 设计 → 开发 → 上线 → 长期运维;也可按月提供技术保姆服务。
与 expertsystemsau/transmitsms-php-client 相关的其它包
同方向 / 同关键字的高下载量 PHP Composer 包推荐,方便对比选型:
Skolkovo API Client
SDK for payment gateway PlatbaMobilom.sk for PHP7.0
Extensible library for building notifications and sending them via different delivery channels.
yii2-sms expand
A client library for the OpenPLZ API project
统计信息
- 总下载量: 35
- 月度下载量: 0
- 日度下载量: 0
- 收藏数: 0
- 点击次数: 7
- 依赖项目数: 1
- 推荐数: 0
其他信息
- 授权协议: MIT
- 更新时间: 2025-12-09