Skip to Content
Cloud One
  • Products

    Business Communication Suite & Phone System


      By Edition

      ​Cloud

      Software

      Appliance

    By Deployment

    ​On-premise

    Hosted by Cloud One

    Self-hosted

    By Management

    ​Managed By Cloud One

    Semi-Managed by Cloud One

    Self-Managed


    Simu Connect UC Clients


    Simu Connect Web Client Simu Connect Mobile Client Simu Connect Desktop ClientSimu Connect Chrome ExtensionSimu Connect TAPI Integration

    SIP Trunks


    Business SIPPay As You Go SIP Country Presence SIPVirtual Phone NumbersGolden Phone NumbersToll Free NumbersBring Your Own Carrier (BYOC)Calling RatesTalktime Top-up

    Get a Proof of Concept Now!


    Simu Connect POC Application Managed Business Communication Suite Self Managed Business Communication SuiteSIP Trunk POCOdoo Phone POC
  • Solutions

    Business Needs


    Work from Anywhere Hosted UCaaS Self hosted UCaaSVideo ConferencingAppliance PBXAI-powered Cloud PBXWhite-label Solution

    Industry


    Call Center Healthcare HospitalityFinanceEducationLogisticsRetail BusinessGovernment Agency

    Ecosystem


    IP Phones SIP Trunks IntegrationHeadsetsVirtual Phone Numbers

    By Integration


    Odoo Phone System Zoho Phone System Salesforce Phone SystemMicrosoft Dynamics Phone SystemZendesk Phone SystemFreshdesk Phone SystemBitrix24 Phone SystemHubSpot Phone System
  • Resources

    Downloads

    Download user guides and more documents

    Book a Meeting

    Schedule a meeting at your convenience

    Developer Guide

    Read API Documentation for Cloud One BCS API

    Business Communication Suite

    Experience our user-friendly business communication suite today. Explore robust telephony features that enhance your client connections efficiently.  

    See More Details
  • Devices

    Yealink IP Phones


    Yealink T3 Series IP Phones Yealink T4 Series IP Phones Yealink T5 Series IP PhonesYealink T7 Series IP PhonesYealink T8 Series IP Phones Yealink DECT IP Phones

    Voice Conferencing Solutions


    VC Room Systems BYOD Solutions Video Phone Video Conferencing Accessories

    Microsoft Solutions


    MS Teams Rooms Systems Microsoft Phones Conference Phones HeadsetsYealink MeetingBoardYealink MeetingBoard Pro

    Zoom Rooms


    Zoom Rooms Systems Zoom Phones Zoom Cameras BYOD Solutions
  • Help

    Ticketing System


    Submit a Helpdesk TicketReport an Issue

    Training


    User TrainingOperator TrainingCall Center Agent TrainingSupervisor Training

    Frequently Asked Questions


    General FAQBCS FAQSIP Trunks FAQLocal Phone Numbers FAQ

    Contact Us


    WhatsApp Icon


  • Support Helpdesk Contact
  • +254 20 790 0100
  • support@cloudone.co

  • Accounts Helpdesk Contact
  • +254 20 790 0000
  • finance@cloudone.co
  • Visit our Office


    Cloud One Ltd

    Saachi Plaza - Unit A3, Argwings Kodhek Road, Nairobi, Kenya
    P.O.Box 76484-00508 Yaya Centre

    +254 20 790 0000

    hello@cloudone.co


    Kindly do not email multiple contacts as it creates multiple tickets on our CRM


  • Contact Us
  • Blog
    ​​
  • Sign in
  • 0
  • 0
  • Deploy in hours Certified Experts Zero Setup / License Fees*
  • Follow us
    Click here to setup your social networks
    Click here to setup your social networks
Cloud One
  • 0
  • 0
    • Products
    • Solutions
    • Resources
    • Devices
    • Help
    • Contact Us
    • Blog
  • Deploy in hours Certified Experts Zero Setup / License Fees*
  • Follow us
    Click here to setup your social networks
    Click here to setup your social networks
  • Sign in
  • ​​

Query Call Report Detail

Query call details in specific IVR/Queue/Agent report.

Request URL

GET {base_url}/{api_path}/call_report/detail?access_token={access_token}

Note: To enhance system performance, Cloud One has upgraded the CDR module in version 83.21.0.117 with a new data structure for clearer display and more comprehensive call details. The system gradually deletes old CDRs and related call report data according to the CDR Auto Cleanup setting.

