Manage 1300 Numbers via API: Routing, CDRs and Service Management
Programmatically Manage Your 1300 Number Configuration with the Simple Telecom API
Key 1300 Number API Features
- List all 1300 services on your account with status and service ID
- Retrieve call detail records for any 1300 number
- Manage call routing and forwarding for 1300 services
- Enable or disable call recording on 1300 numbers
- Integrate 1300 number data with CRM and analytics systems
Managing 1300 Numbers with the Simple Telecom API
If you run a business with 1300 numbers, you know how important they are to your customer communication. But managing multiple 1300 numbers — updating routing, monitoring call volumes, tracking costs — can be time-consuming if you’re doing it manually through the web console. The Simple Telecom API gives you programmatic control over your 1300 numbers, automating the management tasks that eat up your time.
The API covers the full lifecycle of 1300 number management. Use the Services API to list all your 1300 services and their statuses. Use the CDR API to retrieve call records for each number — see who called, when, for how long, and at what cost. Use the Routing API to manage where calls are forwarded, set ring durations, and toggle call recording.
For Australian businesses with multiple 1300 numbers — perhaps one for sales, one for support, and others for specific campaigns — the API provides a single interface for managing all of them. You can query, update, and monitor every 1300 number on your account without switching between different screens or tabs.
Finding and Listing Your 1300 Numbers
The Services API (GET /api/services) is your starting point for managing 1300 numbers. It returns a list of all active services on your account, including your 1300 numbers. Each entry includes the service_id (a unique numeric identifier), service_number (the actual 1300 number), service_type (which will be ‘1300’ for your 1300 numbers), and status (always ‘active’ for active services).
You can use this endpoint to discover all your 1300 numbers automatically. This is particularly useful if you have many numbers and don’t want to maintain a separate list. The API supports pagination with page and page_size parameters, and results can be sorted in ascending or descending order by service number.
Once you have the service ID for a 1300 number, you can use it to manage routing or retrieve CDRs. The service number is used as the primary identifier when querying call records.
Retrieving Call Data for 1300 Numbers
The CDR API (GET /api/cdrs) lets you retrieve call detail records for any of your 1300 numbers. You need the service number (the actual 1300 number, like 1300858751) as a required parameter. You can also filter by date range, paginate results, and sort by start time.
Each CDR record includes rich data about a single call: the start and end time in ISO 8601 UTC format, call duration in seconds, the caller’s number (source), the destination the call was forwarded to, and the cost charged to your account in AUD. This data is available within 1–2 minutes of a call completing, giving you near-real-time visibility into your 1300 number activity.
For businesses using 1300 numbers for marketing campaigns, this data is invaluable. Query the CDR API for each campaign-specific number to see call volumes, calculate cost-per-lead, and track campaign performance alongside your digital metrics.
Managing 1300 Number Routing
The Routing Management API gives you full control over where calls to your 1300 numbers are directed. Use GET /api/services/{service_id}/routing to view the current routing configuration, including all forwarding numbers and call recording settings.
To add a new forwarding destination — for example, a new staff member’s mobile — use POST /api/services/{service_id}/routing/forwarding with the phone number, an optional display name, and a ring duration. To update or remove existing forwarding numbers, use the PUT and DELETE endpoints respectively.
This is particularly useful for 1300 numbers that serve different purposes. A sales 1300 number might route to the sales team’s mobiles, while a support number routes to the support team’s desk phones. You can manage each number’s routing independently, ensuring calls go to the right people.
Automating 1300 Number Management
Once you’re comfortable with the API endpoints, you can build automation around your 1300 number management. Here are some practical examples:
Automated Routing Updates: Schedule routing changes for your 1300 numbers. At 9am, route calls to the day team’s mobiles. At 5pm, switch to after-hours voicemail. This can be done with a simple cron job that calls the Routing API at the appropriate times.
Campaign Performance Reports: Run a weekly script that queries the CDR API for each campaign-specific 1300 number, calculates call volumes and costs, and emails a report to stakeholders. No manual data collection needed.
CRM Integration: Automatically log every call to your 1300 numbers in your CRM. Query the CDR API every 15 minutes, identify new records, and push them to your CRM via its API. Your sales team gets a complete, up-to-date view of every prospect interaction.
Getting Started with 1300 Number API Management
Getting started is straightforward. First, ensure you have an active Simple Telecom account with 1300 numbers. Generate an API token from the console (Settings → API Access → Generate API Token). The token format is st_... and must be included in the Authorization header of every request.
Test your token by calling the Services API to list your 1300 numbers. Then try the CDR API to retrieve recent call data for one of your numbers. Finally, use the Routing API to view the current routing configuration. This three-step workflow confirms you have access to all three API areas.
Full documentation with code examples in PHP, JavaScript, and cURL is available at api.simpletelecom.com.au. For additional help, contact api-support@simpletelecom.com.au.
Frequently Asked Questions
Frequently Asked Questions About Managing 1300 Numbers via API
Can I manage all my 1300 numbers with one API token?
Yes. A single API token gives you access to all services on your account, including all your 1300 numbers. You don’t need separate tokens for each number.
Do I need a special plan for API access?
No. API access is included with your Simple Telecom 1300 number service at no additional cost. Generate your token from the console and you’re ready to go.
Can I add a new 1300 number via the API?
The current API is for managing existing services — viewing CDRs, managing routing, and listing services. To purchase a new 1300 number, use the Simple Telecom website or console.
How quickly do routing changes take effect?
Changes to your 1300 number routing are applied immediately. Once you receive a success response from the API, the new routing configuration is active.
Can I share API access with my team?
Yes. You can generate unique API tokens for each team member. Each token can be revoked independently, giving you granular control over who has access.
Managing your 1300 number through our API gives you complete control over routing, call data records, and service configuration—perfect for businesses wanting seamless integration with their existing systems. Whether you’re curious about how 1300 numbers work in words or exploring cost structures like whether 1800 numbers are free of charge, our flexible platform adapts to your needs. You’ll find similar flexibility across regions too—learn more about 1800 numbers in Singapore or check coverage on networks like Gomo. With Simple1300Numbers, you get the technical control and cost-effectiveness Australian businesses deserve.
