> For the complete documentation index, see [llms.txt](https://apidocs.akinon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apidocs.akinon.com/commerce-openapis/admin/products/product-videos.md).

# Product Videos

Administrative endpoints for **product videos** — video files attached to a product and shown alongside its images on the storefront.

### Core Capabilities

**1. Product Video Listing & Filtering**

* Retrieve a paginated list of product videos, ordered by `order` ascending by default.
* Filter by product and by the stored video file reference.

**2. Product Video Lifecycle Management**

* Attach a video to a product, supplying either inline video content or the storage path of an already-uploaded file.
* Retrieve, update (PUT/PATCH), or delete a single product video.

### Supplying the Video

A product video is defined by exactly one of two mutually complementary inputs — at least one **must** be provided on create:

| Field        | Description                                                                                                                  |
| ------------ | ---------------------------------------------------------------------------------------------------------------------------- |
| `video`      | Inline video file content sent as a string. It is wrapped into a file and stored.                                            |
| `video_path` | The storage path of a video file that has already been uploaded to the media backend. The record simply points at that path. |

When updating, the `product` and inline `video` fields cannot be changed; only `video_path` (to repoint the file), `order`, and other writable fields are applied.

### Dynamic Settings & Environment Variables

No dynamic settings (`dj_dynamic_settings`) and no environment variables affect these endpoints.


---

# 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://apidocs.akinon.com/commerce-openapis/admin/products/product-videos.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.
