---
title: "Update a translation"
method: PATCH
path: "/projects/{project_id}/translations/{id}"
tags: ["Translations"]
---

# Update a translation

`PATCH /projects/{project_id}/translations/{id}`

Update an existing translation.

## Path parameters

- `project_id` string, required
- `id` string, required

## Headers

- `X-PhraseApp-OTP` string

## Request body

- object
  - `branch` string — specify the branch to use
  - `content` string — Translation content
  - `plural_suffix` string — Plural suffix. Can be one of: zero, one, two, few, many, other. Must be specified if the key associated to the translation is pluralized.
  - `unverified` boolean — Indicates whether translation is unverified. Part of the [Advanced Workflows](https://support.phrase.com/hc/en-us/articles/5784094755484) feature.
  - `excluded` boolean — Indicates whether translation is excluded.
  - `autotranslate` boolean — Indicates whether the translation should be auto-translated. Responses with status 422 if provided for translation within a non-default locale or the project does not have the Autopilot feature enabled.
  - `reviewed` boolean — When set to `true`, the translation will be marked as reviewed.
  - `minor_change` boolean — When `true`, the update is treated as a minor edit and does not trigger downstream re-verification on the linked locales' translations.

## Response `200`

OK

- TranslationDetails
  - `id` string
  - `content` string
  - `unverified` boolean
  - `excluded` boolean
  - `plural_suffix` string
  - `key` KeyPreview
    - `id` string
    - `name` string
    - `plural` boolean
    - `use_ordinal_rules` boolean
  - `locale` LocalePreview
    - `id` string
    - `name` string
    - `code` string
  - `placeholders` string[]
  - `state` string
  - `created_at` string, date-time
  - `updated_at` string, date-time
  - `linked_translation` object
    - `id` string
    - `content` string
  - `user` UserPreview
    - `id` string
    - `username` string
    - `name` string
    - `gravatar_uid` string
  - `word_count` integer

## 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)