Hosted relay and queueing
TexMax holds the connection to your paired phone. If the phone is briefly offline, the message waits in the queue and is handed over when it reconnects, and the API response tells your app it was queued.
Pro 50% off your first year when you pay yearly, active through Dec 31, 2026.
See pricingAndroid SMS gateway · Built for your stack
Connect a paired Android phone and its SIM to the software you already use. Send texts through an API, then route replies back into your application.
Keep your dashboard. Add SMS underneath it.
Product
TexMax sits between your backend and a paired Android phone. Your application keeps control of its own screens, data and workflow. When it needs to send a text, it calls the TexMax API; when a reply comes in, TexMax hands it back.
There is nothing to migrate and no new interface your team has to learn. The phone does the sending over its own SIM, so messages come from a real mobile number rather than a rented virtual one.
Read the Android SMS gateway guideHow it works
TexMax runs the hosted relay between your software and the phone, so your app never talks to a handset directly.
Install the TexMax Android app and pair it with your account. That phone and its SIM become your SMS gateway.
Create an API key in your TexMax dashboard and add one HTTP request to your backend.
TexMax queues the message on the hosted relay and hands it to the paired phone, which sends it over its SIM.
Incoming texts return through TexMax to your application via the API or a webhook you configure.
Works behind your software
Anything that can make an HTTP request or receive a webhook can text through TexMax: a CRM, a booking system, a support desk, or the app you built yourself.
Laravel, Node, Python, PHP, React or WordPress: if it speaks HTTP, it works. Your users stay in your product and never see a TexMax screen.
Examples, not built-in integrations.
Developers
Authenticate with an API key, pick the paired device, and send. The same key works for templates and for reading replies.
POST /messages/send sends a text through a paired phonePOST /messages/send-template fills a saved template with your variablescurl -X POST https://api.texmax.app/messages/send \
-H "Authorization: Bearer tmx_your_api_key" \
-H "Content-Type: application/json" \
-d '{
"deviceId": "your_device_id",
"address": "+15551234567",
"body": "Your appointment is confirmed."
}'
Illustrative request. Replace the placeholders with your own key and device ID.
What's inside
TexMax holds the connection to your paired phone. If the phone is briefly offline, the message waits in the queue and is handed over when it reconnects, and the API response tells your app it was queued.
Inbound SMS received by the phone come back through TexMax. Read them with the API or have them pushed to your webhook to trigger your own workflow, such as confirming a booking or opening a ticket.
Save a template once and send it with different values each time. Your app passes the variables; TexMax fills them in.
Hi {{name}}, your appointment is confirmed for {{time}}.Two parts
Web
Create and manage API keys, connect your application, set up reply webhooks and templates, and see message history.
Open the dashboardAndroid
The paired Android phone sends and receives through its SIM's mobile network. No virtual number, and your existing mobile plan applies.
How the gateway worksPricing
Messages go out over your own SIM, so your mobile plan's terms and charges still apply.
€0
50% off yearly · through Dec 31, 2026
€15/month
or €90/year €180 when you pay yearly
Sign up free, then request Pro from the dashboard's billing tab.
Comparing costs? See TexMax vs Twilio and what Twilio actually costs.
Create a free account, pair your phone, and send your first message in minutes.
FAQ
No. TexMax adds SMS underneath the software you already use. Your application keeps its own screens and workflow and calls the TexMax API when it needs to send a text.
No. Messages go out through the SIM in your paired Android phone, so recipients see that phone's number. See how that compares to Twilio, Plivo and other SMS APIs.
Incoming SMS received by the paired phone are relayed back to TexMax. Your application can read them through the API or receive them on a webhook URL you configure.
A message sent while the phone is offline is queued and handed to the phone when it reconnects. The API response tells your application this happened, so it always knows the real status.
No. TexMax connects through a standard HTTP API and webhooks. Any software that can make an HTTP request or receive a webhook can use it, but there are no built-in plug-ins for specific CRMs or booking tools.
Make sure the phone has reliable power and connectivity, that your mobile plan and provider terms allow the volume and type of messages you plan to send, that the countries you text are supported by your carrier, and that your messages follow the rules that apply to you, such as consent and opt-out requirements.