---
title: "Create or update searchability"
method: PATCH
path: "/v2/searchabilities/{name}"
tags: ["Searchabilities"]
---

# Create or update searchability

`PATCH /v2/searchabilities/{name}`

**🔐 This endpoint requires [HTTP authentication](https://docs.constructor.com/reference/main-authentication) (either [Basic](https://docs.constructor.com/reference/main-authentication#basic-authentication) or [Bearer](https://docs.constructor.com/reference/main-authentication#bearer-authentication)).**
For authenticating with Bearer token, required scopes are: `searchabilities(w)`.

Create or update searchability with specified `name`.

## Path parameters

- `name` string, required

## Query parameters

- `key` string, required — The key of the index to use.
- `section` string — The section of the index to use. Defaults to `Products`.
- `c` string — The ID of the client and version that the request is coming from, such as `cio-js-2.90`.
- `skip_rebuild` boolean — Skip index rebuild.

## Request body

- SearchabilityV2PatchRequestBody
  - `fuzzy_searchable` boolean — Configure a field as fuzzy-searchable to enable typo-tolerant keyword-matching on field values in search and autocomplete. A field can be fuzzy-searchable or exact-searchable, but not both. Avoid marking very verbose fields (e.g. long descriptions) as fuzzy-searchable, since it can lead to recall of more items than is necessary and introduces complexity with ranking.
  - `exact_searchable` boolean — Configure this field for ID or ID-like values (SKU ID, ISBN, part number, etc.) to enable exact matching only, with no typo-tolerance, for search and autocomplete. Do not use for fields containing natural language words. A field can be exact-searchable or fuzzy-searchable, but not both.
  - `displayable` boolean — Specifies whether the field is displayable in the response within the `results` array. On create, omitted value inherits from the nearest (deepest) configured parent. To learn more about displayability inheritance, please visit [this guide](/docs/using-the-constructor-dashboard-indexes-manage-searchability-and-displayability#inherited-displayability-configurations)
  - `hidden` boolean — Hides the field by default in the response but makes it available to retrieve via `fmt_options[hidden_fields]` parameter.

## Response `200`

OK

- SearchabilityV2PatchResponse
  - `name` string, required — Name of searchability field.
  - `fuzzy_searchable` boolean, required — Configure a field as fuzzy-searchable to enable typo-tolerant keyword-matching on field values in search and autocomplete. A field can be fuzzy-searchable or exact-searchable, but not both. Avoid marking very verbose fields (e.g. long descriptions) as fuzzy-searchable, since it can lead to recall of more items than is necessary and introduces complexity with ranking.
  - `exact_searchable` boolean, required — Configure this field for ID or ID-like values (SKU ID, ISBN, part number, etc.) to enable exact matching only, with no typo-tolerance, for search and autocomplete. Do not use for fields containing natural language words. A field can be exact-searchable or fuzzy-searchable, but not both.
  - `displayable` boolean, required — Specifies whether the field is displayable in the response within the `results` array.
  - `hidden` boolean, required — Hides the field by default in the response but makes it available to retrieve via `fmt_options[hidden_fields]` parameter.
  - `created_at` string, date-time, required — Creation date and time
  - `updated_at` string, date-time — Last updated date and time

## Other responses

- `400` — Bad Request
- `401` — Credentials are not passed or action is forbidden.
- `403` — The supplied token does not have the required permissions.
- `429` — Rate limit breached

---

[API](https://skmtc.net/constructor/apis/autocomplete.md) · [All operations](https://skmtc.net/constructor/apis/autocomplete/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/constructor/autocomplete/versions/2d33330633b6/schema)