¶ Generating Call Statistics with the V1 Calls API
This guide explains how to use the VOCPhone Portal V1 Call APIs to retrieve call data and generate statistics such as total outbound/inbound calls, total duration, total cost, and missed call counts.
¶ Authentication
All V1 call endpoints require JWT authentication. Include the token in the Authorization header
The authenticated user's account ID is automatically used to scope all queries — you only see calls belonging to your account.
¶ Endpoints
¶ 1. Outbound Calls
¶ Parameters
¶ Response Fields
¶ Example Response
¶ 2. Inbound Calls
¶ Parameters
How type filtering works:
Inbound — returns inbound calls where the destination does not start with 611300 (standard inbound)
Inbound-1300 — returns inbound calls where the destination starts with 611300 (1300 number calls)
¶ Note: The inbound endpoint returns total time seconds (which includes ring time) but does not return destination geo tag or caller id name — unlike the outbound endpoint.
¶ Generating Statistics
¶ Fetching All Pages
Both endpoints are paginated. To compute statistics across a full date range, you must iterate through all pages
Total Outbound and Inbound Calls
¶ Tip: If you only need the count without fetching all records, make a single request with perPage=1 and read the total field from the response.
¶ Total Duration and Cost
¶ Missed Calls (Inbound)
A call is considered missed when billed seconds is 0 — meaning the call was never answered.
¶ Per-Extension Breakdown
¶ 1300 Number Statistics
¶ Average Call Duration
Ring Time (Inbound Only)
The inbound endpoint returns total time seconds alongside billed seconds. The difference is the ring time
.png)
¶ Important Notes
-
Dates are in AEST — The server stores all timestamps in Australia/Sydney timezone. Provide date filters in AEST.
-
Default date range — If dateFrom/dateTo are omitted, both endpoints default to the current calendar month.
-
Pagination limit — Maximum perPage is 50. Requests exceeding this will be rejected.
-
Cost field difference — Outbound uses call_cost directly; inbound maps tflc_call_charge as call_cost. Both are returned as call_cost in the response.
-
Rate limiting — When iterating pages, add reasonable delays between requests to avoid rate limits.