Docs, as a product
CallTrackingMetrics API Documentation: Evaluating Any Vendor's Docs
We are not CallTrackingMetrics, so their documentation lives on their site — we will not paraphrase it. What we can offer is the ten-minute evaluation that tells you whether any vendor's API documentation is buildable, and where our own lives.
- No secondhand docs
- The ten-minute doc check
- Our API, documented plainly
Documentation questions
Where is CallTrackingMetrics' API documentation?
On their own developer site — we are a separate Australian company and will not mirror or summarise their docs, which change with their product. Their official developer portal is the only current source.
How do I judge API documentation quickly?
Four checks: a working authentication example, one complete end-to-end flow for the read you need, clear rate-limit and error behaviour, and a changelog. If any of the four is missing, budget for discovery work the docs did not do.
Where is your API documentation?
On our API page: the three areas — Services, CDR, Routing Management — with authentication and behaviour described. It documents a smaller surface honestly rather than a large one vaguely.
Documentation searches are developer diligence: before touching a vendor, you want to see how they document. For CallTrackingMetrics — a US platform, not us — the answer lives on their developer site, and we will not paraphrase it: summaries of documentation rot faster than the documentation. What this page offers instead is the ten-minute evaluation that works on any vendor’s docs, including ours, and the map of what ours covers.
The ten-minute documentation check
Four things to find, timed:
- A working authentication example — two minutes. If you cannot see exactly how a request authenticates, stop; everything after is speculation.
- One complete end-to-end flow — three minutes. The docs should walk your primary read (for call tracking, fetching call records) start to finish, with real response shapes.
- Rate limits and error behaviour — two minutes. Production integrations live and die here; absent limits are a promise of surprise throttling.
- A changelog — three minutes. Documentation that never updates is documentation you cannot trust next quarter.
Missing any of the four is not disqualifying — it is a budgeting signal: the discovery work the docs skipped will land on your sprint.
What our API documentation covers
Ours is a deliberately small surface, documented plainly on the API page: three areas — Services (list your numbers), CDR (call detail records, appearing within roughly one to two minutes of a call completing), and Routing Management (forwarding and recording control) — over RESTful JSON with bearer-token authentication, rate limited for production. The integration patterns built on it are mapped in telecom API integration, with the starter build in getting started with the API, and the product described on our call tracking page.
The honest scope note
A small documented surface is a choice, not a lack: we manage inbound number services, and the docs cover exactly that. If your integration needs the breadth of a session-level platform — dynamic insertion APIs, conversation analytics endpoints — those vendors’ documentation is the right place for the ten-minute check. For number-based tracking on Australian infrastructure, ours holds up: the rates behind the records are on the pricing page.
A smaller surface, documented
An API sized to be readable
Three areas, RESTful JSON, bearer tokens — number-based tracking from $5 a month per number.