Their API, our API, named
CallTrackingMetrics API: Whose Does What
CallTrackingMetrics is a US platform with its own API — documented on their site, not here. This page separates the two APIs a searcher might mean, and states plainly what ours covers: your call records, your routing, your numbers.
- Two APIs, disentangled
- Three areas, ours named
- Boundaries, not brochures
API questions
Is this CallTrackingMetrics' API documentation?
No — CallTrackingMetrics is a US software company and not us. Their API and its documentation live on their developer site. Our API is a different, smaller thing: programmatic access to your Australian inbound number services.
What does your API cover?
Three areas: Services lists your active numbers, CDR returns call detail records (fresh within a couple of minutes of each call), and Routing Management controls call forwarding and recording. It manages your services — it does not place calls or provision global numbers.
What can I build with it?
Read-side: automated reporting, analytics joins with your own data, anomaly alerting. Write-side, carefully: routing and recording changes driven by your systems. The patterns are mapped in our integration guide.
"CallTrackingMetrics API" names one specific thing: the developer interface of a US call tracking platform. This is not that site, and their documentation is not ours to summarise — it lives with them and changes with their product. What we can do is disentangle the two APIs a search like this sits between, and state plainly what ours covers, because for many searchers the smaller API is the one that fits.
Their API, briefly and honestly
CallTrackingMetrics is a session-level call tracking platform: dynamic number insertion, conversation analytics, contact-centre tooling. Its API, per its own documentation, exposes those capabilities to developers. We cannot and will not review it — evaluate it with the ten-minute documentation check in our docs guide, and price it at your real traffic.
Our API, named
The Simple Telecom API manages your inbound number services — the numbers behind number-based tracking. Three areas:
- Services — list your active numbers; the inventory every integration joins against.
- CDR — call detail records per number, appearing within roughly one to two minutes of each call completing: the data behind attribution and reconciliation.
- Routing Management — control of call forwarding and recording, for systems that must steer routing programmatically.
RESTful JSON over HTTPS, bearer-token authentication, rate limited — described fully on the API page, the canonical source.
Which API fits the question you are asking
If the question is keyword-level attribution — which search term produced this caller — you are in session-level territory, and their category is the honest search. If the question is campaign-level — which medium made the phone ring, at what cost — number-based call tracking answers it without session-level pricing, and the API layer feeds the records into your stack. The category split is in what call tracking software is — see also comparing call tracking competitors — the build sequence in telecom API integration, and the rates — $5 a month per tracking number, call data billed per second — on the pricing page.
Ours, documented
The API behind number-based tracking
Tracking from $5 a month per number — call records and routing control over RESTful JSON.