Using Get Communications/Calls API and receiving 500 Internal Server error.

Question

Using Get Communications/Calls API and receiving 500 Internal Server error.

Priyavert Sharma 136

I am attempting to retrieve active call or meeting details using the endpoint: https://graph.microsoft.com/v1.0/communications/calls/. However, no values are being returned in the response.

Additionally, when using historical Call IDs collected from Teams Call Analytics to fetch details via Postman, I encounter a 500 Internal Server Error. I ensured that App has right permissions needed to run these APIs.

Here’s an example of the GET API I am trying to execute: https://graph.microsoft.com/v1.0/communications/calls/d09d6180-5e2e-4aba-9a13-2fb56d1deu47

I am referencing the APIs described in the following documentation:

Any insights or guidance would be appreciated!

Yakun Huang-MSFT 10,555 Reputation points Microsoft External Staff

2024-12-11T02:00:32.61+00:00

Hello Priyavert Sharma,

Thank you for reaching out to Microsoft Support!

This looks like an error thrown by the server. I suggest you open a support ticket with Microsoft Support to get help from the API owner.

Hope this helps.

If the answer is helpful, please click Accept Answer and kindly upvote it. If you have any further questions about this answer, please click Comment.
Yakun Huang-MSFT 10,555 Reputation points Microsoft External Staff

2024-12-13T10:07:59.71+00:00

Hi @Priyavert Sharma

Is there anything else I can help you with regarding this issue? If you still need further help, please feel free to let me know. If your question has been solved, then you can click "Accept Answer", which may help members with similar questions find the answer easily. Thank you very much!
Laxman Reddy Revuri 3,740 Reputation points Microsoft External Staff

2025-01-06T16:28:08.9866667+00:00

Hi @Priyavert Sharma
Thanks for the question and using MS Q&A platform.
When encountering a 500 Internal Server
Mastering HTTP 500 Internal Server Errors: Complete Guide to Log Collections
Firstly, confirm that you have the required permissions such as Calls.AccessMedia.All, Calls.Initiate.All, and Calls.Access. It's essential to ensure that the permissions have been granted and are also consented. Moving on, videos can be provided only if the Call ID provided has been confirmed and is valid and also active or historic. An important condition is that the accessibility of the call should still be there, so it cannot be closed or expired.

Do not forget to monitor the request limit for the API. The use of the incorrect version is also a possibility, so while version v1.0 is common do verify each version accordingly. Do Examine if the token is valid as that confirming if the Content Type is correct or provides the correct authorization will be clear as well. It is best to check beforehand if all necessary details are provided in the request do so all relevant and confirm and make sure.

Lastly for more specific details opt to check the full message or better use Postman or similar tools to examine the response body and even the error, Postman works best due as it captures the entire error giving a best overview of the task.

Reference: Versioning, support, and breaking change policies for Microsoft Graph - Microsoft Graph | Microsoft Learn
Microsoft Graph: Microsoft Graph overview - Microsoft Graph | Microsoft Learn
if you are still encountering the 500 internal server. please reach out to support ticket. Azure Support Options | Microsoft Azure
Laxman Reddy Revuri 3,740 Reputation points Microsoft External Staff

2025-01-08T01:04:22.7166667+00:00

Hi @Priyavert Sharma
Following up to see if you have chance to check my previous response and help us with requested information to check and assist you further on this.
Priyavert Sharma 136 Reputation points

2025-01-08T05:36:45.1833333+00:00

duplicate
Priyavert Sharma 136 Reputation points

2025-01-08T05:37:42.34+00:00

Hello @Laxman Reddy Revuri

Thank you for your message. I have verified that the necessary permissions have been granted to the application, and the call was active during the test. However, the system should also generate results for past (inactive) calls.

The limits are not a concern, as I was testing in a test environment, not in production. The authentication token was validated since I was able to retrieve results from other APIs, and I used Postman for testing and validation of this API.

I am collaborating with MS to find a solution to this issue. Thanks again for taking the time to share your suggestions.

Your answer

Yakun Huang-MSFT 10,555 Reputation points Microsoft External Staff

2024-12-11T02:00:32.61+00:00

Hello Priyavert Sharma,

Thank you for reaching out to Microsoft Support!

This looks like an error thrown by the server. I suggest you open a support ticket with Microsoft Support to get help from the API owner.

Hope this helps.

If the answer is helpful, please click Accept Answer and kindly upvote it. If you have any further questions about this answer, please click Comment.
Yakun Huang-MSFT 10,555 Reputation points Microsoft External Staff

2024-12-13T10:07:59.71+00:00

Hi @Priyavert Sharma

Is there anything else I can help you with regarding this issue? If you still need further help, please feel free to let me know. If your question has been solved, then you can click "Accept Answer", which may help members with similar questions find the answer easily. Thank you very much!
Laxman Reddy Revuri 3,740 Reputation points Microsoft External Staff

2025-01-06T16:28:08.9866667+00:00

Hi @Priyavert Sharma
Thanks for the question and using MS Q&A platform.
When encountering a 500 Internal Server
Mastering HTTP 500 Internal Server Errors: Complete Guide to Log Collections
Firstly, confirm that you have the required permissions such as Calls.AccessMedia.All, Calls.Initiate.All, and Calls.Access. It's essential to ensure that the permissions have been granted and are also consented. Moving on, videos can be provided only if the Call ID provided has been confirmed and is valid and also active or historic. An important condition is that the accessibility of the call should still be there, so it cannot be closed or expired.

Do not forget to monitor the request limit for the API. The use of the incorrect version is also a possibility, so while version v1.0 is common do verify each version accordingly. Do Examine if the token is valid as that confirming if the Content Type is correct or provides the correct authorization will be clear as well. It is best to check beforehand if all necessary details are provided in the request do so all relevant and confirm and make sure.

Lastly for more specific details opt to check the full message or better use Postman or similar tools to examine the response body and even the error, Postman works best due as it captures the entire error giving a best overview of the task.

Reference: Versioning, support, and breaking change policies for Microsoft Graph - Microsoft Graph | Microsoft Learn
Microsoft Graph: Microsoft Graph overview - Microsoft Graph | Microsoft Learn
if you are still encountering the 500 internal server. please reach out to support ticket. Azure Support Options | Microsoft Azure
Laxman Reddy Revuri 3,740 Reputation points Microsoft External Staff

2025-01-08T01:04:22.7166667+00:00

Hi @Priyavert Sharma
Following up to see if you have chance to check my previous response and help us with requested information to check and assist you further on this.
Priyavert Sharma 136 Reputation points

2025-01-08T05:36:45.1833333+00:00

duplicate
Priyavert Sharma 136 Reputation points

2025-01-08T05:37:42.34+00:00

Hello @Laxman Reddy Revuri

Thank you for your message. I have verified that the necessary permissions have been granted to the application, and the call was active during the test. However, the system should also generate results for past (inactive) calls.

The limits are not a concern, as I was testing in a test environment, not in production. The authentication token was validated since I was able to retrieve results from other APIs, and I used Postman for testing and validation of this API.

I am collaborating with MS to find a solution to this issue. Thanks again for taking the time to share your suggestions.

Share via

Using Get Communications/Calls API and receiving 500 Internal Server error.

Your answer