# Price, photo, title and tag changes, with units a day before and after

> Eto API reference for `GET /api/v1/performance/{shop_id}/changes`. 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/performance/{shop_id}/changes

Price, photo, title and tag changes, with units a day before and after

- Operation ID: `listing_changes`
- Slug: `listing-changes`
- Category: Performance
- Authentication: API key only. Reads or writes data Eto holds for your own account.
- HTML: https://eto.tools/dev/docs/#ep-listing-changes
- Markdown: https://eto.tools/dev/docs/performance/listing-changes.md

Every change Eto noticed between six-hour readings, newest first, with impact: units a day in the 14 days before and after. Price and state changes carry old and new values; photo, title and tag changes only say that they happened (no content is stored).

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `shop_id` | path | `integer` | yes | Your Etsy shop id. |
| `period` | query | `string` | no | The window. Or pass start_date and end_date instead. Default: `30d`. One of: `24h`, `7d`, `30d`, `90d`, `1y`, `ytd`, `all`. |
| `start_date` | query | `string` | no | YYYY-MM-DD, inclusive. With end_date. |
| `end_date` | query | `string` | no | YYYY-MM-DD, inclusive. With start_date. |
| `kinds` | query | `string` | no | Comma-separated: price, photo, title, tags, state. |

### Request

```bash
curl -H "X-Eto-API-Key: eto_your_key" "https://eto.tools/api/v1/performance/53081804/changes?kinds=price"
```

```python
import requests

url = "https://eto.tools/api/v1/performance/53081804/changes?kinds=price"
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/performance/53081804/changes?kinds=price";

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`. This endpoint has no worked response example in the registry yet; the [HTML reference](https://eto.tools/dev/docs/#ep-listing-changes) shows the fields it returns.

### 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.