SMS Broadcast

SMS Broadcast — The cheapest credible Australian bulk SMS API, with a deliberately minimal interface. SMS Broadcast competes on one axis: price per message to Australian mobiles, published openly and among the lowest on this roster. The API is a single form-encoded HTTP call with no SDK, which is a feature rather than a limitation for a service this narrow. There is no multichannel story, no enterprise console and little in the way of platform features — for a cheap, reliable one-way notification pipe, that is precisely the point. Built by SMS Broadcast Pty Ltd.

We track it in 1 comparison — AU SMS APIs — so every claim below is a cell in a table you can open and check rather than an impression. Across those rosters it sits against 12 other tools, and what follows is where it visibly separates from them.

Where it wins.

• Price /SMS @ 10k — A$0.032 /SMS, the best figure of the 8 here.
• Price /SMS @ 100k — A$0.024 /SMS, the best figure of the 8 here.
• Price /SMS @ 1k — A$0.038 /SMS, the best figure of the 9 here.

Each of those is ranked against the whole roster on its category page, not against a hand-picked subset, so a first place here means first of everything we list.

Where it gives ground.

• MMS to AU — No. MessageMedia records Yes.
• RCS — No. Sinch records Yes.
• SDK languages — curl-only, 11th of 12. Twilio records node, python, php, ruby, java, dotnet, go.
• API style — rest-form, 12th of 13. SMSGlobal records rest-json-plus-smpp.

None of these disqualify it on their own. They are the fields to check against your own requirements before you commit, because they are the ones where a competitor genuinely does better.

Provenance. 21 of 26 tracked fields carry a value for SMS Broadcast, and 0 of those cite a document you can open. Nothing here carries a verification date yet, which is itself a reason to check before committing. Every figure keeps its own provenance — measured by us, claimed by the vendor, inferred, or community-reported — and we would rather print a dash than a guess.

Its nearest neighbour in our data is AWS End User Messaging. SMS Broadcast is ahead on Price /SMS @ 100k (A$0.024 /SMS against A$0.07 /SMS) and Price /SMS @ 10k (A$0.032 /SMS against A$0.07 /SMS). AWS End User Messaging takes SDK languages (node, python, php, ruby, java, dotnet, go against curl-only) and MCP server (Partial against No). That pattern repeats across the rest of the roster — see SMS Broadcast alternatives for the other rivals, each compared the same way.

Company

SMS Broadcast Pty Ltd

Fields we track

21 of 26

The price leader, and the integration is a single HTTP call you can write from memory. What you give up is platform: no meaningful console, thin delivery-receipt detail, and opt-out suppression you own yourself. For notification traffic at volume that trade is usually correct.

Price /SMS @ 10k

A$0.032 /SMS1st of 8

Inferred

Price /SMS @ 100k

A$0.024 /SMS1st of 8

Inferred

MMS to AU

○No9th of 12

Inferred

RCS

○No9th of 10

Inferred

Price /SMS @ 1k

A$0.038 /SMS1st of 9

Inferred

SDK languages

curl-only11th of 12

Inferred

Self-serve API key

●Yes1st of 13

Inferred

Carrier route

au-aggregator7th of 13

Inferred

SMS Broadcast is the right call in these situations, each one drawn from a field we actually record:

• High-volume one-way alerts where per-message cost dominates.
• Teams that would rather write the HTTP call than adopt an SDK.
• Backup or overflow routing behind a more featureful primary.
• Price /SMS @ 10k is your binding constraint. SMS Broadcast records A$0.032 /SMS, the best figure in the AU SMS APIs roster. We define that field as list price in AUD per outbound SMS segment to an Australian mobile at roughly 10,000 messages/month — the tier most SaaS products actually sit at.
• Price /SMS @ 100k is your binding constraint. SMS Broadcast records A$0.024 /SMS, the best figure in the AU SMS APIs roster. We define that field as list price in AUD per outbound SMS segment at roughly 100,000 messages/month.
• Price /SMS @ 1k is your binding constraint. SMS Broadcast records A$0.038 /SMS, the best figure in the AU SMS APIs roster.

Reach for something else when any of the following is a requirement rather than a nice-to-have:

• MMS to AU. SMS Broadcast records No on the AU SMS APIs table. MessageMedia records Yes on the same field. If that is a hard requirement rather than a preference, start elsewhere.
• RCS. SMS Broadcast records No on the AU SMS APIs table. Sinch records Yes on the same field. If that is a hard requirement rather than a preference, start elsewhere.
• SDK languages. SMS Broadcast records curl-only, 11th of 12 in the AU SMS APIs roster. Twilio records node, python, php, ruby, java, dotnet, go on the same field. If that is a hard requirement rather than a preference, start elsewhere.
• API style. SMS Broadcast records rest-form, 12th of 13 in the AU SMS APIs roster. SMSGlobal records rest-json-plus-smpp on the same field. If that is a hard requirement rather than a preference, start elsewhere.
• Delivery receipts. SMS Broadcast records Partial on the AU SMS APIs table. Twilio records Yes on the same field. If that is a hard requirement rather than a preference, start elsewhere.

We publish this block because a comparison that only lists what a tool is good at is marketing. Every figure above sits on the same page as its source, and the field definitions are on the category tables if you want to check how we measured them.

What we don't know. 5 of the 26 fields we track for SMS Broadcast are still blank: Dedicated number, Min top-up, Public status page, ACMA Sender ID and Operating since. Those render as dashes rather than as zeroes or assumptions, because an empty cell and a bad cell are not the same thing and only one of them is honest. If you know any of these figures and can point at a document, tell us.