> For the complete documentation index, see [llms.txt](https://apidocs.akinon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apidocs.akinon.com/commerce-openapis/admin/products/special-images.md).

# Special Images

Administrative endpoints for **special images** — the association that flags one of a product's images as serving a specific purpose (base, swatch, listing, or picto). A special image points at an existing product image and marks the role that image plays; it does not upload or store the image itself.

### Core Capabilities

**1. Special Image Listing & Filtering**

* Retrieve a paginated list of special images.
* Filter by image type and by the underlying product image.

**2. Special Image Lifecycle Management**

* Assign an image role to a product (create), replacing any image previously holding that role for the same product.
* Retrieve, replace (PUT), partially update (PATCH), or delete a single special image.

### Image Types

The `image_type` field selects the role the image plays. Each `(product, image_type)` pair is unique: a product can hold at most one image of each type.

| Value     | Description                         |
| --------- | ----------------------------------- |
| `base`    | The product's primary/base image.   |
| `swatch`  | A color or material swatch image.   |
| `listing` | The image used in product listings. |
| `picto`   | A pictogram / icon image.           |

Because the type is unique per product, **creating or updating** a special image is effectively an upsert: any existing record with the same `product` and `image_type` is removed first, so a new assignment always replaces the previous one and no duplicate or orphan row is left behind.

### Dynamic Settings & Environment Variables

No dynamic settings (`dj_dynamic_settings`) and no environment variables affect these endpoints. Listing, creation, update, and deletion behave identically regardless of management-panel configuration.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://apidocs.akinon.com/commerce-openapis/admin/products/special-images.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
