smsbroadcast.com.au

SMS Broadcast is a bulk SMS platform that presents itself as a fit for Australian businesses: its site states it is trusted by 30,000 Australian businesses, and it offers online SMS, an email-to-SMS option, and a developer API. If your business needs to send text messages to customers and wants to pay only for what you send, it is worth evaluating. The main caveats are that suitability depends on your specific use case, and you should confirm current pricing and any trial conditions directly on the site.

What SMS Broadcast offers

Based on the site, the platform covers three main ways to send and receive messages:

• Online SMS – a web-based inbox for managing conversations, with no software download required.
• Email to SMS – send and receive texts from your existing email address, useful when you are away from a desk.
• Developer API – an HTTP API or email API to integrate the SMS gateway into your own systems, stated as available at no added cost.

The site also highlights contact import, grouping, and message templates as part of the setup experience, according to user reviews on the page.

Who it tends to suit

The platform's positioning and the reviews shown on its site point to a few common fits:

If you are a local business that mainly wants to reach customers by text — reminders, promotions, updates — the online inbox and template features are the parts most likely to matter day to day.

What to check before deciding

A few things are not fully resolved by the website content alone, so verify them before committing:

• Pricing per message – the site links to a pricing page and says you only pay for what you send, but the actual rates are not in the material here. Check the pricing page for current numbers.
• Free trial conditions – a free trial is mentioned, but its length, limits, and any requirements are not specified. Confirm the terms before relying on it.
• Your own volume and use case – whether the platform is cost-effective depends on how many messages you send and whether you need the API or email-to-SMS route.
• Compliance and consent – sending marketing SMS in Australia involves consent and opt-out rules. Make sure your process handles these, regardless of platform.

Bottom line

SMS Broadcast is aimed squarely at Australian businesses and offers the core tools most local senders need: an online inbox, email-to-SMS, an API, contact import, and templates, with pay-as-you-send messaging and no fixed-term contracts. It is a reasonable option to shortlist if you want a straightforward bulk SMS tool. Before signing up, confirm current per-message pricing and the exact free trial terms on the site, and check that your messaging complies with Australian consent requirements.

OpenAPI-generated API documentation is reference documentation that is produced automatically from an OpenAPI description file rather than written by hand. You write (or generate) a machine-readable specification of your API — endpoints, parameters, request bodies, responses, schemas, and auth — and a documentation tool reads that file and renders a browsable, often interactive reference site. The spec becomes the single source of truth; the docs become a build artifact.

This differs from manually written docs in one fundamental way: with hand-written docs, the prose is the source of truth and the API is described separately. With spec-driven docs, the API description is the source, and every page, table, and code sample is derived from it.

How the workflow actually runs

A typical spec-driven documentation pipeline has five stages:

1. Author or generate the spec. You either write an OpenAPI document by hand (YAML or JSON), or generate it from code annotations, framework metadata, or a design-first editor. Design-first means the spec is written before implementation; code-first means it is extracted from existing code.
2. Validate and lint. The spec is checked against the OpenAPI schema and against style rules — consistent naming, required descriptions, no undocumented 4xx responses, no orphaned schemas.
3. Bundle and transform. Multi-file specs are combined, $ref pointers are resolved, and the document is optionally split into per-tag or per-version outputs.
4. Render. A documentation tool converts the spec into HTML: an endpoint list, a sidebar of operations, parameter tables, response schemas, and a "try it" console.
5. Publish and version. The rendered site is deployed, and each API version gets its own snapshot so consumers can read docs matching the version they call.

Steps 2 through 5 are usually automated in CI. If the spec fails validation, the docs build fails — which is the point.

Spec-driven vs. hand-written documentation

The practical conclusion most teams reach: generate the reference, write the guides. Reference material is repetitive and mechanical, which is exactly what generation is good at. Conceptual explanations, migration notes, and tutorials carry judgment that a spec cannot express.

What you get out of the box

Generated reference pages commonly include:

• An operation list grouped by tag or path, with HTTP method and path.
• Parameter tables showing name, location (path, query, header, cookie), type, required flag, and description.
• Request and response schemas rendered as expandable trees, including nested objects and arrays.
• Authentication details pulled from the securitySchemes section.
• Interactive request consoles that let a reader send a real call from the browser.
• Generated code samples in several languages, derived from the same schemas.
• Multiple output formats, such as a static site, a single HTML file, or a mock server.

Because all of these come from one document, changing a field name in the spec updates the parameter table, the schema tree, and every code sample at once.

Where spec-driven documentation breaks down

Generation is not free. The trade-offs are real:

Spec quality becomes documentation quality. A field with no description produces a table row with an empty cell. A vague summary produces a vague heading. Tools can enforce presence of descriptions via linting, but they cannot enforce that the description is useful.

Customization has limits. If you need a page that does not map to an OpenAPI concept — a conceptual overview, a pricing explanation, a comparison of two endpoints — you write it outside the generator and link to it.

Not everything is expressible. Webhooks, streaming responses, long-polling behavior, and complex multi-step flows are awkward or impossible to describe fully in OpenAPI. Those need prose.

