---
title: "Update a style guide"
method: PATCH
path: "/projects/{project_id}/styleguides/{id}"
tags: ["Style guides"]
---

# Update a style guide

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

Update an existing style guide.

## Path parameters

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

## Headers

- `X-PhraseApp-OTP` string

## Request body

- object
  - `title` string — Style guide title
  - `audience` string — Audience description
  - `target_audience` 'not_specified' | 'children' | 'teenager' | 'young_adults' | 'adults' | 'old_adults' — Target audience for the translations.
  - `grammatical_person` 'not_specified' | 'first_person_singular' | 'second_person_singular' | 'third_person_singular_masculine' | 'third_person_singular_feminine' | 'third_person_singular_neuter' | 'first_person_plural' | 'second_person_plural' | 'third_person_plural' — Preferred grammatical person.
  - `vocabulary_type` 'not_specified' | 'popular' | 'technical' | 'fictional' — Vocabulary register the translations should use.
  - `business` string — Description of the business
  - `company_branding` string — Company branding to remain consistent.
  - `formatting` string — Formatting requirements and character limitations.
  - `glossary_terms` string — List of terms and/or phrases that need to be translated consistently.
  - `grammar_consistency` string — Formal or informal pronouns, consistent conjugation, grammatical gender
  - `literal_translation` string — Can be one of: Cultural/Conversational, Literal, Neutral.
  - `overall_tone` string — Tone requirement descriptions
  - `samples` string — Provide links to sample product pages, FAQ pages, etc. to give the translator a point of reference. You can also provide past translations. Even snippets or short paragraphs are helpful for maintaining consistency.

## Response `200`

OK

- StyleguideDetails
  - `id` string
  - `title` string
  - `created_at` string, date-time
  - `updated_at` string, date-time
  - `public_url` string
  - `audience` string
  - `target_audience` string
  - `grammatical_person` string
  - `vocabulary_type` string
  - `business` string
  - `company_branding` string
  - `formatting` string
  - `glossary_terms` string
  - `grammar_consistency` string
  - `literal_translation` string
  - `overall_tone` string
  - `samples` string

## 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/revisions/98ecac7ba2bf/schema)