> For the complete documentation index, see [llms.txt](https://attr.sygnal.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://attr.sygnal.com/sa5-video/video-player/youtube-video-data.md).

# YouTube Video Data 🧪

Extraction of YouTube Data

{% hint style="info" %}
This is not yet an SA5 feature. Notes for consideration.
{% endhint %}

## Video Data

* Thumbnail
* Alt versions
* Chapters
* Stats ( likes, etc ) 
* Metadata markup such as links & end-frames
* Transcription / SRTs 

Sources to consider; 

1. **YouTube Data API v3**
2. **Embedded Player Parameters**:
   * When you embed a YouTube video, certain parameters can be added to the URL to control its behavior. While these don't give you new information, they do let you configure how the video is displayed or played.
3. **Public RSS Feeds**:
   * YouTube used to provide RSS feeds for channels which you could use to get a list of videos along with some basic details. However, this method became less accessible over time, and while there are still ways to access RSS data for YouTube, it's less direct and less rich in terms of details compared to the past.
4. **Open Graph Tags & Metadata**:
   * YouTube videos have Open Graph tags and other meta tags to provide data to be used when the video is shared on social platforms. By inspecting the page source or using tools to extract Open Graph data, you can obtain:
     * Video title
     * Thumbnail image
     * Description (though often truncated or limited)
5. **oEmbed Endpoint**:
   * YouTube provides an oEmbed endpoint which returns embed information for a video. You can use it like this: `https://www.youtube.com/oembed?url=http://www.youtube.com/watch?v=[VIDEO_ID]&format=json`
   * This will return some basic data about the video, including title, author\_name, height, width, thumbnail, etc. in JSON format.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://attr.sygnal.com/sa5-video/video-player/youtube-video-data.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.