Skip to main content
GET
Get Billing Usage Summary

Date Handling

Both start_date and end_date accept two formats:
  • Date only (YYYY-MM-DD) — start_date defaults to midnight UTC, end_date defaults to 23:59:59 UTC. Simplest option when you want full-day UTC boundaries.
  • Full ISO timestamp (YYYY-MM-DDTHH:mm:ssZ) — Exact UTC boundaries. Use this when you need timezone-specific alignment.
You can mix formats (e.g., date-only for start, ISO timestamp for end).

Timezone-Aligned Example

To query “February in US Eastern Time”, send:

Notes

  • RVM has two-part pricing: a per-drop fee plus a per-hour duration fee — both are included in rvm.total_cost
  • All costs are in USD and rounded to 2 decimal places

Authorizations

collectwise_key
string
header
required

Query Parameters

start_date
string
required

Start of date range. Accepts YYYY-MM-DD (defaults to 00:00:00 UTC) or a full ISO 8601 UTC timestamp like 2025-02-01T05:00:00Z

end_date
string
required

End of date range. Accepts YYYY-MM-DD (defaults to 23:59:59 UTC) or a full ISO 8601 UTC timestamp like 2025-02-28T04:59:59Z

Response

Usage summary retrieved successfully

object
string

Object type identifier

Example:

"billing.usage_summary"

organization
string

Your organization name

period
object
sms
object
mms
object
email
object
rvm
object

Ringless Voicemail — has two-part pricing (per-drop + per-hour duration)

calls_outbound
object
calls_inbound
object
total_cost
number

Total cost across all channels in USD

currency
string

Currency code

Example:

"usd"