Bulk SMS API Australia: Create Keys and Webhooks in SMSFlow
TL;DR: SMSFlow gives Australian businesses API access under Account > Developers so you can create, regenerate, or revoke keys and set a webhook URL. Use the API with the web platform for sending SMS to Australian numbers and managing contacts once your account is verified.
Get API access in five steps
-
Register and finish verification
Sign up at SMSFlow with a valid ABN, Australian mobile, and business-ready email. Complete 2FA, verify your email, and verify your ABN before you can send. New accounts receive 50 free credits. -
Open Account Developers
In the web app, go to Maintenance > Account > Developers. This is where API keys and the webhook URL live. -
Create an API key
Create a key for your integration. Store it securely in your app or secrets manager. Treat it like a password. -
Regenerate or revoke when needed
If a key is exposed or a contractor leaves, regenerate or revoke it from the same Developers screen. Old keys stop working after revoke or regenerate. -
Set your webhook URL
Add the webhook URL your system should receive events on. Keep the endpoint HTTPS and ready to acknowledge requests. Then send or manage contacts via the API the same way you would in the platform, using credits from your balance.
More detail below if you need context on credits, limits, and how the API sits next to the web UI.
What the SMSFlow API is for
SMSFlow is built for Australian businesses that need a simple platform and API. The Developers area covers API keys (create, regenerate, revoke) and a webhook URL. Sending SMS to Australian numbers and managing contacts are available on both the platform and the API. Campaigns are also available via platform and API while that feature is in beta.
You still work in credits, not a flat "one message equals one credit" model. Longer or more complex messages can use more than one credit. Check remaining credits and invoices under Account > Billing, and see current options on pricing.
The product is web only. There is no desktop or mobile app. It is not a full CRM, and it does not offer custom workflows or custom integrations beyond the standard API access described here.
Account checks before first API send
API sends follow the same rules as the UI:
- Valid ABN (validated)
- Australian mobile on the account
- Email verified
- 2FA completed at signup
- ABN verified in Accounts before send
- Extra human checks may apply for Gmail or other non-business email domains
If a mobile number was used on an account before, a new signup with that number is blocked. Fix verification gaps in the web app first if API calls fail to send.
Using API and web platform together
Many teams keep day-to-day bulk sends, groups, templates, and reports in the browser, and use the API for automated transactional or system-triggered SMS. Contacts can be maintained in the UI (including CSV import matched on phone number) or via the API, then reused for bulk sends.
Reports, dashboard stats, Inbox, and Sender ID requests stay in the web app. Inbox shows inbound messages from numbers you have messaged; you reply via Send SMS, not from Inbox. If you use a Sender ID, recipients cannot reply.
For opt-outs, unsubscribe keywords and the unsubscribes report help you keep lists clean. Those controls live in account and reporting screens, not as separate "custom workflow" builders.
Practical tips for developers
- Create separate keys per environment (for example staging vs production) and revoke keys you no longer need.
- Rotate keys after staff or agency changes.
- Point the webhook at a stable HTTPS URL and log failures so you can spot delivery or parse issues early.
- Preview credit use in the UI when you are unsure how long copy or placeholders affect cost; billing is per credit.
- Prefer dedicated business email domains at signup to reduce manual review delays.
Related guides in this series cover bulk SMS Australia basics, sending bulk SMS, contact groups, and credits.
FAQ
Where do I create a bulk SMS API key in SMSFlow?
Under Maintenance > Account > Developers. From there you can create, regenerate, and revoke API keys and set a webhook URL.
Can I send bulk SMS and manage contacts through the API?
Yes. Sending SMS to Australian numbers and managing contacts are supported on both the platform and the API after your account is verified.
Do I need an ABN to use the API?
Yes. SMSFlow is for Australian businesses with a valid ABN. Email, ABN, and related checks must pass before sending, including via the API.
How do credits work with API sends?
Billing is per credit. Some messages use more than one credit. New signups get 50 free credits. See pricing for current credit packs rather than assuming one credit per SMS.
Can recipients reply when I send via the API with a Sender ID?
No. When a Sender ID is used, recipients cannot reply. That applies whether you send from the UI or the API.
Is there a mobile app for API key management?
No. SMSFlow is web only. Manage keys and webhooks in Account > Developers in the browser.
SMSFlow for developers and marketing teams
SMSFlow keeps API access straightforward: keys and a webhook URL in Developers, with send and contact management available beside the same web tools your marketing team already uses. You get 50 free credits on signup, clear credit-based billing, and Australian-number sending once verification is done.
Conclusion
Set up your bulk SMS API Australia access by verifying the account, creating a key under Developers, setting a webhook URL, and rotating keys when people or systems change. Use the API where automation helps, and the web app for groups, reports, and day-to-day bulk work.
Try SMSFlow free or contact us if you have account questions. For credit packs, see pricing.