The reference card
Simple Telecom API at a Glance
The whole API on one card: three areas, RESTful JSON over HTTPS with bearer tokens, rate limits like any production service — and the four integration patterns teams actually build. The deep detail stays on the API page, where it belongs.
- Three areas, one card
- RESTful JSON, bearer tokens
- Four build patterns
API questions
What are the three areas of the API?
Services — a programmatic listing of your active numbers; CDR — call detail records, appearing within about one to two minutes of each call completing; and Routing Management — programmatic control of call forwarding and recording.
What technology does it use?
RESTful JSON over HTTPS with bearer-token authentication, rate limited for production use — callable from PHP, JavaScript, Python, Ruby, Go or any language that speaks HTTP.
Which area should I integrate first?
CDR, read-only: a nightly pull of call records into your reporting stack. It cannot misroute anything, and it delivers the calls-per-number picture from the first week — the walkthrough is in our getting-started guide.
Some pages explain; this one is a card. The Simple Telecom API on one page — the areas, the technology, the patterns — for the developer or founder who wants the shape of the thing before the documentation. Every claim here traces to the API page, which stays the canonical source.
The three areas
| Area | What it does | Read or write | |---|---|---| | Services | Lists your active numbers | Read | | CDR | Returns call detail records (fresh within ~1–2 minutes) | Read | | Routing Management | Controls call forwarding and recording | Write |
The technology
RESTful JSON over HTTPS, bearer-token authentication in the Authorization header, rate limited for production. Any HTTP-speaking language integrates — the endpoint detail lives on the API page, and the authentication handling rules are in API authentication.
The four build patterns
- Nightly CDR pull. The read-only starter: call records into your reporting stack, value from week one. Walkthrough in getting started with the API.
- Analytics joins. CDR data correlated with your orders, tickets or campaigns — the custom views a console cannot build for you. Patterns in call analytics through the API.
- Routing automation. Rosters, monitors and campaign calendars making the routing changes they already know about. Patterns in API call routing.
- Fleet management. Listing, records and control across many numbers, with per-number reporting and reconciliation — the fleet view is in manage 1300 numbers via API.
The boundaries
The API manages your inbound services — it does not place outbound calls or provision global virtual numbers. And it needs services to manage: standard 1300 and 1800 numbers from $10 a month, tracking numbers from $5, all searchable on available numbers, rates on the pricing page.
From the card to the build
Get numbers worth integrating
1300 and 1800 numbers from $10 a month, tracking from $5 — searchable free in the live pool.