# Set listing personalization

> Eto API reference for `POST /api/v1/listings/{listing_id}/personalization`. 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).

## POST /api/v1/listings/{listing_id}/personalization

Set listing personalization

- Operation ID: `listing_personalization_post`
- Slug: `listing-personalization-post`
- Category: Listings
- 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-personalization-post
- Markdown: https://eto.tools/dev/docs/listings/listing-personalization-post.md

Create or replace all personalization questions on a listing you own (up to 5; max 1 file-upload question). Eto finds the connected store that owns the listing, drafts included. See the Listing Builder guide for full field constraints.

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

### Parameters

| Name | In | Type | Required | Description |
| --- | --- | --- | --- | --- |
| `listing_id` | path | `integer` | yes | The Etsy listing ID |
| `personalization_questions` | body | `array` | yes | Questions: [{question_type, question_text, instructions?, required?, max_allowed_characters?, max_allowed_files?, options?}]. |

### Request

```bash
curl -X POST -H "X-Eto-API-Key: eto_your_key" -H "Content-Type: application/json" -d '{"personalization_questions": [{"question_type": "text_input", "question_text": "Name to engrave", "required": true, "max_allowed_characters": 30}]}' "https://eto.tools/api/v1/listings/1234567890/personalization"
```

```python
import requests

url = "https://eto.tools/api/v1/listings/1234567890/personalization"
headers = {"X-Eto-API-Key": "eto_your_key"}
payload = {
    "personalization_questions": [
        {
            "question_type": "text_input",
            "question_text": "Name to engrave",
            "required": True,
            "max_allowed_characters": 30
        }
    ]
}

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

```javascript
const url = "https://eto.tools/api/v1/listings/1234567890/personalization";
const payload = {
  "personalization_questions": [
    {
      "question_type": "text_input",
      "question_text": "Name to engrave",
      "required": true,
      "max_allowed_characters": 30
    }
  ]
};

const response = await fetch(url, {
  method: "POST",
  body: JSON.stringify(payload),
  headers: {
    "X-Eto-API-Key": "eto_your_key",
    "Content-Type": "application/json",
  },
});
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}/personalization` 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.