Before old call report data are cleaned up, new and historical data are managed separately - openapi/v2.0 for new data and openapi/v1.0 for historical data. Make sure to use the appropriate API path based on the type of data that you want to retrieve.

Request parameters

ParameterAvailableRequiredTypeDescription
typeThis parameter is available in all call report types.YesStringCall report type.
Valid value:
  • ivr: IVR report.
  • aireceptionistcallactivity: AI Receptionist Call Activity report.
  • queueperformance: Queue Performance report.
  • queueperformanceactivity: Queue Performance Activity report.
  • queueagentperformance: Agent Performance report.
my_report_idThis parameter is available in user-created reports.YesIntegerThe ID of a user-created report.
Note: You can query report ID using Query My Reports List.
start_timeThis parameter is available when querying the following types of reports.
  • IVR Report
  • Queue Performance
  • Agent Performance
YesStringSpecify the start time to filter report.
Note: The time format depends on the date and time display format of PBX (set in System > Date and Time > Display Format on PBX).

Examples:

  • If the display format is Month/Day/Year and is 24-hours format, then the valid time format is MM/DD/YYYY HH:mm:ss.
  • If the display format is Year/Month/Day and is 12-hours format, then the valid time format is YYYY/MM/DD HH:mm:ss AM or YYYY/MM/DD HH:mm:ss PM.
end_timeThis parameter is available when querying the following types of reports.
  • IVR Report
  • Queue Performance
  • Agent Performance
YesStringSpecify the end time to filter report.
Note: The time format depends on the date and time display format of PBX (set in System > Date and Time > Display Format on PBX).

Examples:

  • If the display format is Month/Day/Year and is 24-hours format, then the valid time format is MM/DD/YYYY HH:mm:ss.
  • If the display format is Year/Month/Day and is 12-hours format, then the valid time format is YYYY/MM/DD HH:mm:ss AM or YYYY/MM/DD HH:mm:ss PM.
detail_time_beginThis parameter is available when querying the following types of reports.
  • IVR Report
  • Queue Performance
  • Agent Performance
YesStringSpecify the start time to filter call details.
Note: The time format depends on the date and time display format of PBX (set in System > Date and Time > Display Format on PBX).

Examples:

  • If the display format is Month/Day/Year and is 24-hours format, then the valid time format is MM/DD/YYYY HH:mm:ss.
  • If the display format is Year/Month/Day and is 12-hours format, then the valid time format is YYYY/MM/DD HH:mm:ss AM or YYYY/MM/DD HH:mm:ss PM.
detail_time_endThis parameter is available when querying the following types of reports.
  • IVR Report
  • Queue Performance
  • Agent Performance
YesStringSpecify the end time to filter call details.
Note: The time format depends on the date and time display format of PBX (set in System > Date and Time > Display Format on PBX).

Examples:

  • If the display format is Month/Day/Year and is 24-hours format, then the valid time format is MM/DD/YYYY HH:mm:ss.
  • If the display format is Year/Month/Day and is 12-hours format, then the valid time format is YYYY/MM/DD HH:mm:ss AM or YYYY/MM/DD HH:mm:ss PM.
timeThis parameter is available when querying Queue Performance Activity report.YesString

Specify the time frame to filter the call report.

Note: The time format depends on the date display format of PBX.

For example, Date Display Format of PBX is Year/Month/Day, then the valid time format is YYYY/MM/DD.

Time format:
  • To query the report by hour, enter YYYY/MM/DD.
  • To query the report by day, enter YYYY/MM.
  • To query the report by month, enter YYYY.
detail_timeThis parameter is available when querying Queue Performance Activity report.YesString

Specify the time frame to filter call details.

Time format:
  • To query the call details by hour, enter the hour.

    For example, enter 16 to query the call details from 16:00 to 16:59 on the specified day.

  • To query the call details by day, enter the day.

    For example, enter 29 to query the call details for the 29th day of the specified month.

  • To query the call details by month, enter the month.

    For example, enter 10 to query the call details for October of the specified year.

ivr_numThis parameter is available when querying IVR Report.YesStringThe number of the desired IVR.
queue_id_listThis parameter is available when querying the following types of reports:
  • Queue Performance
  • Queue Performance Activity
