On this page
Enfonica is an Australian cloud telco with APIs for phone numbers, SMS, and phone calls. From your own code, you can buy Australian and New Zealand numbers, send and receive SMS, and answer, make, and control calls, over REST or gRPC.
This page covers what you can build, how the parts fit together, what isn't supported, and the limits to plan for. When you're ready to build, contact sales to get an account, and then follow Get started.
Connecting a phone system or Microsoft Teams?
You don't need the API for that. Enfonica supplies the phone numbers and the SIP trunks, which carry your calls over the internet. It doesn't supply the phone system. Start with Cloud SIP or Microsoft Teams Direct Routing. To build call flows for incoming calls in a visual editor, see Flow. To get an account, contact sales.
What you can build
- Give every customer a number of their own. Search for and buy numbers from your code with the Phone Numbers API, and set where each number's calls and messages go.
- Send reminders, alerts, and codes. Send an SMS with one request to Cloud SMS, and get a status webhook when it's delivered.
- Hold two-way SMS conversations. Receive each reply at your server as an incoming message webhook, and answer it with MessageML.
- Send from a business name. Use an alphanumeric sender ID in place of a number. People can't reply to a sender ID, because it has no number behind it. To send to Australian numbers, you must register it first.
- Answer and route calls from your own server. Cloud Voice asks your web server what to do with each call. Your server answers with VoiceML to play a message, collect digits, record, or connect the call to a phone number or a SIP address.
- Put a voice model on a live call. Your app opens a gRPC stream to Enfonica, and the VoiceML
<Stream>action connects a call to it. Enfonica sends the caller's audio to your app, and plays back the audio that your app sends, in real time. The audio is G.711 (mu-law or A-law) at 8 kHz, and the stream is gRPC, not a WebSocket. - Keep each of your customers separate. Create a project for each customer from your app, so that their numbers, opt-outs, and usage stay apart.
How Enfonica fits together
Your app and Enfonica talk in two directions:
- Your app calls the API to send an SMS, start a call, or buy a number.
- Enfonica calls your app with a webhook, which is an HTTP request to a URL that you choose. It does this when an SMS or a call arrives, and when a message or a call changes status. For an incoming SMS or call, your response tells Enfonica what to do next.
A request and a reply
This request sends an appointment reminder. It marks the message as transactional, and it tells Enfonica where to send the reply and the delivery status:
curl -X POST https://messaging.api.enfonica.com/v1/projects/my-project/messages \
-H "Authorization: Bearer $ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"to": "+61491570156",
"from": "+61491570110",
"body": "Your appointment is at 10:30am tomorrow. Reply Y to confirm.",
"classification": "TRANSACTIONAL",
"replyUrl": "https://example.com/sms/reply",
"statusUpdateUrl": "https://example.com/sms/status"
}'
The response is the message. Its name identifies it, and its status changes as the message is sent and delivered:
{
"name": "projects/my-project/messages/j6tfskeu3q0t6k3hp4fnh7d19c1p1p",
"status": "SENDING",
"segmentCount": 1
}
The response has more fields than these.
When the person replies, Enfonica posts the reply to replyUrl. The request body is the message that arrived:
{
"name": "projects/my-project/messages/oprrgs28k9dm5ylgcsqywrrt09j6bg",
"to": "+61491570110",
"from": "+61491570156",
"body": "Y",
"direction": "INCOMING",
"segmentCount": 1,
"price": {
"units": 0,
"nanos": 0,
"currencyCode": "AUD"
},
"status": "RECEIVED",
"createTime": "2026-11-16T23:08:33.813264900Z",
"encoding": "GSM7"
}
To answer it, your app returns MessageML:
<Response>
<Message>Thanks, you're confirmed for 10:30am.</Message>
</Response>
Calls work the same way. Enfonica asks your server what to do with a call, and your server answers with VoiceML.
Four ideas to know
| Idea | What it means |
|---|---|
| Project | A project holds your phone numbers, messages, calls, and settings. It's part of every resource name, such as projects/my-project/messages/MESSAGE_ID. See Projects. |
| Service account | The identity that your code runs as. Your app exchanges the service account's key for an access token that lasts up to one hour, and sends the token with every request. See Authentication. |
| One API design | Phone Numbers, Cloud SMS, and Cloud Voice name resources, page through lists, and report errors in the same way, following Google Cloud API conventions. Each API has its own host, which serves REST and gRPC. |
| Signed webhooks | Every request that Enfonica sends to your app carries an HMAC-SHA256 signature, so your app can check that the request came from Enfonica. See Request signing. |
What's supported
| Area | What's supported |
|---|---|
| APIs | Phone Numbers, Cloud SMS, and Cloud Voice. Each has a REST API and a gRPC API. Real-time audio streaming is gRPC only. |
| Client libraries | Node.js and .NET. |
| Other languages | Call the REST API directly. Authentication has a tested sample for Python, Node.js, Go, C#, Java, PHP, and Ruby. |
| Phone numbers | Australian mobile, local, 1300, and 1800 numbers, and New Zealand local and toll-free numbers. You can also port in the numbers that you already have. |
| SMS | Send to mobile numbers in Australia, New Zealand, and other countries, from a mobile number or an alphanumeric sender ID. Receive on your mobile numbers. |
| Calls | Receive calls on your numbers, and make calls to Australian, New Zealand, and international numbers. |
| On a call | Play audio, read text aloud in English, collect keypad digits, record, transcribe, receive a fax, connect the call to a phone number or a SIP address, and stream the audio to your app. |
Enfonica's key coverage is Australia and New Zealand, with outbound calling internationally. International phone numbers and other services are available on request.
Not supported
If your design depends on one of these, Enfonica isn't the right fit for that part:
- MMS. Cloud SMS sends and receives text messages only.
- WebRTC. There's no SDK for calling from a browser or a mobile app. Calls reach Enfonica from the phone network or over SIP. For a call's live audio, your server opens a gRPC stream to Enfonica.
- A phone system (PBX). Enfonica isn't a phone system. Cloud SIP provides SIP trunks that connect your own phone system or contact center platform to the phone network.
Before you build
These limits and requirements change how you design an app, so it's worth knowing them first. Limits has the full list.
- A sender ID must be registered before it can send to Australia. The API refuses a message to an Australian number from an alphanumeric sender ID that isn't registered to your project. Registration isn't instant, so start it early. A message from a phone number needs no registration.
- Local and mobile numbers need a regulatory listing. A regulatory listing is the name and address of whoever uses the number, and you create it before you buy the number. Australian 1300 and 1800 numbers don't need one. See what Australian and New Zealand numbers need.
- An SMS can be up to 10 segments long. A long message is sent in segments, and each one is charged. Ten segments is 1,530 characters, or 670 if the message has a character outside the GSM-7 alphabet, such as an emoji. A longer message is cut to fit. Each request sends to one number.
- Opt-outs are enforced for you. When someone replies STOP, Enfonica adds them to your project's unsubscribers, and the API refuses later messages to them. The exception is a message that you mark as transactional, such as a code or a reminder: set its
classificationtoTRANSACTIONAL, and it's sent without that check. See How SMS opt-outs work. - Your server has 10 seconds to answer a webhook. If a webhook about a message, or about a call event such as a finished recording, fails, Enfonica retries it for more than three hours, so the same webhook can arrive more than once. A VoiceML request, which asks your server what to do with a live call, isn't retried. You can give a number up to five URLs to try in turn, and if none of them answers, the call fails.
- A call can last up to four hours.
- Calls to high-risk international destinations are blocked by default. You can change this for each project. See Toll fraud prevention.
- Cloud SIP starts at 100 concurrent calls and 10 outgoing call attempts per second for each account. We raise both on request. See Cloud SIP limits. A Teams Direct Routing domain is different: it starts with one channel for outgoing calls, and you can add more.
Get started
- Get an account. Enfonica has no self-service sign-up at the moment, so contact sales to get one. We check every new account, because phone networks attract fraud.
- Create a service account, and download its key. Your code uses the key to get access tokens. Service accounts shows how to create one, and Authentication has a tested, one-file sample for Python, Node.js, Go, C#, Java, PHP, and Ruby.
- Get a number. Create a regulatory listing, and then buy an SMS-enabled mobile number, in the Enfonica Console or with the Phone Numbers API. Buy a phone number shows the steps in the Console.
- Send your first SMS. Follow the Cloud SMS quickstart, or the Node.js tutorial, which also replies to incoming messages.
- Or answer your first call. Set the number's incoming call handler to a URL on your server, in the Console (Choose where calls to your number go) or with the API (
incomingCallHandlerUris), and return VoiceML from it. Controlling calls shows the exchange, and VoiceML requests has the detail.
Build with an AI coding agent
We tested these docs by having AI coding agents build apps from them alone, and we fixed the places where an agent got stuck. To build with yours, give it the docs index and say what you want. For example:
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.
llms.txt is an index of these docs for agents. It explains how to authenticate and how to handle webhooks, and it links to the authentication samples as plain files that an agent can download.
Browse the docs
| Section | What's in it |
|---|---|
| Enfonica Platform | Projects, authentication, request signing, limits, toll fraud prevention, and usage data. |
| Phone Numbers | Search for, buy, and set up numbers. The regulatory requirements for each type of number. The API reference. |
| Cloud SMS | Send and receive SMS. Webhooks, MessageML, and sender IDs. The API reference. |
| Cloud Voice | Control calls from your server. VoiceML, webhooks, and billing. The API reference. |
| Cloud SIP | SIP trunks for your phone system or contact center. Making calls, load balancing, IP addresses, codecs, and Microsoft Teams Direct Routing. |
| Flow | Build call flows for incoming calls in a visual editor, without code. |
| SMS Marketing | Send SMS campaigns to contact lists from the Console. |
| Client Libraries | The Node.js and .NET libraries, and how to call the REST API from any other language. |
Help, pricing, and status
- Help. For a problem or a how-to question, search the Help Center, or contact support.
- Pricing. Our prices are published. A number has a monthly fee, and an SMS is charged by the segment. Cloud Voice billing explains how calls are charged.
- Status. enfonica.status.io shows the live status of each service.
- Network. Enfonica runs across three Google Cloud zones in Sydney. See our network.
- Terms and privacy. See enfonica.com/terms.
- Talk to us. For an account, volume pricing, or a question that this page doesn't answer, contact our team.