# Listing Properties — Eto API

> Category attributes on a listing.

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

- [GET/PUT /api/v1/shops/{shop_id}/listings/{listing_id}/properties/{property_id}](https://eto.tools/dev/docs/listing-properties/listing-property.md): Get or update listing property
- [GET /api/v1/listings/{listing_id}/properties/{property_id}](https://eto.tools/dev/docs/listing-properties/listing-property-public.md): Get a listing property (public)
- [GET /api/v1/shops/{shop_id}/listings/{listing_id}/properties](https://eto.tools/dev/docs/listing-properties/listing-properties-all.md): Get all listing properties
- [DELETE /api/v1/shops/{shop_id}/listings/{listing_id}/properties/{property_id}](https://eto.tools/dev/docs/listing-properties/listing-property-delete.md): Delete a listing property

## GET · PUT /api/v1/shops/{shop_id}/listings/{listing_id}/properties/{property_id}

Get or update listing property

- Operation ID: `listing_property_get`
- Slug: `listing-property`
- Category: Listing Properties
- 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-property
- Markdown: https://eto.tools/dev/docs/listing-properties/listing-property.md
- Operation IDs by method: `listing_property_get` = GET, `listing_property_put` = PUT

Manage specific properties (like color, size) for a listing.

Proxied to the Etsy API at `/v3/application/shops/{shop_id}/listings/{listing_id}/properties/{property_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 |
| `property_id` | path | `integer` | yes | The property ID |

### Request — GET

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

```python
import requests

url = "https://eto.tools/api/v1/shops/12345678/listings/1234567890/properties/200"
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/properties/200";

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 — PUT

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

```python
import requests

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

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

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

const response = await fetch(url, {
  method: "PUT",
  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}/properties/{property_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}/properties/{property_id}

Get a listing property (public)

- Operation ID: `listing_property_public`
- Slug: `listing-property-public`
- Category: Listing Properties
- Authentication: API key only. Reads public marketplace data, so no store needs to be connected.
- HTML: https://eto.tools/dev/docs/#ep-listing-property-public
- Markdown: https://eto.tools/dev/docs/listing-properties/listing-property-public.md

Get a specific property value for any listing. Etsy docs: "Listing Property".

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

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `listing_id` | path | `integer` | yes | The listing ID |
| `property_id` | path | `integer` | yes | The property ID |

### Request

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

```python
import requests

url = "https://eto.tools/api/v1/listings/1234567890/properties/200"
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/properties/200";

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}/properties/{property_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/shops/{shop_id}/listings/{listing_id}/properties

Get all listing properties

- Operation ID: `listing_properties_all`
- Slug: `listing-properties-all`
- Category: Listing Properties
- 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-properties-all
- Markdown: https://eto.tools/dev/docs/listing-properties/listing-properties-all.md

Get all properties for one of your listings. Etsy docs: "Listing Properties".

Proxied to the Etsy API at `/v3/application/shops/{shop_id}/listings/{listing_id}/properties`. 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

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

```python
import requests

url = "https://eto.tools/api/v1/shops/12345678/listings/1234567890/properties"
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/properties";

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/shops/{shop_id}/listings/{listing_id}/properties` 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}/properties/{property_id}

Delete a listing property

- Operation ID: `listing_property_delete`
- Slug: `listing-property-delete`
- Category: Listing Properties
- 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-property-delete
- Markdown: https://eto.tools/dev/docs/listing-properties/listing-property-delete.md

Remove a property value from your listing. Etsy docs: "Delete Listing Property".

Proxied to the Etsy API at `/v3/application/shops/{shop_id}/listings/{listing_id}/properties/{property_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 |
| `property_id` | path | `integer` | yes | The property ID |

### Request

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

```python
import requests

url = "https://eto.tools/api/v1/shops/12345678/listings/1234567890/properties/200"
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/properties/200";

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}/properties/{property_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.