Billing data reference
Reference for all cost fields, billing categories, subcategories, and aggregation dimensions available through the Billing Usage API.
Cost fields
These fields appear in the Billing Usage API response for each aggregation combination.
| Field | Description | Format |
|---|---|---|
| Unit | Measurement basis for billing (message, message part, session, minute, monthly active user) | String |
| Unit price | Cost per unit in standard currency units | Decimal |
| Quantity | Total number of billed units. The value may be a whole number, or a decimal. | Number |
| Total per unit | Total charge in standard currency units (unit price multiplied by quantity) | Decimal |
| Currency | Billing currency (ISO 4217) | String (for example, USD, EUR, GBP) |
Categories
| Code | Display name |
|---|---|
SMS | SMS |
SMS_OPERATOR_FEE | SMS - Operator Fee (US carrier surcharges) |
MMS | MMS |
MMS_OPERATOR_FEE | MMS - Operator Fee |
EMAIL | |
RCS | RCS |
WHATSAPP | |
VIBER | Viber |
MOBILE_PUSH | Mobile Push |
NUMBER_LOOKUP | Number Lookup |
CARRIER_LOOKUP | Carrier Lookup |
EMAIL_VALIDATION | Email Validation |
AGENTOS | AgentOS |
NOTEUS operator fees (
SMS_OPERATOR_FEE, MMS_OPERATOR_FEE) are carrier pass-through costs itemized separately from base message costs.Subcategories
Some categories have subcategories that provide further breakdown of service variants.
| Code | Category | Display name | Description |
|---|---|---|---|
VIBER_BM | Viber | Viber BM | Viber Business Messages |
VIBER_BOTS | Viber | Viber Bots | Viber Bots |
Dimensions
The Behavior column uses the following values:
| Behavior | Meaning |
|---|---|
| Auto-added default | Added automatically to aggregateBy if no dimension from this pair is specified |
| Selectable | Add explicitly to aggregateBy |
| Enrichment | Adds extra columns alongside an existing dimension without creating new data groupings |
| Data group | Dimension | API code | Description | Applicability | Behavior |
|---|---|---|---|---|---|
| Account | Account | ACCOUNT_NAME | Infobip account name |  All channels and services | Auto-added default |
| Account | Account key | ACCOUNT_KEY | Hashed account identifier for programmatic processing | All channels and services | Selectable |
| Account | Username | USER_NAME | Unique username of the user who initiated the traffic | All channels and services | Selectable |
| Account | Application | APPLICATION_ID | Unique identifier assigned to an application within the Infobip multitenant platform | All channels Email ValidationNumber LookupMobile Identity | Selectable |
| Account | Entity | ENTITY_ID | Unique identifier assigned to an entity within the Infobip multitenant platform | All channelsEmail ValidationNumber LookupMobile Identity | Selectable |
| Service and traffic | Category | CATEGORY_NAME | The communication channel or service display name (for example, SMS, WhatsApp, RCS) | All channels and services | Selectable |
| Service and traffic | Category code | CATEGORY_CODE | The category enum code used for filtering and grouping. See Categories. | All channels and services | Auto-added default |
| 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 Identity | Selectable |
| Service and traffic | Traffic type | TRAFFIC_TYPE | Additional traffic categorization (for example, RCS single, basic, A2P, P2A). | WhatsAppRCSViber Business Messages | Selectable |
| Service and traffic | Subcategory name | SUBCATEGORY_NAME | Service variant display name (for example, Viber Business Messages) | Viber | Selectable |
| Service and traffic | Subcategory code | SUBCATEGORY_CODE | Service variant enum code (for example, VIBER_BM). See Subcategories. | Viber | Selectable |
| Sender | Sender | SENDER | The sender, number, or domain used to send traffic | All channelsEmail ValidationNumber LookupMobile Identity | Selectable |
| Sender | Sender type | SENDER_TYPE | Specifies the type of sender (VLN, short code, alphanumeric, toll-free, 10DLC, domain) | SMSMMS | Selectable |
| Geography and network | Country | COUNTRY_NAME | The name of the destination country where traffic was sent | SMSRCSWhatsAppViber Business MessagesNumber Lookup | Selectable. Enrichments: Country code, Country prefix |
| Geography and network | Country code | COUNTRY_CODE | The official two-letter country code (ISO 3166-1 alpha-2) | SMSRCSWhatsAppViber Business MessagesNumber Lookup | Enrichment |
| Geography and network | Network | NETWORK_NAME | The name of the mobile network operator, if available | SMSRCSNumber Lookup | Selectable. Enrichment: Network code |
| Geography and network | Network code | NORM_NET_CODE | MCC+MNC code identifying the mobile network operator | SMSRCSNumber Lookup | Enrichment |
| Geography and network | Country prefix | COUNTRY_PREFIX | International dialing prefix for the destination country | SMSRCSWhatsAppViber Business MessagesNumber Lookup | Enrichment |
| Campaign and message metadata | Campaign ID | CAMPAIGN_ID | The unique identifier for a Broadcast or Journey | All channelsMobile Identity | Selectable |
| Campaign and message metadata | Campaign reference | CAMPAIGN_REFERENCE | The campaign reference ID for traffic sent over Infobip APIs or integrations | All channelsEmail ValidationNumber LookupMobile Identity | Selectable |
| Campaign and message metadata | Template ID | TEMPLATE_ID | The unique identifier for a WhatsApp template | WhatsApp | Selectable |
| Date grouping | Day | DAY | The date representing the aggregated data for a single day | All channels and services | Selectable |
| Date grouping | Month | MONTH | The month representing the aggregated data | All channels and services | Selectable |
Related pages
Query billing data
Build and send a billing usage query and handle the callback response.
Billing Usage API
Overview of the API, supported channels, and data finalization behavior.