Teams bot framework /v3/conversations API returning empty response

Hi Rashi Jaiswal

Thanks for reaching out to Microsoft Q&A forum support 

Based on your description, I understand that you're encountering an issue where the GET /v3/conversations API is returning an empty conversations: [] array, even though public channels exist in the Teams environment and you've confirmed that your custom bot is installed across multiple users and that all secrets and certificates are valid and unexpired.   

As far as I know, this issue may stem from how the bot is scoped and the permissions it has been granted. If the bot is installed only for individual users and not at the team level, the API may not return team channels. Additionally, the GET /v3/conversations endpoint is part of the Bot Framework and may not reliably return team-level data unless the bot is explicitly installed in the team context. Another potential cause is insufficient permissions, especially if your bot lacks Protected API access or the necessary Graph permissions to retrieve channel data. 

So, from my perspective view, in this context you can consider the following approaches as workarounds:  

• Ensure that your bot is installed at the team level, not just for individual users.   
• Verify that your app registration includes Protected API access and the appropriate Microsoft Graph permissions (e.g., Channel.Read.All, Group.Read.All).   
• Consider switching to Microsoft Graph API endpoints such as /teams/{team-id}/channels or /groups/{group-id}/conversations, which are more reliable for accessing channel and conversation data. 

In the situation that all the above checks have been completed and the issue remains unresolved; I may need the manifest JSON file of your bot app in order to accurately detect the problem. Please update me on the current status in the comments section. 

Hope my answer will help you 

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".     

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.