Fleet management, programmatically
Manage 1300 Numbers via API
One 1300 number is console work. A fleet of them — per campaign, per region, per client — is where manual management stops scaling, and where the Simple Telecom API takes over: list, record-read, route, all programmatically.
- List, read, route — via REST
- CDRs within 1–2 minutes
- Built for fleets
API management questions
What management tasks does the API automate?
Three kinds: inventory (the Services area lists your active numbers), data (the CDR area retrieves call records within a couple of minutes of each call), and control (the Routing Management area changes forwarding and toggles recording).
Is the API only for large fleets?
No — the first useful automation is a single number's nightly call-report pull. The API earns its keep as numbers multiply, but nothing about it requires scale to start.
How do I start managing my numbers via API?
Host the numbers with us, get bearer-token credentials as described on the API page, and begin with a read: pull the Services listing, then the CDR records. Write-side changes — routing — come once the read side is trusted.
Hand-managing a 1300 number is a two-minute console task. Hand-managing thirty of them, per campaign, per region, per client, is a part-time job with mistakes built in. The Simple Telecom API exists above that threshold: it turns listing, call-data retrieval and routing changes into programmatic operations over your own services. This page maps which management tasks automate well and how to start. The fleet itself is a set of virtual numbers, none of them wired to a line, which is what makes programmatic control natural; virtual 1300 numbers explains the delivery model.
The three management jobs the API covers
The API organises into three areas, described on the API page:
- Inventory — Services. A programmatic listing of your active numbers. For fleet managers this is the reconciliation baseline: what exists, right now, without opening a console.
- Data — CDR. Call detail records per number, appearing within about one to two minutes of each call completing. Per-number reporting, billing reconciliation and campaign attribution all pull from here.
- Control — Routing Management. Call forwarding and recording changes, applied programmatically. When a campaign ends, a region re-points or a policy window opens, your systems make the change instead of a human remembering to.
Everything is RESTful JSON with bearer-token authentication, rate limited for production use — PHP, JavaScript, Python, Ruby, Go or anything that speaks HTTP.
The management patterns that pay
- Automated reporting per number. A scheduled CDR pull lands per-number call data where your team reads it. The highest-value, lowest-risk integration — described in getting started with the API.
- Reconciliation. Match billed charges against CDR records — per-second billing makes the check exact.
- Lifecycle routing. Campaign numbers re-pointed at launch and teardown by the campaign calendar itself.
- Audit trails. A factual per-call history across the whole fleet, retained in your own systems.
The control-side patterns are walked through in API call routing, with the CDR data above feeding the analytics layer.
Starting small and honest
Begin with one number and one read: pull its CDRs nightly. Add numbers as campaigns justify them: standard 1300s from $10 a month, tracking numbers from $5, all searchable on available numbers. The product behind the fleet is on 1300 numbers.
Numbers first
Build the fleet, then automate it
Standard 1300s from $10 a month, tracking numbers from $5 — searchable free in the live pool.