Download the PHP package expertsystemsau/transmitsms-laravel-client without Composer
On this page you can find all versions of the php package expertsystemsau/transmitsms-laravel-client. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download expertsystemsau/transmitsms-laravel-client
More information about expertsystemsau/transmitsms-laravel-client
Files in expertsystemsau/transmitsms-laravel-client
Package transmitsms-laravel-client
Short Description Laravel notification channel and integration for the TransmitSMS API
License MIT
Homepage https://github.com/expertsystemsau/transmitsms-laravel-client
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package transmitsms-laravel-client
TransmitSMS Laravel Integration
Laravel notification channel and integration for the TransmitSMS API.
Installation
Publish the configuration file:
Configuration
Add your credentials to your .env file:
Sender IDs
TRANSMITSMS_FROM (or the per-message from() / from option) 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. One-way only; recipients cannot reply. - Omitted (leave empty) — TransmitSMS falls back to a shared number for the destination country.
⚠️ 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 setting
TRANSMITSMS_FROM; until then, leave it empty to send from a shared number.
Usage
Facade
The facade proxies to the resource-based client: SMS operations live on sms(),
account operations on account(), reporting on reporting(), and so on.
Notifications
Create a notification that uses the TransmitSMS channel:
Add the routeNotificationForTransmitsms method to your notifiable model:
Then send notifications:
Message options
TransmitSmsMessage is a fluent builder covering every send option:
To send to a TransmitSMS contact list instead of the notifiable's number, use
toList() — the resolved recipient is then ignored:
DLR & Reply Callbacks
The package provides automatic handling for DLR (Delivery Receipt), Reply, and Link Hit callbacks. When you send an SMS, you can specify a job to be dispatched when a callback is received.
Quick Start
Creating Handler Jobs
DLR Handler Job:
Reply Handler Job:
Link Hit Handler Job:
Global Event Listeners
In addition to per-message handlers, you can listen to events for all callbacks:
Example listener:
Webhook Configuration
The webhook routes are automatically registered. You can customize them in config/transmitsms.php:
Callback Data Objects
DlrCallbackData properties:
| Property | Type | Description |
|---|---|---|
messageId |
int |
The message ID |
mobile |
string |
Recipient phone number |
status |
string |
Status: delivered, failed, pending |
datetime |
?string |
Delivery timestamp |
senderId |
?string |
Sender ID used |
errorCode |
?string |
Error code if failed |
errorDescription |
?string |
Error description |
Helper methods: isDelivered(), isFailed(), isPending()
ReplyCallbackData properties:
| Property | Type | Description |
|---|---|---|
messageId |
int |
Original message ID |
mobile |
string |
Sender phone number |
message |
string |
Reply message text |
receivedAt |
string |
Timestamp when received |
responseId |
?int |
Reply ID |
longcode |
?string |
Number replied to |
firstName |
?string |
Sender first name |
lastName |
?string |
Sender last name |
LinkHitCallbackData properties:
| Property | Type | Description |
|---|---|---|
messageId |
int |
Message ID |
mobile |
string |
Recipient phone number |
url |
string |
URL that was clicked |
clickedAt |
string |
Click timestamp |
userAgent |
?string |
Browser user agent |
ipAddress |
?string |
IP address |
How It Works
-
Sending: When you use
onDlr(),onReply(), oronLinkHit(), the package builds a signed callback URL containing your handler class and context data. -
Receiving: When TransmitSMS calls the webhook, the package:
- Verifies the HMAC signature
- Parses the callback data into a DTO
- Dispatches a global event (for logging/monitoring)
- Dispatches your handler job with the data and context
- Security: The callback URL includes an HMAC signature to prevent tampering. Only callbacks with valid signatures are processed.
License
The MIT License (MIT). Please see License File for more information.
All versions of transmitsms-laravel-client with dependencies
expertsystemsau/transmitsms-php-client Version ^1.0
illuminate/notifications Version ^11.0||^12.0
illuminate/support Version ^11.0||^12.0
saloonphp/laravel-plugin Version ^4.0