Billing data reference

Reference for all cost fields, billing dimensions, categories, subcategories, and traffic types available through Financial reports, the Billing Usage API, and AgentOS reports.

Cost fields

These fields apply to Financial reports and the Billing Usage API. AgentOS reports use a different cost structure; see AgentOS report for their specific fields.

Categories

Subcategories

Some categories have subcategories that provide further breakdown of service variants. In Financial reports, Subcategory is added automatically when Voice and Video is selected, and Voice and Video subcategories are grouped into Technologies and Add-ons. Flash Calls is a subcategory in its own right and does not belong to either group. Viber subcategories are available only through the Billing Usage API.

Traffic types by channel

RCS

WhatsApp

Viber Business Messages

Each Viber traffic type has a standard and a regulated variant. The REGULATED_ prefix applies to messages sent in regulated markets.

Dimensions

The Behavior column uses the following values:

Data group	Dimension	API code	Description	Applicability	Behavior
Account	Account	ACCOUNT_NAME	Infobip account name	All channels and services	Always included in Financial reports; Auto-added by default in Billing Usage API if no account dimension is specified
Account	Account key	ACCOUNT_KEY	Hashed account identifier for programmatic processing	All channels and services	Selectable in Billing Usage API
Account	Username	USER_NAME	Unique username of the user who initiated the traffic	All channels and servicesAI	Selectable
Account	Application	APPLICATION_ID	Unique identifier assigned to an application within the Infobip multitenant platform	All channelsEmail ValidationNumber LookupMobile IdentityAI	Selectable
Account	Entity	ENTITY_ID	Unique identifier assigned to an entity within the Infobip multitenant platform	All channelsEmail ValidationNumber LookupMobile IdentityAI	Selectable
Service and traffic	Category	CATEGORY_NAME	The communication channel or service display name (for example, SMS, WhatsApp, RCS)	All channels and services	Always included in Financial reports; Selectable in Billing Usage API
Service and traffic	Category code	CATEGORY_CODE	The category enum code used for filtering and grouping. See Categories.	All channels and services	Auto-added by default in Billing Usage API if no category dimension is specified
Service and traffic	Direction	DIRECTION	Indicates whether the traffic was sent to the customer (outbound) or received from the customer (inbound)	All channelsEmail ValidationNumber LookupMobile IdentityAI	Auto-added sub-dimension in Financial reports; Selectable in Billing Usage API
Service and traffic	Traffic type	TRAFFIC_TYPE	Additional traffic categorization (for example, RCS single, basic, A2P, P2A). See Traffic types by channel.	WhatsAppRCSViber Business Messages	Auto-added sub-dimension in Financial reports; Selectable in Billing Usage API
Service and traffic	Subcategory name	SUBCATEGORY_NAME	Service variant display name (for example, Viber Business Messages, Flash Calls)	ViberVoice and Video	Auto-added in Financial reports when Voice and Video is selected. Selectable in Billing Usage API.
Service and traffic	Subcategory code	SUBCATEGORY_CODE	Service variant enum code (for example, VIBER_BM, FLASH). See Subcategories.	ViberVoice and Video	Auto-added in Financial reports when Voice and Video is selected. Selectable in Billing Usage API.
Service and traffic	Billing time unit	BILLING_TIME_UNIT	The minimum billable duration (X) and rounding increment (Y) applied to a Voice or Video call, expressed as X/Y in seconds (for example, 60/60). The value is null for calls that were not established.	Voice and Video	Auto-added default. Auto-added when the VOICE_VIDEO category is present. Not applicable to subcategories billed on a different basis, such as per call or per character.
Sender	Sender	SENDER	The sender, number, or domain used to send traffic	All channelsEmail ValidationNumber LookupMobile IdentityAI	Selectable
Sender	Sender type	SENDER_TYPE	Specifies the type of sender (VLN, short code, alphanumeric, toll-free, 10DLC, domain)	SMSMMSVoice and Video	Enrichment. Available when Sender is selected. Selectable in Billing Usage API.
Geography and network	Country	COUNTRY_NAME	The name of the destination country where traffic was sent	SMSMMSRCSWhatsAppViber Business MessagesNumber LookupVoice and Video	Selectable. Enrichments: Country code, Country prefix
Geography and network	Country code	COUNTRY_CODE	The official two-letter country code (ISO 3166-1 alpha-2)	SMSMMSRCSWhatsAppViber Business MessagesNumber LookupVoice and Video	Enrichment. Available when Country is selected.
Geography and network	Network	NETWORK_NAME	The name of the network operator, if available. For non-mobile networks (fixed-line, VoIP), this field may be blank.	SMSRCSNumber LookupVoice and Video	Selectable. Enrichments: Network code
Geography and network	Network code	NORM_NET_CODE	MCC+MNC code identifying the mobile network operator. Applicable to mobile/cellular networks only. May be blank for fixed-line, VoIP, or other non-mobile networks.	SMSRCSNumber LookupVoice and Video	Enrichment in Billing Usage API
Geography and network	Country prefix	COUNTRY_PREFIX	International dialing prefix for the destination country	SMSMMSRCSWhatsAppViber Business MessagesNumber LookupVoice and Video	Enrichment in Billing Usage API
Campaign and message metadata	Campaign ID	CAMPAIGN_ID	The unique identifier for a Broadcast or Journey	All channelsAIMobile Identity	Selectable. Enrichment: Campaign name. The Billing Usage API returns the ID only.
Campaign and message metadata	Campaign reference	CAMPAIGN_REFERENCE	The campaign reference ID for traffic sent over Infobip APIs or integrations	All channelsEmail ValidationNumber LookupMobile IdentityAI	Selectable
Campaign and message metadata	Template ID	TEMPLATE_ID	The unique identifier for a WhatsApp template	WhatsApp	Selectable. Enrichment: Template name. The Billing Usage API returns the ID only.
Date grouping	Day	DAY	The date representing the aggregated data for a single day	All channels and services	Selectable. Add to break results down by day.
Date grouping	Month	MONTH	The month representing the aggregated data	All channels and services	Selectable. Add to aggregateBy when querying across multiple months in the Billing Usage API.
AgentOS (cost reports only)	Engine type	—	The AgentOS component that processed the traffic: Journeys, Human (Inbox), Chatbot, or AI Agent	AgentOS	Selectable in AgentOS reports
AgentOS (cost reports only)	Journey ID	—	The unique identifier for an Automation Studio Journey	AgentOS	Selectable in AgentOS reports

