gunisms.com.au

Guni SMS is an Australian two-way SMS and MMS service provider built for business messaging. It offers bulk SMS, an SMS API, Email to SMS, MMS marketing, wholesale SMS, and subaccount management, with Australian business SMS starting from 2.8c. It suits Australian organisations that need to reach customers at scale while keeping data onshore and support local.

What Guni SMS actually is

Guni SMS describes itself as a two-way SMS service provider that simplifies SMS and MMS sending through an SMS gateway. The platform is positioned as affordable and accessible, so businesses can run customer communication without deep technical setup.

Two-way messaging matters here: it means conversations can go both directions, not just one-way blasts. That makes it usable for replies, opt-ins, and support-style exchanges rather than only announcements.

Core capabilities

The site lists these main functions:

• Bulk SMS — send messages to many recipients at once.
• SMS API — connect messaging to your own systems or applications.
• Email to SMS — send texts directly from your inbox, with no technical setup required.
• MMS marketing — run text and MMS campaigns.
• Wholesale SMS — messaging capacity for higher-volume or reseller-style use.
• Subaccount management — manage multiple accounts under one platform.

The platform is described as enterprise-level, so the feature set is aimed at organisations running ongoing or large-scale campaigns rather than occasional one-off texts.

Delivery, security, and support

Three claims stand out for Australian buyers:

For businesses with data-residency or compliance considerations, the onshore server and local routing points are the most relevant. The 24/7 local support claim is also a differentiator if you need help outside standard hours.

Pricing model

Guni SMS uses a "Pay & Go" model, which the site describes as transparent and predictable for budgeting. Two pricing details are stated:

• Australian business SMS from 2.8c.
• Unlimited incoming SMS and MMS at no additional cost.

The site also mentions 500 bonus SMS on your first credit purchase, and a separate offer of 50 free SMS credits through an interactive demo or by connecting with an SMS expert. Treat these as promotional offers tied to specific actions, not standing free allowances.

Who it fits

Guni SMS is aimed at Australian businesses that need scalable customer communication. It is a reasonable fit if you:

• Send SMS or MMS regularly or at volume.
• Want an API to integrate messaging into existing systems.
• Prefer Australian-based servers and local support.
• Want to avoid lock-in contracts.
• Need two-way messaging rather than one-way broadcasts.

It is less obviously suited to someone sending a handful of messages occasionally, or to businesses operating primarily outside Australia, since the routing, servers, and support are all Australia-focused.

How to evaluate it

The site reports being trusted by 2,000+ Australian businesses, which is a self-reported figure rather than an independent benchmark. To decide whether it fits your needs, the practical steps are:

1. Use the interactive demo or contact the team to claim the 50 free SMS credits and test delivery.
2. Check the SMS API documentation against your existing stack if integration matters.
3. Confirm current per-message pricing and any volume tiers directly, since the 2.8c figure is a starting rate.
4. Ask about the Pay & Go terms and whether the 500 bonus SMS applies to your first purchase.

The main things to verify before committing are API compatibility, actual delivery performance for your audience, and how the Pay & Go model scales as volume grows.

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.

You can start with Guni SMS in three ways: book a demo or use the "Get Started Free" option to connect with an SMS expert, try the interactive demo to get 50 free SMS credits, or make a first credit purchase to receive 500 bonus SMS. The right path depends on whether you want to test the platform first or commit to a paid plan immediately.

Before You Start

Guni SMS is an Australian two-way SMS and MMS provider offering an SMS gateway, SMS API, email to SMS, MMS marketing, wholesale SMS, and subaccount management. Before signing up, confirm a few basics so you choose the right setup:

• Sending method — Do you want to send from a web platform, connect via the SMS API, or send from your email inbox using email to SMS?
• Volume — Estimate how many messages you send monthly, since pricing is a "Pay & Go" model starting from 2.8c.
• Account structure — If you manage multiple brands or clients, ask about subaccount management.
• Compliance needs — Guni SMS runs on Australia-based servers with onshore technology, which matters if data confidentiality and local compliance are requirements.

Step-by-Step: Getting Started

Option 1: Book a Demo or Get Started Free

