Call Recording API: Enable and Disable Recording Programmatically
Control Call Recording for Your Services via the Simple Telecom Routing API
Key Call Recording API Features
- Enable or disable call recording per service via a single API call
- Toggle recording instantly — no web console login required
- Fine-grained control over which numbers record calls
- Integrate recording policies with compliance workflows
- Access recordings through your Simple Telecom console
What Is the Call Recording API?
The Simple Telecom Call Recording API lets you enable or disable call recording for your services programmatically. Instead of logging into the web console to toggle recording settings, you can manage recording policies through a simple API call — making it easy to integrate recording controls with your compliance systems, staff scheduling, or automated workflows.
Call recording is a critical feature for many Australian businesses. It’s used for quality assurance, staff training, compliance with industry regulations, and resolving disputes. The API gives you the flexibility to turn recording on or off as needed, per service, without manual intervention. This is particularly valuable for businesses that need different recording policies for different departments, campaigns, or time periods.
Recording is managed through the Routing Management API, specifically the PUT /api/services/{service_id}/routing/recording endpoint. It’s a simple boolean toggle — send {"enabled": true} to start recording, or {"enabled": false} to stop. The change takes effect immediately.
How the Call Recording API Works
Using the call recording API is straightforward. You need two things: a valid API token with Bearer authentication, and the service ID of the number you want to manage. The service ID is the numeric identifier for your 1300, 1800, or CTN number, which you can retrieve from the Services API (GET /api/services).
To enable call recording, send a PUT request to https://api.simpletelecom.com/v1/api/services/{service_id}/routing/recording with a JSON body containing {"enabled": true}. The API responds with a success message and the current recording status. To disable recording, send the same request with {"enabled": false}.
The response includes both a confirmation message and the current call recording configuration, so you can verify the change was applied correctly. The API returns a standard 200 OK response on success, or an appropriate error code if something goes wrong — such as 401 Unauthorized for invalid tokens or 404 Not Found for invalid service IDs.
Why Manage Call Recording Programmatically?
Programmatic call recording management opens up powerful automation possibilities. For compliance-driven businesses, you can integrate recording policies with your HR or compliance systems. When a new staff member is onboarded, automatically enable recording on their assigned number. When they complete training, disable it or adjust the policy.
For marketing teams, you might want recording enabled only during specific campaign periods. Use a scheduling system to enable recording at campaign launch and disable it at campaign end — no manual intervention needed. This ensures you’re always recording the calls that matter while respecting privacy when recording isn’t necessary.
For call centres with fluctuating staffing, you can automatically enable recording during peak hours or when new agents are on shift, and disable it during quiet periods or for experienced teams. This gives you complete control over your recording policies without needing a dedicated admin to manage the web console.
Compliance and Privacy Considerations
Australian businesses using call recording must comply with the Privacy Act 1988 and Australian Privacy Principles (APPs). This requires informing callers that calls may be recorded, securing recorded data appropriately, and providing access to recordings when requested. The Call Recording API helps you implement these requirements by giving you granular control over which services record calls.
You can configure specific services to record only when needed, reducing the amount of recorded data you need to store and manage. This is particularly important for businesses that handle sensitive information or have varying recording requirements across different departments.
Remember that enabling call recording on a service will record all incoming calls to that number. Ensure your callers are informed about recording through an automated message or your IVR greeting. Consult legal advice to ensure your recording practices comply with your specific regulatory requirements.
Integrating Call Recording with Your Workflows
The Call Recording API integrates naturally with common business workflows. Here are some practical examples:
Staff Training Pipeline: When a new sales representative joins, automatically enable recording on their assigned number. After their training period is complete, disable recording or keep it enabled for ongoing quality assurance. This can be triggered from your HR system or learning management platform.
Campaign-Specific Recording: For marketing campaigns that require call recording for attribution and quality analysis, enable recording at campaign launch and disable it at campaign end. This ensures you capture the data you need without recording unnecessary calls.
Compliance Auditing: Schedule periodic recording audits by enabling recording for specific services during audit periods, then disabling it when the audit is complete. This minimises the volume of recorded data while ensuring you have the data needed for compliance reviews.
Best Practices for Using the Call Recording API
When using the Call Recording API, follow these best practices to ensure reliable operation. First, always check the current recording status before making changes. You can retrieve this by calling the GET routing endpoint (GET /api/services/{service_id}/routing), which returns the complete routing configuration including the current recording status.
Second, implement error handling in your integration. The API returns standard HTTP error codes and JSON error messages. Handle 401 (unauthorized) by refreshing your token, 404 (not found) by verifying the service ID, and rate limiting by implementing backoff logic.
Third, log all recording status changes for audit purposes. Keep a record of when recording was enabled or disabled and by which process or user. This creates an audit trail that can be invaluable for compliance reviews or internal investigations.
Frequently Asked Questions
Frequently Asked Questions About the Call Recording API
How quickly does a recording change take effect?
Changes take effect immediately. Once you receive a success response from the API, the new recording setting is applied to all incoming calls to that service.
Can I enable recording on some numbers and not others?
Yes. The recording setting is per-service, so you can have different recording policies for different numbers. This is ideal for businesses that need recording on sales lines but not on support lines, for example.
Do I need to notify callers that calls are being recorded?
Yes. Australian privacy laws require you to inform callers that calls may be recorded. This is typically done through an automated message at the start of the call or through your IVR greeting.
Where are call recordings stored?
Call recordings are stored securely and are accessible through your Simple Telecom console. Contact support for details about recording retention periods and storage policies.
Can I access recordings through the API?
The current API supports enabling and disabling recording. Recordings themselves are accessed through the Simple Telecom web console. Check the API documentation for updates on additional recording-related endpoints.
With Simple1300Numbers’ Call Recording API, you can programmatically manage call recordings to suit your business needs—whether you’re operating domestically or handling calls from 1800 numbers from overseas. This level of control helps Australian businesses maintain compliance and improve customer service quality. Understanding how to enable and disable recording on demand works seamlessly alongside our flexible pricing model, so you can choose the right solution based on what a 1800 number costs for your operation.
