Build calling and SMS into your product.
Order Australian numbers by API, send SMS that arrives in a median 2.7 seconds, and control every call with code. Our SDKs and agent-ready docs mean your AI coding assistant can build right alongside you.
- 2.7s median SMS delivery
- REST + gRPC Numbers, SMS and Voice APIs
- 3 zones Google Cloud, Sydney
30%lower SMS costs at WeKo, after switching
“By switching over to Enfonica, we have improved the delivery of our SMS to patients and reduced our costs by 30%.”
Ian Daniel Chief Technology Officer, WeKoWhat software teams build on Enfonica.
Numbers, SMS and calls, from the same account and the same docs.
-
Order phone numbers by API
Search for and buy Australian numbers from your own code, and give each of your customers a number of their own.
Who runs it:
- Software
-
Send reminders, alerts and codes
Send appointment reminders, delivery updates and one-time codes from your product, delivered in a median 2.7 seconds.
Who runs it:
- Software
-
Hold two-way SMS conversations
Receive replies by webhook, and keep every conversation with your customers inside your own product.
Who runs it:
- Software
- Small business
-
Register sender IDs for your clients
Register each client's alphanumeric sender ID on ACMA's SMS Sender ID Register, from your own account.
Who runs it:
- MSPs
- Software
-
Real-time streaming with frontier voice models
Stream a call's audio to your app and back as it happens, and put the voice model you choose on the line.
Who runs it:
- Software
-
Control calls from your own code
Answer and route calls from your own web server with VoiceML, from simple menus to transfers that check your own APIs.
Who runs it:
- Software
Docs your AI coding assistant can build from.
Most teams build with an AI coding assistant now, so we wrote our docs for both of you. Then we tested them. AI coding agents built apps using only our docs, we found where they got stuck, and we improved the docs until agents could build on our API without getting confused.
- One index for agents at enfonica.com/docs/llms.txt.
- SDKs, or the REST API from any language.
- REST and gRPC, following Google Cloud API conventions.
Read the Enfonica docs at https://enfonica.com/docs/llms.txt. Then add SMS appointment reminders to my app. Send each one from our Enfonica mobile number as a transactional message, ask people to reply Y to confirm, and handle delivery receipts and replies with signed webhooks.
Point your assistant at llms.txt, and it can build from our docs alone.
SMS, numbers and voice, built by your coding agent.
Point your coding agent at our docs and tell it what to build.
Works with Claude Code, Cursor, Codex and other coding agents.
>Read https://enfonica.com/docs/llms.txt, then add SMS appointment reminders. Send them from our Enfonica mobile number and handle the replies.
Fetch(enfonica.com/docs/llms.txt)The docs index, with the REST API, authentication and Cloud SMS
Fetch(docs/samples/oauth/nodejs/enfonica-credentials.ts)Added to src/ as it is, as the docs ask
Write(src/reminders.ts)
const credentials = EnfonicaCredentials.fromEnv();2+await fetch(`${MESSAGING}/v1/${project}/messages`, {3+ method: 'POST',4+ headers: { Authorization: await credentials.getAuthorizationHeader() },5+ body: JSON.stringify({ to, from: '+61491570110', body }),6+});Write(src/routes/sms-replies.ts)Checks X-Enfonica-Signature, then handles INCOMING_MESSAGE
Bash(npm test)6 passed
Reminders now send from 0491 570 110. Replies arrive at /sms/replies, and each request's signature is checked before it's trusted.
>Give each new clinic a mobile number of its own when it signs up.
Fetch(docs/phone-numbers/api-reference/rest/overview)numbering.api.enfonica.com, v1beta1
Write(src/numbers.ts)
// find a free mobile number, then add it to the project2+const found = await get(`${NUMBERING}/v1beta1/phoneNumbers:search`,3+ { countryCode: 'AU', numberType: 'MOBILE', supportsSms: true });4+await post(`${NUMBERING}/v1beta1/${project}/phoneNumberInstances`, {5+ phoneNumber: found.phoneNumbers[0],6+ labels: { clinic: clinic.id },7+ incomingMessageHandlerUris: ['https://your-brand.com.au/sms/replies'],8+});Update(src/signup.ts)Calls provisionNumber() when a clinic is created
Bash(npm test)9 passed
Each new clinic now gets its own mobile number at signup, and its replies come to the same webhook. An Australian mobile number also needs a regulatory listing with the clinic's name and address, which you assign in the Console.
>Connect calls to those numbers to GPT Realtime 2.1, so it answers them.
Fetch(docs/cloud-voice/voiceml/stream)A call's audio in both directions, over the StreamCall gRPC method
Write(src/voice-bridge.ts)
// the caller's voice to the model, and its reply back to the call2+const call = streams.StreamCall(metadata);3+call.write({ setup: { stream, audioConfig: MULAW_8K } });4+call.on('data', (m) => m.outputAudio && model.send(m.outputAudio.audio));5+model.onAudio((audio) => call.write({ inputAudio: { audio } }));6+model.onInterrupt(() => call.write({ inputAudio: { clear: true } }));Write(src/routes/voice.ts)
// answer the call by connecting it to the stream2+res.type('text/xml').send(`<Response><Stream>${stream}</Stream></Response>`);Update(src/numbers.ts)incomingCallHandlerUris now points each number at /voice
Bash(npm test)12 passed
Calls to each clinic's number are now answered by GPT Realtime 2.1. The call's audio streams both ways through src/voice-bridge.ts, and the model's queued reply is cleared when the caller interrupts.
Ready
3 prompts
Give every customer a number of their own.
Search for and buy Australian numbers from your own code, tag each one to the customer or user it belongs to, and decide in code what happens when someone calls or texts it.
- Mobile numbers for SMS and calls, plus local, 1300 and 1800 phone numbers for calls.
- Your customer's details on each number. Local and mobile numbers carry the name and street address of whoever uses them, from a regulatory listing you assign in the Console.
- Calls answered by your code with VoiceML, or sent to any SIP endpoint.
- Existing numbers ported in, with no interruption.
Numbers by API ready instantly
SMS that follows Australia's rules.
- Registered sender IDs. Since 1 July 2026, a sender ID shown to Australians must be on ACMA's SMS Sender ID Register. We won't send from one that isn't, so your messages never arrive marked unverified. Why unregistered sender IDs are blocked
- Opt-outs built in. When someone replies STOP, they join your project's unsubscribers, and the API refuses any later message to them that isn't marked transactional, with nothing sent or charged. Codes and reminders marked transactional still go through. Opt-outs belong to a project, so give each of your customers its own project to keep theirs separate. How SMS opt-outs work
- Signed webhooks. Set a status URL and a reply URL on each message, and your app hears when it's delivered, when a handset can't take it or when delivery fails, and receives every reply. Each request is signed with HMAC-SHA256, and if your endpoint is down, we retry with increasing delays for more than three hours. SMS webhooks
- refusedReminder from "AcmeDental": This sender ID is not registered for Australian SMS.
- deliveredReminder from AcmeClinic to 0491 570 156
- deliveredSurvey from 0491 570 110 to 0491 570 313
- reply"STOP" from 0491 570 313: unsubscribed
- refusedMarketing to 0491 570 313: Recipient is unsubscribed
- deliveredTransactional reminder to 0491 570 313
Put a frontier voice model on a live call.
Connect a call to your app with the VoiceML <Stream> action, and Cloud Voice streams the call's audio to you and plays back whatever you send, in real time. Your app sits between the caller and the voice model you choose, so the model hears the caller as they speak, and the caller hears it answer.
- Audio in both directions over one gRPC stream, as G.711 at 8 kHz.
- Interruptions handled by your code. Clear the audio you've queued the moment the caller starts talking.
- Back to your call flow when the conversation is done. Close the stream, pass on what the model learned, and transfer the caller to a person with VoiceML.
Live call audio in both directions
Caller“Can I move my appointment to Friday?”
Voice model“Of course. Does 10:30am or 2:15pm work?”
Connect it to whatever you're building.
Your own code through the API, a frontier voice model on a live audio stream, or an AI voice agent platform over SIP.
| Platform | How it connects | What you can use | Setup guide |
|---|---|---|---|
| Your own app | REST API and SDKs | Phone numbers, SMS and calls, all from your own code, with webhooks for what happens | Read the API docs |
| Frontier voice models | Real-time streaming | A call's live audio in both directions with VoiceML <Stream>, for the voice model you choose | VoiceML <Stream> in the docs |
| AI voice agents | SIP | An Australian number for your agent, for calls in and out | Connect a voice agent |
Voice and SMS APIs for SaaS: common questions.
Can't find yours? The docs and the Help Center go deeper.
How do we get API access?
Talk to our team, and we'll open your account. Then create a service account in the Console, download its key, and point your coding agent at our docs. Request API access
Which languages can we build with?
Any language that can make an HTTPS request. The REST API follows Google Cloud API conventions, and the docs have a tested authentication sample for Python, Node.js, Go, C#, Java, PHP and Ruby. Our SDKs for Node.js and .NET wrap the same API, and each API takes gRPC on the same host as REST. Client libraries
Can our AI coding assistant really build from your docs?
We tested it. AI coding agents built apps using only our docs, we found where they got stuck, and we improved the docs until agents could build on our API without getting confused.
Do you have Australian numbers for SMS and calls?
Yes. Mobile numbers send and receive both SMS and calls, and local, 1300 and 1800 numbers are for calls. They're ready instantly in the Console or by API, and you can port in the numbers you already have.
Do we need to register our sender ID for SMS?
Yes, when your messages show a name instead of a number. Since 1 July 2026, a sender ID shown to Australians must be on ACMA's SMS Sender ID Register, so you register yours in the Console with your ABN, and someone at your business confirms it in ACMA Assist with their myID. Messages from a phone number need no registration, and they're the only ones people can reply to. Register an alphanumeric sender ID
What limits should we plan for?
Each account starts with a limit of 100 concurrent calls and 10 outgoing call attempts per second, and we raise them on request. Planning a high volume of calls that would exceed these limits? Tell us your volumes before you launch.
Where does our traffic run?
On the Enfonica network, which runs across three Google Cloud zones in Sydney, with no single point of failure.
How is it priced?
Our prices are published, with pay-as-you-go pricing for numbers, calls and SMS. Numbers have a monthly fee, and SMS is charged by the segment. Every message records its own price and segment count in the API, so you can see what each of your customers costs. Committing to a monthly spend lowers your rates, and we can take your planned traffic into account when we set them.