1. Select Book Demo or Get Started Free on the site.
2. Connect with an SMS expert who can walk you through the platform.
3. Use this route if you want guidance on setup, API integration, or campaign structure before committing.

Expected result: A guided onboarding and answers to your specific questions about sending methods and volume.

Option 2: Try the Interactive Demo for 50 Free SMS Credits

1. Open the interactive demo on the Guni SMS site.
2. Follow the demo flow to explore how sending works.
3. Claim the 50 free SMS credits offered through the demo.

Expected result: You can test message delivery and platform behavior without spending money.

Option 3: First Purchase for 500 Bonus SMS

1. Set up your account and choose your sending method.
2. Make your first credit purchase.
3. Receive 500 bonus SMS on that first purchase.

Expected result: A larger credit balance to run real campaigns, on top of your purchased credits.

What You Get Once You're Set Up

Guni SMS states it is trusted by 2,000+ Australian businesses and reports 99% delivery with local routing.

Common Questions When Starting

Do I need technical setup for email to SMS? No — the site describes reaching your audience directly from your inbox without technical setup. The SMS API route is for those who want programmatic sending.

Which free credit offer applies to me? The 50 free SMS credits come through the interactive demo. The 500 bonus SMS applies to your first credit purchase. These are separate offers, so you can use the demo credits to test before buying.

Is there a contract? Guni SMS advertises no lock-in contracts, so you are not tied to a long-term commitment.

What if I'm unsure about volume or setup? Use Book Demo or Get Started Free to speak with an SMS expert before choosing a plan.

Quick Recommendation

• Want to test first? Use the interactive demo for 50 free SMS credits.
• Ready to commit? Make your first purchase to get 500 bonus SMS.
• Need guidance or have complex needs (API, subaccounts, wholesale)? Book a demo or Get Started Free and speak with the local support team.

Guni SMS is worth shortlisting if you are an Australian business that wants a local-routed SMS gateway with bulk SMS, an SMS API, and email-to-SMS, priced from 2.8c per message on a Pay & Go model with no lock-in contract. It is less clearly suited if you need published, itemised pricing before you talk to a sales team, or if your volume is large enough that wholesale rates need to be negotiated and verified first. Below are the specific things to confirm before you commit.

Confirm the sending methods you actually need

Guni SMS advertises three main ways to send, and you should check that the one matching your workflow is covered:

• Bulk SMS — for campaigns sent to a contact list.
• SMS API — for sending triggered or transactional messages from your own software.
• Email to SMS — for reaching customers directly from your inbox without technical setup.

The site also lists MMS marketing, wholesale SMS, and subaccount management. If you run multiple brands or client accounts, subaccounts matter; if you only send one-off campaign blasts, they may be irrelevant. Match the feature list to your real sending pattern rather than the full feature set.

Check routing, delivery, and where your data sits

Two claims are central to the value proposition and both are worth verifying against your own use case:

If your messages are transactional (appointments, alerts, verification codes), delivery speed and reliability matter more than campaign features. If they are marketing, opt-out handling and compliance matter more. The site states direct telco connections for instant delivery — ask for evidence at your expected volume.

Understand the pricing model before you scale

The headline rate is from 2.8c, and the model is Pay & Go, described as transparent and predictable, with unlimited incoming SMS and MMS at no extra cost. There are also promotional credits: 50 free SMS credits via the interactive demo, and 500 bonus SMS on your first credit purchase.

What to check:

• Whether 2.8c applies to your destination mix and message type, or only to specific routes.
• How MMS and wholesale pricing are quoted, since these are listed separately.
• Whether the bonus credits have an expiry or minimum purchase condition.

The site does not publish a full rate card, so treat the 2.8c figure as a starting point and get your actual per-message cost confirmed in writing for your volume.

Weigh the trust signals against your own requirements

Guni SMS states it is trusted by 2,000+ Australian businesses, offers no lock-in contracts, and provides 24/7 local support from an Australian team. These are meaningful if flexibility and local help matter to you — no lock-in means you can leave if delivery or pricing disappoints.

