If you are comparing your call logs (through either your Console logs or the API /Calls List) against your call usage (through either the Console Usage page or the API Usage/Records) there are a number of considerations to keep in mind for a proper comparison.
In order to match call logs with Usage API, keep these points in mind:
count in the usage API is the number of events (# of calls, in this case)usage returned via the Usage API is the total number of BILLED minutes per call, rounded to duration defined by the pricing model ( minimum and round quantity )usage console, call usage is displayed separately as "voice minutes" and "client minutes". Since client calls are a separate entity in the usage API definition, you will need to get the usage for calls and client calls separately.Failed, or Busy, are not billed and the usage API will not add the usage from those calls.< 1st day of next month as the end boundary (do not use <= last day of this month).| Parameter | Usage (API and Console) | Logs (API and Console) | How to Reconcile Usage and Logs |
|---|---|---|---|
| Duration of Calls | Measured in minutes | Measured in seconds | Round up duration in your call logs to the nearest minute to match the usage logs. |
| Voice vs. Client Calls | Client and Voice calls are treated separately | Client and Voice calls are merged | Add your voice and client usage minutes together to match the combined logs. |
| Call Billing Time | The start date of the call is the date we use to attribute it | N/A | If a call begins in one month and ends in another, usage would be attributed to the first month.. |
| Call Time Zone | Calls timezone is always in UTC | Calls will be in UTC or your local time zone | If your logs are in your local time zone, normalize them to UTC to match usage. |