Metrics API
Metrics and filters
Voice and Video metrics and filters

Voice and Video metrics and filters


The Metrics API provides tools for analyzing your Voice and Video communications. You can track performance across delivery, engagement, and failure metrics for both inbound and outbound calls. Use filters to customize your queries and segment data by time, direction, network, or communication technology.

Use this page to explore all Voice-specific metrics and filters available through the Metrics API (opens in a new tab).

IMPORTANT

To ensure data accuracy and consistency, the API will only return aggregated Voice and Video data from May 15, 2025 onwards. Historical data before this date is not available.


Metrics

Use the following metrics to monitor delivery, performance, and call outcomes for Voice and Video traffic.

Delivery

Metrics nameAPI syntaxDescription
Total callsTOTAL_CALL_COUNTTotal number of calls sent to customers (outbound) and received from customers (inbound).
Total attempted outbound callsTOTAL_ATTEMPTED_CALL_COUNTTotal number of outbound call attempts initiated by the business.
Total seized callsTOTAL_SEIZED_CALL_COUNTTotal number of outbound calls that reached the recipient's device and started ringing, regardless of whether the call was answered.
Total answered callsTOTAL_ANSWERED_CALL_COUNTTotal number of calls that were successfully answered, including both inbound calls (initiated by the customer) and outbound calls (initiated by the business).
Calls processed by AMDAMD_PROCESSED_CALL_COUNTNumber of calls processed using Automated Machine Detection (AMD).
Calls answered by personANSWERED_BY_PERSON_CALL_COUNTNumber of outbound calls answered by a human.
Calls answered by voice detectionANSWERED_BY_VOICE_DETECTION_CALL_COUNTNumber of outbound calls answered by a voice detection system, such as voicemail or automated service.

Inbound

Metrics nameAPI syntaxDescription
Total received callsTOTAL_RECEIVED_CALL_COUNTTotal number of calls received from customers (inbound).

Delivery failure

Metrics nameAPI syntaxDescription
Not answeredNOT_ANSWERED_CALL_COUNTTotal number of outbound calls not answered by the recipient.
CanceledCANCELED_CALL_COUNTTotal number of outbound calls canceled by the sender before routing to the recipient began.
FailedFAILED_CALL_COUNTTotal number of calls that failed due to rejection from the user or the operator, user unavailability, or other system or network errors.
BusyBUSY_CALL_COUNTTotal number of outbound calls that received a busy signal or were rejected because the line was occupied.

Performance

Metrics nameAPI syntaxDescription
Answer seizure ratioANSWER_SEIZURE_RATIOPercentage of seized calls (calls that started ringing) that were successfully answered.
Answer rateANSWER_RATEPercentage of all call attempts that were successfully answered.
Busy rateBUSY_RATEPercentage of all attempted calls that received a busy signal.
Call hang-upsHUNG_UP_COUNTTotal number of calls or sessions that ended, either after a successful interaction or due to a system error.
Normal hang-upsNORMAL_HUNG_UP_COUNTNumber of calls or sessions ended by the user after a successful interaction.
Hung up due to an errorERROR_HUNG_UP_COUNTNumber of calls or sessions that ended due to a system error.
Call durationTOTAL_CALL_DURATIONTotal duration of all inbound and outbound calls.


Aggregation/Dimensions

Use dimensions to group Voice and Video metrics and analyze them more effectively, for example, by country, direction, sender or capabilities. The Metrics API (opens in a new tab) supports flexible aggregation (using aggregateBy) across time intervals, call outcomes, network information, and error types.

