# Get buyer category properties

> Eto API reference for `GET /api/v1/buyer-categories/{category_id}/properties`. Base URL `https://eto.tools/api/v1/`. Authenticate with the `X-Eto-API-Key` header.

Part of the [Eto API reference](https://eto.tools/dev/docs/). The full reference in one file is at [llms-full.txt](https://eto.tools/dev/docs/llms-full.txt); the machine-readable schema is at [openapi.json](https://eto.tools/dev/docs/openapi.json).

## GET /api/v1/buyer-categories/{category_id}/properties

Get buyer category properties

- Operation ID: `buyer_category_properties`
- Slug: `buyer-category-properties`
- Category: Categories
- Authentication: API key only. Reads public marketplace data, so no store needs to be connected.
- HTML: https://eto.tools/dev/docs/#ep-buyer-category-properties
- Markdown: https://eto.tools/dev/docs/categories/buyer-category-properties.md

Get filterable properties for a buyer category. Etsy docs: "Buyer Taxonomy Properties".

Proxied to the Etsy API at `/v3/application/buyer-taxonomy/nodes/{category_id}/properties`. Fields Etsy returns are passed through untouched.

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `category_id` | path | `integer` | yes | The buyer category ID |

### Request

```bash
curl -H "X-Eto-API-Key: eto_your_key" "https://eto.tools/api/v1/buyer-categories/1/properties"
```

```python
import requests

url = "https://eto.tools/api/v1/buyer-categories/1/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/buyer-categories/1/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/buyer-taxonomy/nodes/{category_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.