---
title: "Update a term"
method: PATCH
path: "/accounts/{account_id}/glossaries/{glossary_id}/terms/{id}"
tags: ["Glossary Terms"]
---

# Update a term

`PATCH /accounts/{account_id}/glossaries/{glossary_id}/terms/{id}`

Update an existing term in a term base (previously: glossary).

## Path parameters

- `account_id` string, required
- `glossary_id` string, required
- `id` string, required

## Headers

- `X-PhraseApp-OTP` string

## Request body

- object
  - `term` string — Glossary term
  - `description` string — Description of term
  - `translatable` boolean — Indicates whether the term should be used for all languages or can be translated
  - `case_sensitive` boolean — Indicates whether the term is case sensitive

## Response `200`

OK

- GlossaryTerm
  - `id` string
  - `term` string
  - `description` string
  - `translatable` boolean
  - `case_sensitive` boolean
  - `translations` GlossaryTermTranslation[]
    - `id` string
    - `locale_code` string
    - `content` string
    - `created_at` string, date-time
    - `updated_at` string, date-time
  - `glossary` object — The glossary this term belongs to.
    - `id` string
    - `name` string
  - `created_at` string, date-time
  - `updated_at` string, date-time

## Other responses

- `400` — Bad request. The request could not be parsed or a parameter failed validation. Verify the request body, the content type, and the parameter types, then retry.
- `401` — Unauthorized. Authentication failed because the access token is missing, expired, or invalid. Supply a valid access token and retry.
- `403` — Forbidden. The credentials are valid but not permitted for this request: the access token may lack the required scope, the user may lack permission on the resource, or the account plan may not include the feature. Use a token with the required scope on an account and user that hold the necessary permissions.
- `404` — Not found. The requested resource does not exist or is not visible to the authenticated user. Verify the identifiers in the request path and that the token has access to them, then retry.
- `422` — Unprocessable entity. The request was well-formed but failed validation. The response body lists each offending field in the `errors` array, with its resource, field, and a human-readable message. Correct the listed fields and retry.
- `429` — Too many requests. The rate limit has been exceeded. Wait until the time indicated by the `X-Rate-Limit-Reset` response header before retrying.

---

[API](https://skmtc.net/phrase/apis/control-hub-service.md) · [All operations](https://skmtc.net/phrase/apis/control-hub-service/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/phrase/control-hub-service/versions/98ecac7ba2bf/schema)