microsoftgraph / microsoftgraph/microsoft-graph-comms-samples
Graph Beta API Start transcription not working
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 253
- Forks
- 275
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 1
Description
Issue
I am trying to start the transcription of a Teams call using the graph api http request. Refer the link below:
https://learn.microsoft.com/en-us/graph/api/call-starttranscription?view=graph-rest-beta&tabs=http
This api is returning a 400 bad request. Refer the request & response bodies below
Request
{
"language": "en-us"
}
Response
{
"error": {
"code": "",
"message": "The input was not valid.",
"details": [
{
"code": "",
"message": "The input was not valid."
}
]
}
}
Code Snippet
This is just a request from Postman
Expected behavior
Expecting a status 202 response body
{
"@odata.type": "#microsoft.graph.startTranscriptionOperation",
"clientContext": "clientContext-value",
"status": "running"
}
Graph SDK (please complete the following information):
- Beta version
Call ID
Call Id: 08002980-9c3b-40cf-97e1-d9f4bd75ca0d
Chain Id: eea4773b-28cb-465a-9d67-b34568e59f49
Request-id': 'bb544e93-6eaf-4f8a-bc1b-6308bd2ee288',
Client-request-id': 'bb544e93-6eaf-4f8a-bc1b-6308bd2ee288'
2025-12-05T05:23:23 UTC
Logs
If required, please add logs from the SDK. (Please remove any PII from the logs before uploading)
Additional context
My scenario
- PSTN user calling in the resource account
- Microsoft Graph bot answers the call
- M365 Teams user is invited via Graph API
- M365 Teams user joins
- Start transcript
This issue is not happening to a specific call. It happens to all the calls
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Microsoft Graph beta startTranscription endpoint and reproduce the request in Postman using the supplied language value and call scenario. Review the returned 400 response alongside the request IDs and timestamp, then check the linked logging guidance if SDK logs are needed. Done means identifying whether the request or endpoint behavior explains the consistent failure and recording the verified requirements or result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postman
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100