# 2025-03-04: Shopping List Service - metadata field changes

## Overview

The `metadata` field at root level is now deprecated in GET responses, as each shopping list now maintains its own independent `metadata` field. This field will be fully removed on September 1st, 2025. Additionally we have added version validation for update operation where you can provide `version` in the update payload to validate it against the current entity version, preventing unintentional overriding when multiple updates occur simultaneously.

## Updated endpoints

| Endpoint                                                                                                                                                                                            | Description                                                                                 |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- |
| [Retrieving a shopping list](https://developer.emporix.io/api-references/api-guides/checkout/shopping-list/api-reference/shopping-lists)                                                            | Deprecated `metadata` field on root level and added `metadata` field to each shopping list. |
| [Retrieving a customer shopping list](https://developer.emporix.io/api-references/api-guides/checkout/shopping-list/api-reference/shopping-lists#get-shoppinglist-tenant-shopping-lists-customerid) | Deprecated `metadata` field on root level and added `metadata` field to each shopping list. |
| [Updating a customer shopping list](https://developer.emporix.io/api-references/api-guides/checkout/shopping-list/api-reference/shopping-lists#put-shoppinglist-tenant-shopping-lists-customerid)   | Added `metadata.version` to request payload which allows for version validation             |

## Known problems

There are no known problems.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://developer.emporix.io/changelog/archive/changelog-2025/2025-03-04-shopping-list.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.