Skip to main content
GET
Get usage statistics for the API key's company
Retrieves usage statistics for the API key’s company: total minutes or credits consumed, the number of conversations, and a breakdown by cost key. Behaviour differs between regular API keys and ATS integration keys, and between companies on the minutes and credits billing systems.

Overview

The get usage endpoint provides read-only access to billing and usage information. For regular API keys, it returns usage for the associated company. For ATS keys, it returns aggregated usage across all companies managed by that ATS key. Each company in the response carries a billingSystem field indicating which unit it is billed in:
  • "minutes" — legacy call-minutes accounting. totalMinutesUsed and breakdownByCostKey[].minutesUsed are populated; totalCreditsUsed and creditsUsed are omitted entirely.
  • "credits" — per-product credits accounting. totalCreditsUsed and breakdownByCostKey[].creditsUsed are populated; totalMinutesUsed and minutesUsed are omitted entirely.

Date Range Parameters

You can specify a date range for usage data:
  • start (optional): Start date in ISO 8601 format (defaults to 30 days ago)
  • end (optional): End date in ISO 8601 format (defaults to current date)

Regular API Keys (Minutes-Based Company)

For minutes-based companies, the response reports usage in call minutes:

Regular API Keys (Credits-Based Company)

For credits-based companies, the response reports usage in credits. Minutes-related fields are omitted entirely:

ATS Integration Keys

For ATS keys, the response includes aggregated usage across all companies managed by the ATS.

Use Cases

  • Usage Monitoring: Track minutes or credits spent, and how many conversations ran
  • Cost Tracking: Monitor usage against subscription limits
  • Billing Reporting: Generate usage reports for billing purposes
  • Multi-Tenant Analytics: Track usage per company for ATS platforms

Response Structure

The response includes:
  • companies: Array of company-level usage (single item for regular keys, multiple for ATS keys).
  • billingSystem (per company): Either "minutes" or "credits".
  • totalMinutesUsed: Total call minutes consumed in the period. Present when at least one company in scope is on the minutes billing system; omitted otherwise.
  • totalCreditsUsed: Total credits consumed in the period. Present when at least one company in scope is on the credits billing system; omitted otherwise.
  • totalInterviews: How many conversations ran. The field keeps its original name — see Resource names — as does the interview_minutes cost key.
  • breakdownByCostKey: Array of usage buckets. Each entry includes costKey and events, plus minutesUsed or creditsUsed depending on the company’s billing system. Cross-system fields are never present in a per-company breakdown.

Monitoring Usage

Required Scope

Required Scope: read:billing is required to access this endpoint. Ensure your API key has this scope enabled.

Billing Resource Guide

Comprehensive guide to billing, usage tracking, and subscription management

Scopes & Permissions

Learn about required scopes

ATS Integration

Understand ATS key usage aggregation

Authorizations

Authorization
string
header
required

API key for authentication using Bearer scheme

Query Parameters

start
string

Start of the billing period (inclusive), ISO 8601

Example:

"2025-01-01T00:00:00.000Z"

end
string

End of the billing period (exclusive), ISO 8601

Example:

"2025-01-31T00:00:00.000Z"

companyId
string

Required for ATS API keys to specify which company to access. Ignored for standard company API keys.

Response

200 - application/json
companies
object[]
required

Per-company usage details for all companies visible to this ATS key

totalInterviews
number
required

How many conversations ran across all companies. The field keeps its original name.

Example:

80

breakdownByCostKey
object[]
required

Global breakdown of usage by cost key across all companies

totalMinutesUsed
number | null

Total minutes used across all minutes-based companies in the selected period. Omitted entirely when no managed company is on the minutes billing system.

Example:

1200

totalCreditsUsed
number | null

Total credits used across all credits-based companies in the selected period. Omitted entirely when no managed company is on the credits billing system.

Example:

3000.5