The spec can go stale. If the spec is maintained separately from the implementation, it drifts just like hand-written docs. The mitigation is to generate the spec from code, or to test the implementation against the spec in CI.

Interactive consoles need care. A "try it" button that hits a production API with real credentials is a security and rate-limit problem. Point it at a sandbox, or disable it.

Deciding whether to adopt it

Adopt spec-driven reference documentation if most of these are true:

• Your API has more than a handful of endpoints, or changes frequently.
• You ship client SDKs or code samples in more than one language.
• Multiple teams consume the API and need a consistent, always-current reference.
• You already have, or are willing to maintain, an OpenAPI description.

Stay with hand-written docs, or a hybrid, if:

• Your API is small and stable, and the reference fits on one page.
• Your documentation is mostly conceptual and contains little endpoint-level detail.
• You cannot commit to keeping the spec in sync with the implementation.

A reasonable middle path: generate the reference from the spec, and hand-write the getting-started guide, authentication walkthrough, and error-handling page. Link the two directions so readers can move from concept to endpoint and back.

A minimal starting checklist

1. Produce one valid OpenAPI document for a single API version.
2. Add a linter with rules for descriptions, operation IDs, and error responses.
3. Wire the docs build into CI so a failing spec fails the build.
4. Render the reference and review it as a reader, not as the author.
5. Write the two or three conceptual pages the generator cannot produce.
6. Version the published docs alongside the API version.

The core idea is simple: describe the API once, in a format both machines and humans can read, and let the reference documentation fall out of that description. Everything else — tooling, hosting, interactivity — is a detail on top of that decision.

SMS Broadcast offers three ways to send and receive text messages: Online SMS (a web-based inbox), Developer API (HTTP or email API for system integration), and Email to SMS (send and receive from your existing email address). All three are available from a single account, and the Developer API is described as having no added cost. Which one suits you depends on whether you want a ready-made interface, a programmatic connection, or a familiar email workflow.

Online SMS: for teams that want a ready-made interface

This is the option to pick if you want to manage conversations directly in a browser without installing anything.

• What it is: A web-based inbox for managing SMS conversations.
• Input: Your contact lists and message content, entered in the browser.
• Action: Import contacts, create groups, set up templates, and send from the online inbox.
• Expected result: You send and receive messages and track conversations in one place, with no software download.

Reviewers on the site repeatedly mention the same practical points: importing multiple contacts and creating groups is straightforward, templates save time on repeat messages, and the setup is quick. One reviewer (David) specifically calls out importing contacts and creating groups; another (Paul) highlights templates and cost-effectiveness. If your team sends recurring campaigns to grouped audiences, this is the lowest-friction starting point.

Developer API: for integrating SMS into your own systems

Choose this if you need SMS triggered by your own software rather than typed by a person.

• What it is: An SMS gateway you integrate into your systems, offered as either a full-feature HTTP API or an email API.
• Input: Requests from your application to the SMS gateway.
• Action: Your system calls the API to send messages.
• Expected result: SMS becomes a function of your existing software, and the site states the API carries no added cost.

The key decision here is HTTP API versus email API. The HTTP API is the fuller option and fits applications that need to construct requests programmatically. The email API is the lighter path if your system already generates email and you want that to become an SMS. Both are described as available at no added cost, so the choice is about your architecture, not price.

A concrete scenario

For example, if you run a booking system and want a confirmation text the moment an appointment is made, the HTTP API lets your application fire that message automatically. If instead you have an internal tool that already emails staff, the email API can turn those emails into texts without new code.

Email to SMS: for sending from your existing inbox

Pick this if you want to keep working in email but have the message arrive as a text.

• What it is: Send and receive text messages from your existing email address.
• Input: An email you compose and send as usual.
• Action: Your email is routed to the recipient as an SMS.
• Expected result: You can communicate by text while on the go, without opening a separate SMS tool.

The site frames this as a way to "still communicate while on the go." It suits people who are already in their inbox all day and don't want a second interface for occasional messages.

How to choose

The three methods are not mutually exclusive — they sit under one account, so you can start with Online SMS and add API integration later, or use Email to SMS alongside either.

What to check before committing

• Pricing and trial terms: The site advertises a free trial and a pricing page, and states you "only pay for what you send" with "no fixed term contracts." Check the pricing page for current per-message rates, since these are not specified in the material available here.
• Volume and use case: The "only pay for what you send" model suits variable or campaign-based sending. If you send at a steady high volume, confirm the rates still work for you.
• Integration effort: The API is the only method that requires development work. If you have no developer, Online SMS or Email to SMS will get you sending faster.

SMS Broadcast reports being trusted by 30,000 Australian businesses with a 4.7 out of 5 rating across 5,000 reviews, and the recurring themes in those reviews — ease of setup, contact import, templates, and support — map most directly to the Online SMS experience.