Account hierarchy and visibility

By default, Financial reports, the Billing Usage API, and AgentOS reports all return data across your full account hierarchy: your own account, related sub-accounts, and all accounts under your company. This cross-account view mirrors the invoicing structure.

This behavior is set by default and cannot be changed. If you log in as a sub-account, you see only your own account data.

To narrow results to specific accounts, use the account filter (Financial reports, AgentOS reports) or the accountKeys filter parameter (Billing Usage API).

Data scope and finalization

These constraints apply to Financial reports, the Billing Usage API, and AgentOS reports.

• Retention: Current month and up to 2 months prior
• Time zone: UTC. Custom time zones are not supported.
• Multi-data center: Data is generated and accessed per data center. Cross-data center aggregation is not supported. To determine where your accounts are hosted, contact your account manager or Support.
• Invoicing alignment: Billing data follows the same monthly cycles, currency format, and billing structure as Infobip invoices.

Data finalization [#data-finalization-data-scope-and-finalization]

• Provisional: Current month data may change until the month is finalized on the 5th of the following month, when the invoice is issued
• Why data changes: Late-arriving traffic records, retroactive volume-based discounts, and pricing adjustments
• Billing Usage API: The response includes a metadata.billingPeriods array with volumeFinalized status per month. volumeFinalized: true means unit counts are complete; prices may still change until the invoice is issued. See Response data.

Always verify against your invoice before using billing data for financial planning or billing purposes.