!!!danger
Deprecation Date: April 29, 2022
Removal Date: October 15, 2022
!!!

## Color attribute: hexadecimal only

`POST /api/completenesses/settings` and `GET /api/enums/colors` — the color attribute now only accepts hexadecimal values.

- **Previously:** both color names and hexadecimal values were accepted
- **Now:** only hexadecimal in uppercase format is accepted

Valid payload for `POST /api/completenesses/settings`:

```json
{
  "color": "#4DABF7",
  "fields": [],
  "attributes": [],
  "linkTypes": [],
  "id": "identifier_example",
  "documentTypeCode": "document_type_example",
  "description": {},
  "name": {}
}
```

Invalid payload (will return a bad request):

```json
{
  "color": "blue",
  "fields": [],
  "attributes": [],
  "linkTypes": [],
  "id": "identifier_example",
  "documentTypeCode": "document_type_example",
  "description": {},
  "name": {}
}
```

## `limit` parameter maximum value reduced to 50

The `limit` parameter is now capped at **50** (previously 100) on the following endpoints:

- `GET /api/documents`
- `GET /api/assets`
- `GET /api/variants`
- `GET /api/classifications`
- `GET /api/links`

**If you use the pagination links provided in the response bodies**, these will clearly indicate 50 — no action needed.

**If your script builds pagination queries manually** (e.g. querying page 2 with a limit of 70), you will have an offset of 20 documents not returned. Update the limit value in your scripts accordingly.