YesStringThe ID of the desired queue.
Note: You can query the queue's ID using Get Menu Options.
queue_idThis parameter is available when querying Agent Performance report.YesIntegerThe ID of the desired queue.
Note: You can query the queue's ID using Get Menu Options.
queue_numThis parameter is available when querying the following types of reports:
  • Queue Performance
  • Queue Performance Activity
  • Agent Performance
YesStringThe number of the desired queue.
agent_numThis parameter is available when querying Agent Performance report.YesStringThe extension number of the desired agent.
abandon_timeThis parameter is available when querying the following types of reports:
  • Queue Performance
  • Queue Performance Activity
  • Agent Performance
NoIntegerSet a time. Calls abandoned within the specified time will not be included in report. (Unit: Second)
talk_timeThis parameter is available when querying the following types of reports:
  • Queue Performance
  • Inbound Queue Activity Analysis
  • Inbound Queue Logs
  • Agent Activity Analysis
NoIntegerSet a time. Calls that proceeded within the specified time will be not be included in report. (Unit: Second)
ai_receptionist_id_listThis parameter is available when querying the AI Receptionist Call Activity report.NoStringThe ID(s) of the AI receptionist(s).Note:
  • You can query the ID using Get Menu Options (menu=ai_receptionist).
  • Use commas to separate multiple IDs.
processing_resultThis parameter is available when querying the AI Receptionist Call Activity report.NoStringThe process result of an AI receptionist call.Valid value:
  • resolved: The AI receptionist successfully resolved caller's issue without transferring the call.
  • transferred: The AI receptionist transferred the call to another destination.
  • unresolved: The AI receptionist neither resolved caller's issue nor transferred the call.
Note: If this parameter is omitted, the details of all types of calls are returned.

Response parameters

ParameterTypeDescription
errcodeIntegerReturned error code.
  • 0: Succeed.
  • Non-zero value: Failed.
Note:You can check the error code and error message in Error Code and Error Message.
errmsgStringReturned message.
  • SUCCESS: Succeed.
  • FAILURE: Failed.
total_numberIntegerThe total number of call detail records.
ivr_report_detailArray<ivr_call_detail>The list of the IVR call details.
ai_receptionist_call_activity_detailArray<ai_receptionist_call_activity_detail>The list of the AI Receptionist call details.
queue_performance_detailArray<queue_call_detail>The list of the Queue Performance call details.
queue_performance_activity_detailArray<queue_call_detail>The list of the Queue Performance Activity call details.
queue_agent_performance_detailArray<agent_call_detail>The list of the Queue Agent Performance call details.

ivr_call_detail

ParameterTypeDescription
idStringThe unique ID of the call.
timeStringThe time when the call was received.
call_fromStringThe number and name of the caller.
pressStringThe key pressed in the call.
destinationStringThe destination of the keypress.
opr_durationIntegerThe time between the caller called into the IVR and exited the IVR.
reason_partya ~ reason_partyfStringThe parts of the content that are used to compose the information about the keypress destination (destination).Note:This parameter is returned only in API version 1.0.
call_toStringThe number and name of the keypress destination (destination).
Note: If the keypress destination doesn't have a number, such as Play Prompt and Exit, Play Prompt and Return to IVR, etc., this parameter returns null.
timestampIntegerThe timestamp of the time when the call was received.
Note: This parameter is returned only in API version 1.0.
dst_numStringThe number of the keypress destination (destination).
Note:
  • This parameter is returned only in API version 1.0.
  • If the keypress destination doesn't have a number, such as Play Prompt and Exit, Play Prompt and Return to IVR, etc., this parameter returns null.
ivr_numStringIVR number.
destination_typeString

The destination type of the keypress.

Note: This parameter is returned only in API version 2.0.

ai_receptionist_call_activity_detail

ParameterTypeDescription
idStringThe unique ID of the call.
timeStringThe time when the call was received.
call_fromStringThe number and name of the caller.
call_toStringThe number and name of the AI receptionist.
talk_durationIntegerThe amount of time the AI receptionist spent talking to the caller.
processing_resultStringThe process result of the AI receptionist call.
  • resolved: The AI receptionist successfully resolved caller's issue without transferring the call.
  • transferred: The AI receptionist transferred the call to another destination.
  • unresolved: The AI receptionist neither resolved caller's issue nor transferred the call.

queue_call_detail

