Microsoft Graph Search API - Video transcripts in SharePoint

Question

Hello, we are using the microsft search API endpoint: https://graph.microsoft.com/v1.0/search/query to find items in sharepoint/onedrive. This is working fine for us.

However, when using search terms that are located in a video transcript, the item is discovered but the link to the video it is associated with is not returned; instead, a link to the "transcript file" is returned. (below is an example snippet of the POST being sent to API).

Instead of getting returned .../sites/TestingSite/Shared Documents/Videos/videofile.mp4, we get back .../sites/TestingSite/Shared Documents/Forms/DispForm.aspx?ID=XXX which apparently is the 'hidden' transcript file itself for the Video.
When we navigate to the transcript file link, we get a page like the attached image.

Here is the API POST code, for example we are searching for a video where the speaker says "erla":

{ 
"requests": 
  [ 
		{ 			
"entityTypes": [ 				
"driveItem", "listItem", "list" 			
], 		
"query": { "queryString": "erla" } 		
               } 	
  ]
}

And here is a snippet of the Response we get back:

The "webUrl" returned in the response is not a link to the video itself, but is instead a link to the screenshot shown above.

Would it be possible to change the search API so that it functions more like the SharePoint search bar (when searching in the search bar, it searches the transcripts, but returns the associated video instead)?

Answer 1

Hi @Trevor Harris-A ,

The behavior you described with the Microsoft Search API is expected. By default, when searching for content using the search API, it returns the items (such as files or documents) that match the search query along with their respective URLs. However, the API does not automatically provide a direct link to the associated video when searching for content within a video transcript.

I also did a test, which shows an expected behaviour:

Here is MP4:

Here is result:

Thanks for letting us know your user experience. According to your case description, I do understand how frustrated you are now.

 

When I received the case, I searched a lot of documents did a lot of researches. And I feel regretful to inform you that it turns out to be a by-design one.

 

And I noticed that some end users have also proposed the same request, it is highly recommended that you can vote this ticket. Many features of our current products are designed and upgraded based on customers’ feedback. With requirements like this increase, the problem may well be released in the future. Thanks for your understanding.

 

feedback

https://feedbackportal.microsoft.com/feedback/

---

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.

Best Regards

Cheng Feng