Key Takeaways
- Laravel talks HTTPS JSON to the control plane. The paired Android SIM still submits the PDU.
- There is no official Laravel / Composer SMS SDK from us. Http::withToken, queues, and live fields in Developer Center.
- Do not SMS inside the request. Dispatch after DB commit with an idempotency key.
- 201 is queued, not inbox. Persist the message id; watch DLR.
- Priced by devices and SMS send volume. You use your own phone and operator SMS credit. Free’s 300 SMS lifetime is a canary, not a campaign.
Laravel sends JSON, not GSM
Sending SMS from Laravel through an Android SMS gateway API is still your SIM on the last mile. Developer Center. SMS API documentation. Laravel HTTP client.
If OrderController waits on GSM, a sleepy OEM battery becomes a checkout 504.Controller vs queue vs radio
| Layer | Does | Must not |
|---|---|---|
| Controller / listener | Commit, dispatch | Block on the radio |
| Job | POST JSON, retry 5xx with backoff | Retry 4xx validation forever |
| Control plane | Queue to paired device | Invent carrier credit |
| Android SIM | Submit PDU | Share OTP with Friday CSVs |
Http facade, not a Laravel SDK
Same rule as PHP samples: copy the HTTPS shape. Device setup. Django order alerts if you want the same event model in another stack.
Queue after commit
- Put Bearer and deviceIds in env. Never commit the token. Confirm live JSON in Developer Center.
- Commit, then dispatch a job. Idempotency: order_id or user_id + template. Queue workers must be running.
- POST HTTPS with timeouts. Typical shape POST /api/v1/messages. Field names are live-owned, not this article.
- Store the message id. Support cannot debug “it didn’t arrive” from a 201 alone.
- Staff canary before customers. Real Laravel path, staff MSISDN, reboot the phone, then OTP.
- Isolate OTP deviceId. CSV campaigns must not sit in front of 2FA. Dual SIM is not isolation.
Delivery reports. Webhooks on paid plans. Laravel troubleshooting.
Keep login codes off promo
OTP verification. Multi-device. Dual SIM ≠ two queues.
Retries still spend pulsa
Service pricing is based on device count and total SMS sent through the gateway. You need a working Android phone with a SIM and SMS credit from your mobile operator. Operator message costs are yours—we do not sell carrier SMS balance. Paid from $19/month. Device and SMS volume pricing.
Next steps
Env, job, idempotency, staff DLR, OTP isolated. Then stop composer require a gateway SDK we do not publish.
Related product pages
Jump to the live product docs for this topic—not another long-form article.
- SMS API documentationLive endpoint reference
- PHP REST send samplesPHP code examples
- device and SMS volume pricingPlans and allowances
- Android SMS gateway product guideDefinition, product, and how to buy