ParameterTypeDescription
idStringThe unique ID of the call.
timeStringThe time when the call was received.
call_fromStringThe number and name of the caller.
queue_nameStringQueue name.
agent_nameStringAgent name and agent number.
statusStringCall status.
  • abandond: The call was abandoned by the caller.
  • missed: The call was eventually not answered by the agent.
  • answered: The call was answered by the agent.
ring_durationIntegerThe time between the call started to ring an agent and the call answered.
talk_durationIntegerThe time between the call answered and the call ended.
hold_durationIntegerThe total amount of time that the call was held.
reasonStringThe reason why the call was not answered by the agent or why the call ended.Note:This parameter is returned only in API version 1.0.
process_resultStringThe process result for an abandoned or missed queue call.
  • unprocessed
  • processed
polling_attemptsIntegerThe number of polling attempts to call an agent.
process_extStringThe extension number and name of the agent that processed the abandoned or missed queue call.
process_timeStringThe time that an agent changed the processing status of an abandoned or missed queue call.
reason_partya ~ reason_partyfStringThe parts of the content that are used to compose the information about the reason.
Note: This parameter is returned only in API version 1.0.
call_toStringThe number and name of the callee.
timestampIntegerThe timestamp of the time when the call was received.
queue_numStringQueue number.
agent_numStringAgent number.
auto_sync_process_resultIntegerWhether to automatically synchronize the updated process result to all missed or abandoned calls from the same caller to the same queue within a specified time period.
  • 0: Disabled.
  • 1: Enabled.

queue_call_detail

ParameterTypeDescription
idStringThe unique ID of the call.
timeStringThe time when the call was received.
call_fromStringThe number and name of the caller.
queue_nameStringQueue name.
agent_nameStringAgent name and agent number.
statusStringCall status.
  • abandond: The call was abandoned by the caller.
  • missed: The call was eventually not answered by the agent.
  • answered: The call was answered by the agent.
ring_durationIntegerThe time between the call started to ring an agent and the call answered.
talk_durationIntegerThe time between the call answered and the call ended.
hold_durationIntegerThe total amount of time that the call was held.
reasonStringThe reason why the call was not answered by the agent or why the call ended.Note:This parameter is returned only in API version 1.0.
process_resultStringThe process result for an abandoned or missed queue call.
  • unprocessed
  • processed
polling_attemptsIntegerThe number of polling attempts to call an agent.
process_extStringThe extension number and name of the agent that processed the abandoned or missed queue call.
process_timeStringThe time that an agent changed the processing status of an abandoned or missed queue call.
reason_partya ~ reason_partyfStringThe parts of the content that are used to compose the information about the reason.
Note: This parameter is returned only in API version 1.0.
call_toStringThe number and name of the callee.
timestampIntegerThe timestamp of the time when the call was received.
queue_numStringQueue number.
agent_numStringAgent number.
auto_sync_process_resultIntegerWhether to automatically synchronize the updated process result to all missed or abandoned calls from the same caller to the same queue within a specified time period.
  • 0: Disabled.
  • 1: Enabled.

agent_call_detail

ParameterTypeDescription
idStringThe unique ID of the call.
timeStringThe time when the call was received.
call_fromStringThe number and name of the caller.
queue_nameStringQueue name.
agent_nameStringAgent name and agent number.
statusStringCall status.
Note: This parameter indicates the status of the incoming call for the agent.
  • abandond: The call was abandoned by the caller.
  • missed: The call was not answered by the agent.
  • answered: The call was answered by the agent.
ring_durationIntegerThe time between the call started to ring an agent and the call answered.
talk_durationIntegerThe time between the call answered and the call ended.
hold_durationIntegerThe total amount of time that the call was held.
reasonStringThe reason why the call was not answered by the agent or why the call ended.
Note: This parameter is returned only in API version 1.0.
process_resultStringThe process result for an abandoned or missed queue call.
  • unprocessed
  • processed
polling_attemptsIntegerThe number of polling attempts to call an agent.
process_extStringThe extension number and name of the agent that processed the abandoned or missed queue call.
process_timeStringThe time that an agent changed the processing status of an abandoned or missed queue call.
reason_partya ~ reason_partyfStringThe parts of the content that are used to compose the information about the reason.
Note: This parameter is returned only in API version 1.0.
dispositionStringCall status.
Note: This parameter indicates the status of the incoming call for the queue, and is returned only in API version 1.0.
  • answered: The call was answered by an agent in the queue.
  • no_answered: The call was not answered by any agents in the queue.