But "2,000+ businesses" tells you about adoption, not fit. A business sending 200 messages a month and one sending 200,000 have different needs. Use the reference as a reason to trial, not a reason to skip your own evaluation.

A practical pre-decision checklist

1. List your required sending methods (bulk, API, email-to-SMS, MMS).
2. Get a written per-message quote for your actual volume and destinations.
3. Confirm delivery-rate methodology and whether it is guaranteed or indicative.
4. Verify data residency and compliance against your industry obligations.
5. Test the API or email-to-SMS path with the free credits before committing.
6. Confirm contract terms — no lock-in should mean you can exit without penalty.

If those six items check out against your usage, Guni SMS is a reasonable fit for a small-to-mid Australian business wanting local routing and flexible billing. If you need published rates or enterprise-grade SLAs up front, request them directly before deciding.

Guni SMS prices Australian business messaging from 2.8¢ per SMS, using a "Pay & Go" model with no lock-in contracts. You buy credits and spend them as you send, so cost tracks volume rather than a fixed monthly commitment. Incoming SMS and MMS are listed as unlimited at no additional cost, and the site advertises 500 bonus SMS on your first credit purchase plus 50 free SMS credits through an interactive demo. The sections below cover what that means for budgeting and where the published information stops.

The pricing model at a glance

The practical effect of a credit model is that your monthly spend is a function of how many messages you send, not a recurring seat or platform fee. That suits businesses with uneven campaign volume — quiet months cost less, heavy campaign months cost more, with no renegotiation.

What "from 2.8¢" does and doesn't tell you

The 2.8¢ figure is a starting rate, not a flat rate. The site presents it as the entry point for Australian business SMS with local routing, alongside a claimed 99% delivery rate. It does not publish a rate card showing how price changes by destination, message type, or volume tier.

So treat 2.8¢ as a floor for estimating, not a quote. To turn it into a budget number:

1. Estimate your monthly outbound SMS volume.
2. Multiply by 2.8¢ to get a best-case baseline.
3. Ask Guni SMS for the rate that applies to your actual mix — especially if you send MMS, international messages, or high volumes that might qualify for wholesale pricing.

MMS is offered as part of the platform, but the published material does not give a separate MMS rate, so that needs confirming directly.

Where the cost predictability comes from

Three features in the published description support budgeting:

• Pay & Go credits. You top up and draw down. There is no stated minimum term, so you are not committing to a fixed spend across a contract period.
• No lock-in contracts. The site states this explicitly, which means switching costs are not built into the pricing structure.
• Free inbound. Unlimited incoming SMS and MMS at no extra cost removes a variable that often surprises two-way messaging budgets — replies from customers don't add to your bill.

The 500 bonus SMS on first credit purchase effectively discounts your first top-up. If you send, say, 2,000 messages a month, that bonus covers roughly a quarter of one month at the entry rate — useful for a trial, not a structural discount.

How to verify pricing before committing

Because the site gives a starting rate rather than a full schedule, confirm these before you buy credits:

• Your effective per-message rate at your expected volume, including any wholesale tier.
• MMS pricing, since only SMS has a published starting rate.
• Whether the 2.8¢ rate applies to all Australian destinations or only specific networks.
• Credit expiry, if any — the site does not state whether purchased credits expire.
• Setup or platform fees, if any — none are mentioned, but "from 2.8¢" refers to messaging, not necessarily to every account cost.

The interactive demo offering 50 free SMS credits is the lowest-risk way to test delivery speed and the sending workflow before spending. The site also advertises 24/7 local support from an Australian team, which is the channel to use for a written rate confirmation.

Who this pricing suits

The Pay & Go structure fits Australian businesses that want SMS as a variable cost — campaign-driven senders, small teams without a messaging platform budget line, and anyone unwilling to sign a term contract. It is less obviously suited to organisations that need a fixed, fully predictable monthly invoice, since spend rises and falls with volume and the full rate card is not published.

If your priority is a hard monthly cap, ask Guni SMS whether credit top-ups can be limited or whether spend alerts exist. If your priority is the lowest per-message cost at high volume, the wholesale SMS and subaccount options are the relevant conversation, and the 2.8¢ starting rate is only the beginning of that negotiation.