Your developers want an API. Support wants a console. Marketing runs campaigns, ops sends reminders. SMS365 gives each team the way they already know — over one gateway, one bill, and one set of rules.
Plans from $10/mo + 10c a message · Australian, carrier-direct
# Send an SMS in three lines curl -X POST https://app.sms365.com.au/v1/messages \ -H "Authorization: Bearer sk_live_…" \ -H "Content-Type: application/json" \ -d '{"to":"0412345678","body":"Your order is on its way."}'
await fetch("https://app.sms365.com.au/v1/messages", { method: "POST", headers: { Authorization: `Bearer ${process.env.SMS365_KEY}`, "Content-Type": "application/json", }, body: JSON.stringify({ to: "0412345678", body: "Your order is on its way." }), });
import requests requests.post( "https://app.sms365.com.au/v1/messages", headers={"Authorization": f"Bearer {KEY}"}, json={"to": "0412345678", "body": "Your order is on its way."}, )
$ch = curl_init("https://app.sms365.com.au/v1/messages"); curl_setopt_array($ch, [ CURLOPT_POST => true, CURLOPT_HTTPHEADER => ["Authorization: Bearer $key", "Content-Type: application/json"], CURLOPT_POSTFIELDS => json_encode(["to" => "0412345678", "body" => "Your order is on its way."]), ]); curl_exec($ch);
Your teams don't send SMS the same way — so SMS365 meets each where they are. Every path runs through the same gateway, so opt-out, suppression, sender rules and spend caps apply to all of it, on one bill.
A REST API that reads like the docs — send in three lines, scoped keys, idempotency, HMAC-signed events and an OpenAPI spec. Integrate in an afternoon.
A clean console to type and send, look up a contact, and see every message's history. No code, no training.
Import a list, personalise from each contact, send a campaign of any size, and measure the clicks — with opt-out enforced for you.
Appointment reminders that count down to a visit, trigger URLs, and email-to-SMS so any system that can send an email can send a text.
One-time codes for sign-ins and checkouts — rate-limited, expiring, attempt-capped, and never stored in the clear.
Give each client their own workspace, set your own price, and see revenue and margin per account. Sell SMS under your brand.
However a message enters — API, webhook, email, a link, or the console — it flows through the same pipeline. So the opt-out check, the suppression list, sender authorisation and the spend cap can never be skipped by a door someone added later.
Pick a plan, bring every team onto one gateway, and send your first message today.
See plans →