Recording as a switch
Call Recording API: The Toggle, Programmatically
Recording on a hosted number is a switch — on or off, per service. The Routing Management area of our API exposes that switch to your software, so recording follows your policy windows instead of a calendar reminder.
- Toggle recording per service
- Part of Routing Management
- Records surface via CDR
Recording API questions
Can the API turn call recording on and off?
Yes — the Routing Management area controls call forwarding and toggles call recording for your services, programmatically over RESTful JSON with bearer-token authentication.
Why automate a toggle?
When recording is governed by policy windows — campaigns that must be captured, lines where it is not permitted, audit periods — manual toggles rely on memory. The API lets the system that knows the window make the change too.
Where do the recordings and records surface?
Recordings attach to the service and are available through your console; the call detail records behind your reporting surface via the CDR area of the API, within a couple of minutes of each call.
Call recording on a hosted number is conceptually tiny — a switch per service — and operationally loaded: policies determine when it must be on, when it must not be, and who remembers to check. The Routing Management area of our API takes the remembering out of human hands: recording toggles become programmatic operations, applied by the systems that know the schedule. This page covers the control, the uses, and the honest boundaries.
What the control is
Call recording toggling is part of the Routing Management area — one of three API areas, alongside Services (listing your numbers) and CDR (retrieving call records). The whole API is RESTful JSON over HTTPS with bearer-token authentication, rate limited for production use; the toggle operates per service, so different lines can carry different recording states at the same moment. The area-level detail is on the API page, the canonical source this page does not fork.
The policy windows it serves
Recording requirements rarely say "always" or "never" — they say "when", and the API serves the when:
- Campaign windows. Recording enabled for a promotion period, restored at teardown.
- Line-specific policies. Sales lines recorded; internal or sensitive lines not — the states diverge without human juggling.
- Audit periods. Recording on for the review window, off afterwards, with the change itself logged in your deployment history.
- Failover companions. Alongside the forwarding changes described in API call routing, so a re-pointed line carries the right recording state too.
The honest boundaries
Two. First, the API toggles recording — it does not transcribe, analyse or store recordings in your systems; recordings attach to the service and reach you through the console, and the per-call data surfaces via the CDR area. Second, recording obligations are yours to determine — we provide the control, not compliance advice, and we will not pretend otherwise.
Getting started
Recording control needs a recorded-eligible service first: standard 1300 and 1800 numbers from $10 a month, searchable on available numbers. Start in the console — flip the switch once, confirm the playback path — then automate the schedule through the API when a real policy window exists. Rates on the pricing page; questions to contact us.
The switch behind the switch
Get numbers your policy can steer
1300 and 1800 numbers from $10 a month — recording, routing and reporting under your control.