Forum Discussion
getCallRecord API not returning sessions and media information
Hi
we are trying graph api to get call quality data for our our teams calls
the link below provides the information on the getCallRecords API,
https://learn.microsoft.com/en-us/graph/api/callrecords-callrecord-get?view=graph-rest-1.0&tabs=http#code-try-11
we are following the information in the above link
we are able to retrieve the basic call details from the above api, when we provide the call id, however when we use the below call using additional query parameters we dont see any difference in data output no sessions OR media information about the call is in the output as provided in the detailed call information api , the api just ignores the additional query parameters
https://graph.microsoft.com/v1.0/communications/callRecords/{e7f2e623-e27b-4bd2-a61d-5e2a5d61f812}?%24expand%3Dsessions%28%24expand%3Dsegments%29
please suggest if syntax of the api call is correct or different
7 Replies
- It appears that you are facing issues with the Microsoft Graph API call to retrieve call quality data for Microsoft Teams calls. Specifically, you mentioned that the API call is not returning session or media information as expected.
To address this issue, please make sure you are following the correct syntax and query parameters for the API call. It's important to note that the Graph API may have updates and changes over time, so it's essential to ensure that you are using the latest endpoint and parameters.
Here are a few troubleshooting steps you can take:
Verify Your Permissions:
Ensure that the account you are using to make the API request has the necessary permissions to access call records. You may need the appropriate permissions in your Azure AD application registration.
Check the Endpoint:
Confirm that you are using the correct endpoint and resource URL for the Microsoft Graph API. Ensure that you are using the most up-to-date API version.
Query Parameters:
Double-check the query parameters you are using. It's possible that the syntax or parameters have changed since you last checked the documentation. Refer to the official Microsoft Graph API documentation for any updates on the API's query parameters.
Test in Graph Explorer:
To quickly check if the API call is working as expected, you can use the Microsoft Graph Explorer, a web-based tool for testing Microsoft Graph API calls. This tool allows you to interactively experiment with different queries to see if you can retrieve the desired information.
API Response Format:
Ensure that you are parsing the API response correctly to extract the session and media information. This information might be nested within the response data, so make sure you are navigating through the JSON structure correctly.
Review the API Documentation:
Occasionally, API behavior may change, so it's a good idea to consult the official Microsoft Graph API documentation or release notes for any recent updates or changes to the API call.
Contact Microsoft Support:
If you've tried all the above steps and are still facing issues, consider reaching out to Microsoft support for specific assistance with the Microsoft Graph API and call quality data retrieval.
Keep in mind that API behavior and documentation can change, so staying up-to-date with the latest information and following best practices is essential.- Hi we are referring to latest API documentation, and following the information and syntax as provided in documentation and that's not working as expected. We are just dumping the json output as is in the curl output, so there is no issue in parsing json. all we get is call information not its sessions or media as provided in the documentation in get detailed information on call records. the api seems to just ignore the extended query parameters as written in the documentation. Either the extended parameters written the documentation is wrong or if something has changed then documentation is not updated
- It seems like you've encountered an issue with the Microsoft Graph API call for retrieving call quality data for Microsoft Teams calls, and you're following the latest API documentation and query parameters as provided, but you're not getting the expected results. Your concerns about the API behavior not aligning with the documentation are valid. Here are some steps to consider in this situation:
Documentation Accuracy: It's possible that the API documentation might not be up-to-date or accurate. APIs can change over time, and it's essential that the documentation reflects those changes. If you believe the documentation is incorrect or outdated, consider reporting this to Microsoft so they can address the issue.
Community and Forums: Check if there are any discussions or forums related to the Microsoft Graph API where other developers may have encountered similar issues. They might provide insights or workarounds based on their experiences.
Contact Microsoft Support: If you're confident that you're following the correct API syntax and parameters, and the issue persists, it might be time to reach out to Microsoft's developer support. They can provide specific assistance and guidance on the problem you're facing.
Wait for Updates: Sometimes, API issues are resolved in future updates or patches. Keep an eye on any release notes or updates from Microsoft that address the problem you're encountering. They may release a fix in the near future.
Consider a Different Approach: While you wait for a resolution, consider whether there's an alternative way to gather the information you need. Sometimes, using a different API endpoint or method can yield the desired results.
Request for Clarification: If you decide to contact Microsoft Support or engage in developer forums, be specific about the issue and your expectations. Provide detailed information on what you're doing, the expected results based on the documentation, and the actual results you're getting. The more information you can provide, the easier it will be for others to help you.
In summary, it's frustrating when API behavior doesn't align with the documentation. In such cases, reporting the issue, seeking help from the community, and keeping an eye on updates from the API provider are good steps to take. It's also essential to maintain open communication with the provider to ensure that documentation is accurate and up-to-date for the benefit of all developers.
- we will check this and get back to you.
- any update ? thank you