SMS Broadcast charges on a pay-as-you-go basis: you only pay for the text messages you actually send, and there are no fixed-term contracts. A free trial is available, and specific rates are listed on the company's pricing page. This model suits businesses that want to test bulk SMS before committing and keep messaging costs tied directly to volume rather than a monthly subscription.

How the pricing model works

The core mechanic is simple: cost is calculated per message sent, not per month or per user.

• Pay only for what you send — the site states "Only pay for what you send," so there is no charge for unused capacity.
• No fixed term contracts — you are not locked into a long-term agreement, which matters if your SMS volume fluctuates or you want to switch providers later.
• Per-message rates — exact rates are not shown on the homepage. You need to check the Pricing page for current figures, since rates can vary by volume or destination.

Because pricing is usage-based, your effective cost depends on how many messages you send and where you send them. A business sending a few hundred messages a month has a very different bill from one sending tens of thousands.

What the free trial covers

SMS Broadcast advertises a free trial, which lets you test the platform before paying. The homepage and site description both reference it ("Get a free trial!").

What to confirm before relying on it:

• Trial limits — the number of free messages, trial length, and whether any features are restricted are not specified in the available site content. Check the pricing or sign-up page for the current terms.
• What you can test — the platform supports Online SMS (a web-based inbox), Email to SMS, and a Developer API. A trial is the practical way to confirm which of these fits your workflow.
• No software install for Online SMS — the site notes you manage conversations in a web-based inbox without downloading software, so the trial requires only a browser.

Choosing SMS Broadcast: what fits and what to check

The API is described as available "at no added cost," which means integration itself does not carry a separate platform fee — you still pay per message.

Who this pricing suits

This model tends to fit:

• Small or growing businesses testing SMS marketing without a subscription commitment.
• Teams with variable volume — for example, seasonal promotions or one-off customer notifications — since unused months cost nothing.
• Developers who want to embed an SMS gateway via HTTP or email API without an added platform charge.

It is less obviously suited to organisations that need a fixed monthly cost for budgeting, or that require rate certainty before signing up — in those cases, get the per-message rates from the Pricing page first and model them against your expected volume.

Practical next steps

1. Open the Pricing page to get current per-message rates.
2. Start the free trial to test Online SMS, Email to SMS, or the API against your real workflow.
3. Estimate your monthly message volume and multiply by the listed rate to project cost.
4. Confirm trial terms (message cap, duration) before depending on it for a live campaign.

SMS Broadcast is an Australian bulk SMS platform built around a web-based inbox, so you can send and manage messages from a browser without installing any software. It suits businesses that want to import contacts, group them, reuse message templates, and pay only for the messages they send. The features below are the ones that most directly affect how quickly you can get started and how much day-to-day effort sending takes.

A web-based inbox with no software to install

The core sending and receiving interface runs in your browser. You log in, manage conversations, and send messages from the same place. Because there is nothing to download, setup does not depend on installing or maintaining a desktop application, and you can work from any machine where you can sign in.

For a small team, this means the person sending messages does not need special software or IT involvement to get going.

Contact import and grouping

You can import multiple contacts and organise them into groups. This matters because bulk SMS usually means sending the same message to a defined audience rather than typing numbers one at a time. Grouping lets you keep separate lists — for example, customers, staff, or event attendees — and target each one without rebuilding the list every time.

A practical workflow looks like this:

1. Export your contacts from wherever they currently live (CRM, spreadsheet, booking system).
2. Import them into SMS Broadcast.
3. Create groups so future sends only need a group selected, not a fresh upload.
4. Send to the group and manage replies in the web inbox.

Message templates

Templates let you save a message you send repeatedly and reuse it instead of retyping. This is useful for appointment reminders, order updates, or standard follow-ups where most of the wording stays the same and only a few details change. Reviewers specifically call out templates as a feature they like, alongside cost-effectiveness.

Three ways to send

SMS Broadcast offers more than one sending method, which changes how much manual work a message requires:

The API is described as available at no added cost, and it comes in a full-feature HTTP version or an email version. Email to SMS is the lowest-effort option if you already live in your inbox and do not want to log into another tool.

What users report about ease of use

The site highlights a 4.7 out of 5 rating across 5,000 reviews, and the recurring themes in those reviews are directly about ease of use:

• Setup described as quick and easy, with results reported as immediate.
• Importing multiple contacts and creating groups called out as simple.
• Templates and value for money mentioned together.
• Customer support described favourably.

These are user-reported impressions rather than verified performance claims, but they consistently point to a short path from sign-up to first send.

Who this fits

SMS Broadcast is positioned for Australian businesses — the site states it is trusted by 30,000 Australian businesses. It fits best if you want:

• Pay-per-message sending with no fixed-term contract.
• A browser-based tool rather than installed software.
• The option to automate later via API without switching platforms.
• A free trial before committing.

If your main need is a fully custom messaging application with bespoke UI, the API route is the relevant feature rather than the web inbox. If you simply want to send reminders and updates to grouped contacts, the online inbox plus templates covers it.

To judge fit for your own case, start with the free trial, import a real contact list, build one group and one template, and send a test message to yourself before rolling it out to a full audience.