call_toStringThe number and name of the callee.
timestampIntegerThe timestamp of the time when the call was received.Note:This parameter is returned only in API version 1.0.
queue_numStringQueue number.
agent_numStringAgent number.
auto_sync_process_resultIntegerWhether to automatically synchronize the updated process result to all missed or abandoned calls from the same caller to the same queue within a specified time period.
  • 0: Disabled.
  • 1: Enabled.

Examples

Request example

Query the call details of agent 1002 in queue 6400 (ID:"1") during 2024/09/29 00:00:00 - 2024/09/29 23:59:59.

Important:Make sure to use the appropriate API path based on the type of report data that you want to retrieve.

  • For new report data generated on version 83.21.0.117 or later, use openapi/v2.0.
  • For legacy report data generated on version 83.21.0.66 or earlier, use openapi/v1.0.
GET /openapi/v1.0/call_report/detail?access_token=synJ1EwaEXYvp7fipey7L4mq8E2hrPU8&type=queueagentperformance&start_time=2024/09/01 00:00:00&end_time=2024/09/30 23:59:59&detail_time_begin=2024/09/29 00:00:00&detail_time_end=2024/09/29 23:59:59&agent_num=1002&queue_id=1&abandon_time=5 HTTP/1.1  
Host: 192.168.5.150:8088

Response example

HTTP/1.1 200 OK
{
"errcode": 0,
"errmsg": "SUCCESS",
"total_number": 2,
"queue_agent_performance_detail": [
{
"id": "202409291711030B6DF",
"time": "2024/09/29 17:11:02",
"call_from": "Anna Simmons<2000>",
"queue_name": "Support",
"agent_name": "NONE",
"status": "missed",
"ring_duration": 36,
"talk_duration": 0,
"hold_duration": 0,
"reason": "Anna Simmons<2000> caller_call_callee Terrell Smith<1002> ",
"process_result": "unprocessed",
"polling_attempts": 1,
"process_ext": "",
"process_time": "",
"reason_partya": "src",
"reason_partyb": "caller_call_callee",
"reason_partyc": "dst",
"reason_partyd": "",
"reason_partye": "",
"reason_partyf": "",
"disposition": "no_answered",
"call_to": "Terrell Smith<1002>",
"timestamp": 1727601062,
"queue_num": "6401",
"agent_num": "1002"
},
{
"id": "20240929170007A9523",
"time": "2024/09/29 17:00:06",
"call_from": "Carmen Gordon<2001>",
"queue_name": "Support",
"agent_name": "NONE",
"status": "answered",
"ring_duration": 12,
"talk_duration": 560,
"hold_duration": 0,
"reason": "Terrell Smith<1002> hangup ",
"process_result": "unprocessed",
"polling_attempts": 1,
"process_ext": "",
"process_time": "",
"reason_partya": "dst",
"reason_partyb": "hangup",
"reason_partyc": "",
"reason_partyd": "",
"reason_partye": "",
"reason_partyf": "",
"disposition": "answered",
"call_to": "Terrell Smith<1002>",
"timestamp": 1727600406,
"queue_num": "6401",
"agent_num": "1002"
}
]
}
Useful Links
  • Home
  • About us
  • Products
  • Services
  • Shipping
  • Return Policy
  • Warranty
  • Contact us
Legal
  • Terms
  • Privacy
  • Shared Responsibility
    Service Level Agreement
  • Certifications
About us

Cloud One Limited is a leading Kenyan local telephony service provider. Established in 2017, we offer reliable and secure cloud and on premise business communication solutions, including SIP trunks, Yealink IP phones, and VPS hosting in our Tier 3 data center.


Our mission is to revolutionize cloud communications by providing unparalleled reliability, cutting-edge innovation, and substantial cost savings. We deliver a stress-free, always-available service experience that empowers businesses to thrive in the digital age.

DUNS Registration Number: 561230946
Company Registration Number: PVT-5JUEYMA
Licensed & Regulated by the Communications Authority of Kenya


Follow us
Connect with us
  • Contact us
  • hello@cloudone.co
  • +254 20 7900000
  • Saachi Plaza, UNIT A3 - Argwings Kodhek Rd
Download Simu Connect

    Get the app on the playstore

    Download desktop app for Windows​

    Download app from the appstore

    Download MacOS app