Dimension nameDescription
ACCOUNT_KEYGroups results by account key in the response, showing corresponding account key values.
HOURGroups results by hour, showing corresponding timestamp values.
DAYGroups results by day, showing corresponding day values.
WEEK_SATURDAY_STARTGroups results by week starting from Saturday, showing corresponding timestamp values.
WEEK_SUNDAY_STARTGroups results by week starting from Sunday, showing corresponding timestamp values.
WEEK_MONDAY_STARTGroups results by week starting from Monday, showing corresponding timestamp values.
MONTHGroups results by month, showing corresponding month values.
QUARTERGroups results by quarter, showing corresponding quarter values.
YEARGroups results by year, showing corresponding year values.
TIME_TO_ANSWERGroups the results by call answer time, showing time-to-answer period descriptions.
CHANNEL_CODEGroups results by channel, showing corresponding channel code values.
CHANNEL_NAMEGroups results by channel name, showing corresponding channel name values.
CAPABILITYGroups the results by capability, showing corresponding capability code values.
DIRECTIONGroups results by the traffic direction, showing corresponding direction values: OUTBOUND for traffic sent to a client and INBOUND for traffic received from a client.
SENDERGroups results by sender, showing corresponding sender values.
SENDER_TYPEGroups results by sender type, showing corresponding sender type values.
COMMUNICATIONGroups results by communication, showing corresponding communication ID value.
NETWORK_IDGroups results by network, showing corresponding network ID values.
NETWORK_NAMEGroups results by network, showing corresponding network name values.
COUNTRY_IDGroups results by country, showing corresponding country ID values.
COUNTRY_NAMEGroups results by country, showing corresponding country name values.
APPLICATION_IDGroups results by application, showing corresponding application ID values.
ENTITY_IDGroups results by entity, showing corresponding entity ID values.
STATUS_GROUPGroups results by status group, showing corresponding status group values of a response.
STATUSGroups results by status name, showing corresponding status values of a response.
ERROR_GROUPGroups results by error group, showing corresponding error group values of a response.
ERROR_CODEGroups results by error code, showing their corresponding error code values of a response.


Filters

Use filters to narrow down your metrics query and target specific data sets.

FilterAPI syntaxDescriptionRequired
AccountsaccountKeysTargets specific accounts based on accountKeys (opens in a new tab).
Restrictions apply for legacy accounts.
No
Sub-accountsincludeSubaccountsIncludes subaccount traffic data for comprehensive analysis.No
Sent time rangesentSincesIncludes a specific message time frame.Yes
sentUntil
Engagement timeframetimeToAnswerRepresents the time it took for the call to be answered using time buckets. For example, you can filter only for calls answered within a second. The from bucket is inclusive, while the to bucket is exclusive.No
Statuses and error codesstatusGroupsFilter by specific status or error codes.No
statuses
errorGroups
errorCodes
DirectiondirectionCategorizes traffic based on direction, distinguishing between outbound and inbound messages.No
ChannelchannelCodeCategorizes traffic based on communication channels.Yes
CapabilitiescapabilitiesApplies only when the channel code is VOICE_VIDEO. Specifies the underlying technology used to initiate or receive a call.

Available capabilities and their codes:
  • Phone: PHONE
  • WebRTC: WEBRTC
  • SIP trunks: SIPTRUNK
  • Viber Business Calls: VIBER_BC
  • WhatsApp Business Calls: WHATSAPP_BC
No
SendersendersFilters traffic based on specific senders or sender types.
List of possible values for sender types.
No
Sender typesenderTypes
Communication IDcommunicationIdsCategorizes traffic based on specific identifiers such as communication IDs. It is only applicable for traffic sent over Infobip SaaS solutions, such as Broadcast or Moments (Flow).No
NetworknetworkIdsCategorizes traffic based on specific identifiers, such as network IDs, or country IDs.No
CountrycountryIds
ApplicationapplicationIdBy including additional CPaaSX parameters like applicationId and entityId, you can get valuable insights into the source and purpose of your communication activities, aiding in more accurate analysis and decision-making. The Metrics API (opens in a new tab) supports filtering data by multiple application and entity pairs within a single request.

Use these parameters if you are using CPaaSX concepts and features.

Learn more about CPaaSX here.
No
EntityentityId

Capabilities

Voice and Video communication can span different technologies. The capabilities parameter helps you filter and group data based on specific method used to initiate or receive a call, such as a traditional phone networks or internet-based services. This parameter applies only to the VOICE_VIDEO channel and allows you to distinguish between various communication methods supported under this unified channel. It is especially useful for analyzing performance across different technologies.

See the table below for supported capabilities:

Capability codeDescription
PHONETraditional phone calls
WEBRTCWebRTC-based calls
SIPTRUNKSIP trunking
VIBER_BCViber Business Calls
WHATSAPP_BCWhatsApp Business Calls






Need assistance

Explore Infobip Tutorials

Encountering issues

Contact our support

What's new? Check out

Release Notes

Unsure about a term? See

Glossary
Service status

Copyright @ 2006-2025 Infobip ltd.

Service Terms & ConditionsPrivacy policyTerms of use