Forum Discussion
Issue with Teams 'Add a User to Group Chat' API call?
Hello AutomatonSolutionsRDE,
The request fails due to two issues: first, the @odata.type value was misspelled, causing Microsoft Graph to stop processing and return a misleading schema error. Second, an incorrect property was used instead of user@odata.bind. Correcting both issues resolves the problem. The proper request body must include the correct @odata.type, roles array, and the user@odata.bind reference to the target user.
{
"@odata.type": "#microsoft.graph.aadUserConversationMember",
"roles": [],
"user@odata.bind": "https://graph.microsoft.com/v1.0/users('USER_ID')"
}
- AutomatonSolutionsRDEFeb 10, 2026Copper Contributor
Sayali, this is not correct. There's nothing wrong with my API call, it's following the exact format you would expect. You are looking at artifacts of my copy/paste, but the API call follows the exact format in the documentation.
https://graph.microsoft.com/v1.0/chats/[[THREAD_ID]]/members
BODY:{
"chatType": "group",
"\u0040odata.type": "#microsoft.graph.aadUserConversationMember",
"user\u0040odata.bind": "https://graph.microsoft.com/v1.0/users/[[USER_ID]]",
"roles": []
}
- AutomatonSolutionsRDEFeb 10, 2026Copper Contributor
Incorrect. You are referring to changes I made to the post for security reasons. Here is a screenshot of the call being made:
This exactly follows the convention in the documentation. Why isn't it working? (https://learn.microsoft.com/en-us/graph/api/chat-post-members?view=graph-rest-1.0&tabs=http)
Please don't just ask an AI. The AIs all say the same identical thing and they're wrong. Can anyone ACTUALLY explain this?
Error Message:
{"error":{"code":"BadRequest","message":"The provided '#microsoft.graph.aadUserConversationMember' for 'odata.type' is not valid for this operation.","innerError":{"date":"2026-02-10T17:59:50","request-id":"7b28c192-7906-40b1-94d7-dd3abb5577c3","client-request-id":"7b28c192-7906-40b1-94d7-dd3abb5577c3"}}} - AutomatonSolutionsRDEFeb 09, 2026Copper Contributor
Sayali, this is not correct. Apologies that my initial report was not more clear. This is the exact API call being sent, as you can see; the issues you pointed out are not present in the actual API call. it's following the correct format.
Response body:
{"error":{"code":"BadRequest","message":"The provided '#microsoft.graph.aadUserConversationMember' for 'odata.type' is not valid for this operation.","innerError":{"date":"2026-01-29T14:56:25","request-id":"8ef444c8-64e3-45db-80d4-2c0ea9e47902","client-request-id":"8ef444c8-64e3-45db-80d4-2c0ea9e47902"}}}
PPlease advise.