Telecoms glossary • A
API (Application Programming Interface)
The difference between a phone system that logs a call and one that updates the customer record while you are still talking.
What is an API?in VoIP and business telephony
1. An API is a published set of instructions that lets two pieces of software exchange data and trigger actions in each other. In telephony it is how a phone system pushes a caller’s number into your CRM, opens the right record on screen, writes the call back as an activity, and starts a call when someone clicks a number.
2. Most business phone APIs are REST APIs: your software sends an HTTPS request and receives structured data back. Webhooks run the other way, with the phone system posting an event to your system the instant a call starts, is answered or ends.
What an API actually buys you
Nobody buys an API. They buy the four or five things an API makes possible, and those are the items to put in a quote request.
- Screen pop
- The caller’s record opens on the agent’s screen before the phone is answered. The single biggest handling time saving in most offices, because the alternative is asking for an account number.
- Click to dial
- A number in the CRM or browser becomes a link. The extension dials it. Removes mis-dialled digits and the two minutes an hour they cost.
- Activity write back
- Call time, duration, direction, outcome and a link to the recording land on the customer record without anyone typing them.
- Dialler control
- Your system feeds a list to the platform and reads results back. This is what turns a CRM campaign into an outbound calling shift.
- Event automation
- A missed call on the sales number raises a task, sends an SMS or pings a channel. Built on webhooks rather than polling, so it fires in seconds.
What South African providers publish
Integration claims are easy to make and easy to check. Two examples of what documented looks like in this market, verified against the providers’ own pages in August 2026.
Euphoria Telecom publishes a documented REST API and lists out of the box integrations with Zendesk, Zoho, Freshdesk, Microsoft Teams and the Excalibur collections platform, with custom work quoted per integration. Telviva lists Salesforce, Zendesk and Zoho, plus Microsoft and Google calendars and address books, and states that legacy or in-house CRMs can be connected.
Those are examples, not a shortlist. The point is that both put the platform names and the API in writing, on a public page, which is the standard the rest of a shortlist should be held to. See how the platforms compare on features and price side by side.
Questions that separate an open API from a brochure one
-
Where are the docs, and can I read them now
Public documentation you can open without signing anything is the strongest signal. Documentation behind an NDA usually means the API exists but is not a product.
-
Is there a test environment
A sandbox and test credentials mean other people have built against it. No sandbox means your developer will be testing on your live phone system.
-
What are the rate limits
Ask for requests per minute in writing. A screen pop that throttles at peak is worse than no screen pop, because agents stop trusting it.
-
Who builds it and who owns it afterwards
If the provider builds the integration, establish whether it is a once off fee or a monthly line, and whether the code and credentials leave with you.
-
What breaks when the contract ends
Integrations are usually the reason a migration overruns. Know what has to be rebuilt before the integration becomes the reason you cannot switch.
Read the integration line on the quote
There is a difference between a native integration, listed and supported by the provider, and an API you may build against at your own cost. Both appear on quotes as integration ready. Ask which one you are buying, and whether support covers the connector when it stops working.
If your CRM is a South African vertical package, a practice management or dealer system, assume no native connector exists and price a custom build. That is a project with a developer and a scope, not a checkbox on a plan.
About this entry
Definitions are written for South African business buyers and checked against primary sources – provider documentation, standards bodies and ICASA – not vendor marketing. Reviews are independent and sponsors are always disclosed. Read our editorial policy and scoring methodology.
Spotted something out of date, or think we have this wrong? Tell the editors and we will re-check it.