# Read preferences key

One of the signed-in person's own app preferences by its namespaced `key` (`setting:theme`, `table:leads`) — the stored JSON handed back exactly as it was written, because this service never interprets it. `get_preferences` lists them and `put_preferences_key` writes one. A table's column order is deliberately NOT here: that is typed, and lives at `get_table-preferences_tableKey`.

Access class: `workspace`.

## Endpoint

`GET /v1/preferences/{key}`

## Parameters

| Name | In | Type | Required |
| --- | --- | --- | --- |
| key | path | string | Yes |
| body | query | null | No |
| params | query | object | No |
| query | query | object | No |

## Responses

### 200

the action's answer

Content type: `application/json`.

```json
{
  "data": {
    "key": "string",
    "updatedAt": "string",
    "value": "string"
  }
}
```

### default

a refusal: `{"error": "<what a person needs to read>"}`. 401 no credential, 402 the plan does not include this, 403 the seat does not, 404 the thing does not exist or is not yours to see.

Content type: `application/json`.

```json
{
  "error": "string"
}
```