Toll-free, programmatically
Manage 1800 Numbers via API
An 1800 fleet has the same management surface as any inbound range: an inventory to list, records to read, routing to steer. The Simple Telecom API covers all three over RESTful JSON — so your toll-free numbers run as code where that pays.
- List, read, steer — via REST
- CDRs within 1–2 minutes
- Same areas as 1300 management
1800 API questions
Is managing 1800 numbers different from 1300s?
Not at the API level. The same three areas — Services, CDR, Routing Management — cover both ranges, and the patterns are identical: list inventory, read call records, steer forwarding and recording. The format differs in caller cost, not in manageability.
What can the API change about an 1800 number?
Its forwarding destinations and its recording state, programmatically. Number selection and connection happen through the availability pool and your account; everything after connection is the API's surface.
Where should a 1800 integration start?
The same place every integration starts: read-only. A scheduled CDR pull gives per-number reporting for the whole fleet before any write-side change is attempted — the walkthrough is in our getting-started guide.
A 1800 number is a toll-free promise on the front and a routing table behind it — and the back of the house is identical to every other inbound range we host. Managing 1800 numbers via API means the same three areas, the same patterns and the same disciplines as managing 1300s, applied to the format your customers know as free. This page is the 1800-side view.
The management surface
Three API areas, described on the API page:
- Services — your active 1800 numbers, listed programmatically: the inventory every automation reconciles against.
- CDR — call detail records per number, appearing within roughly one to two minutes of each call completing. The data behind per-line reporting and per-second billing reconciliation.
- Routing Management — control of call forwarding and recording: where each toll-free line lands, and whether it captures audio.
All of it is RESTful JSON with bearer-token authentication, rate limited for production — PHP, JavaScript, Python, Ruby, Go, anything that speaks HTTP.
The 1800-specific patterns
The patterns are shared with the 1300 range — manage 1300 numbers via API covers them — but two matter more on toll-free lines:
- Cost vigilance. On the 1800 format the owner funds every call, so the CDR feed doubles as a cost monitor: per-number volumes and durations reconcile exactly against billing, and anomalies surface in hours, not invoice cycles.
- Campaign lifecycle routing. Toll-free numbers in advertising change destinations with campaigns; the Routing Management area applies the changes per the patterns in API call routing.
Starting honestly
Read-only first: a nightly CDR pull across the fleet, per the walkthrough in getting started with the API. Numbers first, actually: standard 1800s from $10 a month, phonewords by lease, searchable on available numbers, with rates on the pricing page.
Fleets and single lines alike
Get 1800 numbers worth automating
Toll-free numbers from $10 a month, searchable free — routing and records under programmatic control.