# Images & Media — Eto API

> Listing images, videos and digital files.

Base URL `https://eto.tools/api/v1/`. Every request carries the `X-Eto-API-Key` header. Part of the [Eto API reference](https://eto.tools/dev/docs/).

## Endpoints in this category

- [POST /api/v1/shops/{shop_id}/listings/{listing_id}/images](https://eto.tools/dev/docs/images-and-media/listing-image-upload.md): Upload listing image
- [DELETE /api/v1/shops/{shop_id}/listings/{listing_id}/images/{image_id}](https://eto.tools/dev/docs/images-and-media/listing-image-delete.md): Delete listing image
- [POST /api/v1/shops/{shop_id}/listings/{listing_id}/videos](https://eto.tools/dev/docs/images-and-media/listing-video-upload.md): Upload listing video
- [DELETE /api/v1/shops/{shop_id}/listings/{listing_id}/videos/{video_id}](https://eto.tools/dev/docs/images-and-media/listing-video-delete.md): Delete listing video
- [GET/POST /api/v1/shops/{shop_id}/listings/{listing_id}/variation-images](https://eto.tools/dev/docs/images-and-media/listing-variation-images.md): Manage variation images
- [GET/POST /api/v1/shops/{shop_id}/listings/{listing_id}/files](https://eto.tools/dev/docs/images-and-media/listing-file-upload.md): List or upload digital files
- [GET/DELETE /api/v1/shops/{shop_id}/listings/{listing_id}/files/{file_id}](https://eto.tools/dev/docs/images-and-media/listing-file-detail.md): Get or delete a digital file
- [GET /api/v1/listings/{listing_id}/images/{image_id}](https://eto.tools/dev/docs/images-and-media/listing-image-detail.md): Get a single image
- [GET /api/v1/listings/{listing_id}/videos/{video_id}](https://eto.tools/dev/docs/images-and-media/listing-video-detail.md): Get a single video

## POST /api/v1/shops/{shop_id}/listings/{listing_id}/images

Upload listing image

- Operation ID: `listing_image_upload`
- Slug: `listing-image-upload`
- Category: Images & Media
- Authentication: API key plus a connected store. Eto uses that store’s Etsy token, so the shop_id must belong to a store connected to your Eto account or the call answers 403 STORE_NOT_CONNECTED.
- HTML: https://eto.tools/dev/docs/#ep-listing-image-upload
- Markdown: https://eto.tools/dev/docs/images-and-media/listing-image-upload.md

Upload an image to a listing. Send as multipart/form-data with the image in the "image" field.

Proxied to the Etsy API at `/v3/application/shops/{shop_id}/listings/{listing_id}/images`. Fields Etsy returns are passed through untouched.

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `shop_id` | path | `integer` | yes | Your Etsy shop ID |
| `listing_id` | path | `integer` | yes | The listing ID |
| `image` | body | `file` | yes | Image file (JPEG, PNG, GIF) |
| `rank` | body | `integer` | no | Image display order (1-10) |

### Request

```bash
curl -X POST -H "X-Eto-API-Key: eto_your_key" -F "image=@photo.jpg" -F "rank=1" "https://eto.tools/api/v1/shops/12345678/listings/1234567890/images"
```

```python
import requests

url = "https://eto.tools/api/v1/shops/12345678/listings/1234567890/images"
headers = {"X-Eto-API-Key": "eto_your_key"}
files = {"image": open("photo.jpg", "rb")}
data = {"rank": "1"}

response = requests.post(url, headers=headers, files=files, data=data, timeout=120)
response.raise_for_status()
print(response.json())
```

```javascript
const url = "https://eto.tools/api/v1/shops/12345678/listings/1234567890/images";
const form = new FormData();
form.append("image", fileInput.files[0]);
form.append("rank", "1");

const response = await fetch(url, {
  method: "POST",
  body: form,
  headers: {
    "X-Eto-API-Key": "eto_your_key",
  },
});
if (!response.ok) throw new Error(`Eto API ${response.status}`);
const data = await response.json();
```

### Response

`application/json`, passed through from Etsy’s `/v3/application/shops/{shop_id}/listings/{listing_id}/images` verbatim. The field-by-field data model is in the [v2 preview reference](https://eto.tools/eto-dev-api-v2/), which documents these same routes alongside the whole Etsy schema.

### Errors

Failures answer with the shared error body described in the Errors section: `{"error": {"code", "status", "message", "hint", "docs"}}`. Branch on `code`, not on the message.

This endpoint can additionally return `STORE_NOT_CONNECTED` (403) when the shop is not linked to your account, and `STORE_TOKEN_EXPIRED` (503) when its Etsy authorisation has lapsed and needs reconnecting.


## DELETE /api/v1/shops/{shop_id}/listings/{listing_id}/images/{image_id}

Delete listing image

- Operation ID: `listing_image_delete`
- Slug: `listing-image-delete`
- Category: Images & Media
- Authentication: API key plus a connected store. Eto uses that store’s Etsy token, so the shop_id must belong to a store connected to your Eto account or the call answers 403 STORE_NOT_CONNECTED.
- HTML: https://eto.tools/dev/docs/#ep-listing-image-delete
- Markdown: https://eto.tools/dev/docs/images-and-media/listing-image-delete.md

Remove an image from a listing.

Proxied to the Etsy API at `/v3/application/shops/{shop_id}/listings/{listing_id}/images/{image_id}`. Fields Etsy returns are passed through untouched.

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `shop_id` | path | `integer` | yes | Your Etsy shop ID |
| `listing_id` | path | `integer` | yes | The listing ID |
| `image_id` | path | `integer` | yes | The image ID to delete |

### Request

```bash
curl -X DELETE -H "X-Eto-API-Key: eto_your_key" "https://eto.tools/api/v1/shops/12345678/listings/1234567890/images/987654321"
```

```python
import requests

url = "https://eto.tools/api/v1/shops/12345678/listings/1234567890/images/987654321"
headers = {"X-Eto-API-Key": "eto_your_key"}

response = requests.delete(url, headers=headers, timeout=120)
response.raise_for_status()
print(response.json())
```

```javascript
const url = "https://eto.tools/api/v1/shops/12345678/listings/1234567890/images/987654321";

const response = await fetch(url, {
  method: "DELETE",
  headers: {
    "X-Eto-API-Key": "eto_your_key",
  },
});
if (!response.ok) throw new Error(`Eto API ${response.status}`);
const data = await response.json();
```

### Response

`application/json`, passed through from Etsy’s `/v3/application/shops/{shop_id}/listings/{listing_id}/images/{image_id}` verbatim. The field-by-field data model is in the [v2 preview reference](https://eto.tools/eto-dev-api-v2/), which documents these same routes alongside the whole Etsy schema.

### Errors

Failures answer with the shared error body described in the Errors section: `{"error": {"code", "status", "message", "hint", "docs"}}`. Branch on `code`, not on the message.

This endpoint can additionally return `STORE_NOT_CONNECTED` (403) when the shop is not linked to your account, and `STORE_TOKEN_EXPIRED` (503) when its Etsy authorisation has lapsed and needs reconnecting.


## POST /api/v1/shops/{shop_id}/listings/{listing_id}/videos

Upload listing video

- Operation ID: `listing_video_upload`
- Slug: `listing-video-upload`
- Category: Images & Media
- Authentication: API key plus a connected store. Eto uses that store’s Etsy token, so the shop_id must belong to a store connected to your Eto account or the call answers 403 STORE_NOT_CONNECTED.
- HTML: https://eto.tools/dev/docs/#ep-listing-video-upload
- Markdown: https://eto.tools/dev/docs/images-and-media/listing-video-upload.md

Upload a video to a listing.

Proxied to the Etsy API at `/v3/application/shops/{shop_id}/listings/{listing_id}/videos`. Fields Etsy returns are passed through untouched.

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `shop_id` | path | `integer` | yes | Your Etsy shop ID |
| `listing_id` | path | `integer` | yes | The listing ID |
| `video` | body | `file` | yes | Video file |

### Request

```bash
curl -X POST -H "X-Eto-API-Key: eto_your_key" -F "video=@clip.mp4" "https://eto.tools/api/v1/shops/12345678/listings/1234567890/videos"
```

```python
import requests

url = "https://eto.tools/api/v1/shops/12345678/listings/1234567890/videos"
headers = {"X-Eto-API-Key": "eto_your_key"}
files = {"video": open("clip.mp4", "rb")}

response = requests.post(url, headers=headers, files=files, timeout=120)
response.raise_for_status()
print(response.json())
```

```javascript
const url = "https://eto.tools/api/v1/shops/12345678/listings/1234567890/videos";
const form = new FormData();
form.append("video", fileInput.files[0]);

const response = await fetch(url, {
  method: "POST",
  body: form,
  headers: {
    "X-Eto-API-Key": "eto_your_key",
  },
});
if (!response.ok) throw new Error(`Eto API ${response.status}`);
const data = await response.json();
```

### Response

`application/json`, passed through from Etsy’s `/v3/application/shops/{shop_id}/listings/{listing_id}/videos` verbatim. The field-by-field data model is in the [v2 preview reference](https://eto.tools/eto-dev-api-v2/), which documents these same routes alongside the whole Etsy schema.

### Errors

Failures answer with the shared error body described in the Errors section: `{"error": {"code", "status", "message", "hint", "docs"}}`. Branch on `code`, not on the message.

This endpoint can additionally return `STORE_NOT_CONNECTED` (403) when the shop is not linked to your account, and `STORE_TOKEN_EXPIRED` (503) when its Etsy authorisation has lapsed and needs reconnecting.


## DELETE /api/v1/shops/{shop_id}/listings/{listing_id}/videos/{video_id}

Delete listing video

- Operation ID: `listing_video_delete`
- Slug: `listing-video-delete`
- Category: Images & Media
- Authentication: API key plus a connected store. Eto uses that store’s Etsy token, so the shop_id must belong to a store connected to your Eto account or the call answers 403 STORE_NOT_CONNECTED.
- HTML: https://eto.tools/dev/docs/#ep-listing-video-delete
- Markdown: https://eto.tools/dev/docs/images-and-media/listing-video-delete.md

Remove a video from a listing.

Proxied to the Etsy API at `/v3/application/shops/{shop_id}/listings/{listing_id}/videos/{video_id}`. Fields Etsy returns are passed through untouched.

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `shop_id` | path | `integer` | yes | Your Etsy shop ID |
| `listing_id` | path | `integer` | yes | The listing ID |
| `video_id` | path | `integer` | yes | The video ID to delete |

### Request

```bash
curl -X DELETE -H "X-Eto-API-Key: eto_your_key" "https://eto.tools/api/v1/shops/12345678/listings/1234567890/videos/987654321"
```

```python
import requests

url = "https://eto.tools/api/v1/shops/12345678/listings/1234567890/videos/987654321"
headers = {"X-Eto-API-Key": "eto_your_key"}

response = requests.delete(url, headers=headers, timeout=120)
response.raise_for_status()
print(response.json())
```

```javascript
const url = "https://eto.tools/api/v1/shops/12345678/listings/1234567890/videos/987654321";

const response = await fetch(url, {
  method: "DELETE",
  headers: {
    "X-Eto-API-Key": "eto_your_key",
  },
});
if (!response.ok) throw new Error(`Eto API ${response.status}`);
const data = await response.json();
```

### Response

`application/json`, passed through from Etsy’s `/v3/application/shops/{shop_id}/listings/{listing_id}/videos/{video_id}` verbatim. The field-by-field data model is in the [v2 preview reference](https://eto.tools/eto-dev-api-v2/), which documents these same routes alongside the whole Etsy schema.

### Errors

Failures answer with the shared error body described in the Errors section: `{"error": {"code", "status", "message", "hint", "docs"}}`. Branch on `code`, not on the message.

This endpoint can additionally return `STORE_NOT_CONNECTED` (403) when the shop is not linked to your account, and `STORE_TOKEN_EXPIRED` (503) when its Etsy authorisation has lapsed and needs reconnecting.


## GET · POST /api/v1/shops/{shop_id}/listings/{listing_id}/variation-images

Manage variation images

- Operation ID: `listing_variation_images_get`
- Slug: `listing-variation-images`
- Category: Images & Media
- Authentication: API key plus a connected store. Eto uses that store’s Etsy token, so the shop_id must belong to a store connected to your Eto account or the call answers 403 STORE_NOT_CONNECTED.
- HTML: https://eto.tools/dev/docs/#ep-listing-variation-images
- Markdown: https://eto.tools/dev/docs/images-and-media/listing-variation-images.md
- Operation IDs by method: `listing_variation_images_get` = GET, `listing_variation_images_post` = POST

Get or upload images for listing variations.

Proxied to the Etsy API at `/v3/application/shops/{shop_id}/listings/{listing_id}/variation-images`. Fields Etsy returns are passed through untouched.

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `shop_id` | path | `integer` | yes | Your Etsy shop ID |
| `listing_id` | path | `integer` | yes | The listing ID |

### Request — GET

```bash
curl -H "X-Eto-API-Key: eto_your_key" "https://eto.tools/api/v1/shops/12345678/listings/1234567890/variation-images"
```

```python
import requests

url = "https://eto.tools/api/v1/shops/12345678/listings/1234567890/variation-images"
headers = {"X-Eto-API-Key": "eto_your_key"}

response = requests.get(url, headers=headers, timeout=120)
response.raise_for_status()
print(response.json())
```

```javascript
const url = "https://eto.tools/api/v1/shops/12345678/listings/1234567890/variation-images";

const response = await fetch(url, {
  method: "GET",
  headers: {
    "X-Eto-API-Key": "eto_your_key",
  },
});
if (!response.ok) throw new Error(`Eto API ${response.status}`);
const data = await response.json();
```

### Request — POST

```bash
curl -X POST "https://eto.tools/api/v1/shops/12345678/listings/1234567890/variation-images" \
  -H "X-Eto-API-Key: eto_your_key"
```

```python
import requests

url = "https://eto.tools/api/v1/shops/12345678/listings/1234567890/variation-images"
headers = {"X-Eto-API-Key": "eto_your_key"}

response = requests.post(url, headers=headers, timeout=120)
response.raise_for_status()
print(response.json())
```

```javascript
const url = "https://eto.tools/api/v1/shops/12345678/listings/1234567890/variation-images";

const response = await fetch(url, {
  method: "POST",
  headers: {
    "X-Eto-API-Key": "eto_your_key",
  },
});
if (!response.ok) throw new Error(`Eto API ${response.status}`);
const data = await response.json();
```

### Response

`application/json`, passed through from Etsy’s `/v3/application/shops/{shop_id}/listings/{listing_id}/variation-images` verbatim. The field-by-field data model is in the [v2 preview reference](https://eto.tools/eto-dev-api-v2/), which documents these same routes alongside the whole Etsy schema.

### Errors

Failures answer with the shared error body described in the Errors section: `{"error": {"code", "status", "message", "hint", "docs"}}`. Branch on `code`, not on the message.

This endpoint can additionally return `STORE_NOT_CONNECTED` (403) when the shop is not linked to your account, and `STORE_TOKEN_EXPIRED` (503) when its Etsy authorisation has lapsed and needs reconnecting.


## GET · POST /api/v1/shops/{shop_id}/listings/{listing_id}/files

List or upload digital files

- Operation ID: `listing_file_upload_get`
- Slug: `listing-file-upload`
- Category: Images & Media
- Authentication: API key plus a connected store. Eto uses that store’s Etsy token, so the shop_id must belong to a store connected to your Eto account or the call answers 403 STORE_NOT_CONNECTED.
- HTML: https://eto.tools/dev/docs/#ep-listing-file-upload
- Markdown: https://eto.tools/dev/docs/images-and-media/listing-file-upload.md
- Operation IDs by method: `listing_file_upload_get` = GET, `listing_file_upload_post` = POST

GET: List all digital files for a listing. POST: Upload a new digital file. Etsy docs: "Listing Files".

Proxied to the Etsy API at `/v3/application/shops/{shop_id}/listings/{listing_id}/files`. Fields Etsy returns are passed through untouched.

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `shop_id` | path | `integer` | yes | Your Etsy shop ID |
| `listing_id` | path | `integer` | yes | The listing ID |
| `file` | body | `file` | yes | Digital file to upload |
| `name` | body | `string` | no | Display name for the file |

### Request — GET

```bash
curl -X GET "https://eto.tools/api/v1/shops/12345678/listings/1234567890/files" \
  -H "X-Eto-API-Key: eto_your_key" \
  -F "file=@/path/to/photo.jpg"
```

```python
import requests

url = "https://eto.tools/api/v1/shops/12345678/listings/1234567890/files"
headers = {"X-Eto-API-Key": "eto_your_key"}
files = {"file": open("/path/to/photo.jpg", "rb")}

response = requests.get(url, headers=headers, files=files, timeout=120)
response.raise_for_status()
print(response.json())
```

```javascript
const url = "https://eto.tools/api/v1/shops/12345678/listings/1234567890/files";
const form = new FormData();
form.append("file", fileInput.files[0]);

const response = await fetch(url, {
  method: "GET",
  body: form,
  headers: {
    "X-Eto-API-Key": "eto_your_key",
  },
});
if (!response.ok) throw new Error(`Eto API ${response.status}`);
const data = await response.json();
```

### Request — POST

```bash
curl -X POST -H "X-Eto-API-Key: eto_your_key" -F "file=@design.pdf" "https://eto.tools/api/v1/shops/12345678/listings/1234567890/files"
```

```python
import requests

url = "https://eto.tools/api/v1/shops/12345678/listings/1234567890/files"
headers = {"X-Eto-API-Key": "eto_your_key"}
files = {"file": open("design.pdf", "rb")}

response = requests.post(url, headers=headers, files=files, timeout=120)
response.raise_for_status()
print(response.json())
```

```javascript
const url = "https://eto.tools/api/v1/shops/12345678/listings/1234567890/files";
const form = new FormData();
form.append("file", fileInput.files[0]);

const response = await fetch(url, {
  method: "POST",
  body: form,
  headers: {
    "X-Eto-API-Key": "eto_your_key",
  },
});
if (!response.ok) throw new Error(`Eto API ${response.status}`);
const data = await response.json();
```

### Response

`application/json`, passed through from Etsy’s `/v3/application/shops/{shop_id}/listings/{listing_id}/files` verbatim. The field-by-field data model is in the [v2 preview reference](https://eto.tools/eto-dev-api-v2/), which documents these same routes alongside the whole Etsy schema.

### Errors

Failures answer with the shared error body described in the Errors section: `{"error": {"code", "status", "message", "hint", "docs"}}`. Branch on `code`, not on the message.

This endpoint can additionally return `STORE_NOT_CONNECTED` (403) when the shop is not linked to your account, and `STORE_TOKEN_EXPIRED` (503) when its Etsy authorisation has lapsed and needs reconnecting.


## GET · DELETE /api/v1/shops/{shop_id}/listings/{listing_id}/files/{file_id}

Get or delete a digital file

- Operation ID: `listing_file_detail_get`
- Slug: `listing-file-detail`
- Category: Images & Media
- Authentication: API key plus a connected store. Eto uses that store’s Etsy token, so the shop_id must belong to a store connected to your Eto account or the call answers 403 STORE_NOT_CONNECTED.
- HTML: https://eto.tools/dev/docs/#ep-listing-file-detail
- Markdown: https://eto.tools/dev/docs/images-and-media/listing-file-detail.md
- Operation IDs by method: `listing_file_detail_get` = GET, `listing_file_detail_delete` = DELETE

Get details for or delete a specific digital file. Etsy docs: "Listing File".

Proxied to the Etsy API at `/v3/application/shops/{shop_id}/listings/{listing_id}/files/{file_id}`. Fields Etsy returns are passed through untouched.

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `shop_id` | path | `integer` | yes | Your Etsy shop ID |
| `listing_id` | path | `integer` | yes | The listing ID |
| `file_id` | path | `integer` | yes | The file ID |

### Request — GET

```bash
curl -H "X-Eto-API-Key: eto_your_key" "https://eto.tools/api/v1/shops/12345678/listings/1234567890/files/987654321"
```

```python
import requests

url = "https://eto.tools/api/v1/shops/12345678/listings/1234567890/files/987654321"
headers = {"X-Eto-API-Key": "eto_your_key"}

response = requests.get(url, headers=headers, timeout=120)
response.raise_for_status()
print(response.json())
```

```javascript
const url = "https://eto.tools/api/v1/shops/12345678/listings/1234567890/files/987654321";

const response = await fetch(url, {
  method: "GET",
  headers: {
    "X-Eto-API-Key": "eto_your_key",
  },
});
if (!response.ok) throw new Error(`Eto API ${response.status}`);
const data = await response.json();
```

### Request — DELETE

```bash
curl -X DELETE "https://eto.tools/api/v1/shops/12345678/listings/1234567890/files/1" \
  -H "X-Eto-API-Key: eto_your_key"
```

```python
import requests

url = "https://eto.tools/api/v1/shops/12345678/listings/1234567890/files/1"
headers = {"X-Eto-API-Key": "eto_your_key"}

response = requests.delete(url, headers=headers, timeout=120)
response.raise_for_status()
print(response.json())
```

```javascript
const url = "https://eto.tools/api/v1/shops/12345678/listings/1234567890/files/1";

const response = await fetch(url, {
  method: "DELETE",
  headers: {
    "X-Eto-API-Key": "eto_your_key",
  },
});
if (!response.ok) throw new Error(`Eto API ${response.status}`);
const data = await response.json();
```

### Response

`application/json`, passed through from Etsy’s `/v3/application/shops/{shop_id}/listings/{listing_id}/files/{file_id}` verbatim. The field-by-field data model is in the [v2 preview reference](https://eto.tools/eto-dev-api-v2/), which documents these same routes alongside the whole Etsy schema.

### Errors

Failures answer with the shared error body described in the Errors section: `{"error": {"code", "status", "message", "hint", "docs"}}`. Branch on `code`, not on the message.

This endpoint can additionally return `STORE_NOT_CONNECTED` (403) when the shop is not linked to your account, and `STORE_TOKEN_EXPIRED` (503) when its Etsy authorisation has lapsed and needs reconnecting.


## GET /api/v1/listings/{listing_id}/images/{image_id}

Get a single image

- Operation ID: `listing_image_detail`
- Slug: `listing-image-detail`
- Category: Images & Media
- Authentication: API key only. Reads public marketplace data, so no store needs to be connected.
- HTML: https://eto.tools/dev/docs/#ep-listing-image-detail
- Markdown: https://eto.tools/dev/docs/images-and-media/listing-image-detail.md

Get details for a specific listing image. Etsy docs: "Listing Image".

Proxied to the Etsy API at `/v3/application/listings/{listing_id}/images/{image_id}`. Fields Etsy returns are passed through untouched.

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `listing_id` | path | `integer` | yes | The listing ID |
| `image_id` | path | `integer` | yes | The image ID |

### Request

```bash
curl -H "X-Eto-API-Key: eto_your_key" "https://eto.tools/api/v1/listings/1234567890/images/987654321"
```

```python
import requests

url = "https://eto.tools/api/v1/listings/1234567890/images/987654321"
headers = {"X-Eto-API-Key": "eto_your_key"}

response = requests.get(url, headers=headers, timeout=120)
response.raise_for_status()
print(response.json())
```

```javascript
const url = "https://eto.tools/api/v1/listings/1234567890/images/987654321";

const response = await fetch(url, {
  method: "GET",
  headers: {
    "X-Eto-API-Key": "eto_your_key",
  },
});
if (!response.ok) throw new Error(`Eto API ${response.status}`);
const data = await response.json();
```

### Response

`application/json`, passed through from Etsy’s `/v3/application/listings/{listing_id}/images/{image_id}` verbatim. The field-by-field data model is in the [v2 preview reference](https://eto.tools/eto-dev-api-v2/), which documents these same routes alongside the whole Etsy schema.

### Errors

Failures answer with the shared error body described in the Errors section: `{"error": {"code", "status", "message", "hint", "docs"}}`. Branch on `code`, not on the message.


## GET /api/v1/listings/{listing_id}/videos/{video_id}

Get a single video

- Operation ID: `listing_video_detail`
- Slug: `listing-video-detail`
- Category: Images & Media
- Authentication: API key only. Reads public marketplace data, so no store needs to be connected.
- HTML: https://eto.tools/dev/docs/#ep-listing-video-detail
- Markdown: https://eto.tools/dev/docs/images-and-media/listing-video-detail.md

Get details for a specific listing video. Etsy docs: "Listing Video".

Proxied to the Etsy API at `/v3/application/listings/{listing_id}/videos/{video_id}`. Fields Etsy returns are passed through untouched.

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `listing_id` | path | `integer` | yes | The listing ID |
| `video_id` | path | `integer` | yes | The video ID |

### Request

```bash
curl -H "X-Eto-API-Key: eto_your_key" "https://eto.tools/api/v1/listings/1234567890/videos/987654321"
```

```python
import requests

url = "https://eto.tools/api/v1/listings/1234567890/videos/987654321"
headers = {"X-Eto-API-Key": "eto_your_key"}

response = requests.get(url, headers=headers, timeout=120)
response.raise_for_status()
print(response.json())
```

```javascript
const url = "https://eto.tools/api/v1/listings/1234567890/videos/987654321";

const response = await fetch(url, {
  method: "GET",
  headers: {
    "X-Eto-API-Key": "eto_your_key",
  },
});
if (!response.ok) throw new Error(`Eto API ${response.status}`);
const data = await response.json();
```

### Response

`application/json`, passed through from Etsy’s `/v3/application/listings/{listing_id}/videos/{video_id}` verbatim. The field-by-field data model is in the [v2 preview reference](https://eto.tools/eto-dev-api-v2/), which documents these same routes alongside the whole Etsy schema.

### Errors

Failures answer with the shared error body described in the Errors section: `{"error": {"code", "status", "message", "hint", "docs"}}`. Branch on `code`, not on the message.