> ## Documentation Index
> Fetch the complete documentation index at: https://developers.phrase.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

export const DownloadOpenApiCard = ({url}) => {
  return <Card title="Full API Schema" href={url} target="_blank" horizontal>
      Explore the raw schema to see all endpoints in one place. Perfect for tools and integration setup.
    </Card>;
};

## Style Guide API Reference

The Style Guide API lets you manage organization-wide writing guidelines that Phrase applies across translations and
authored content. A Style Guide is a Markdown document scoped to a single language and versioned on every revision.
Rules are automatically extracted from each Style Guide and can also be created manually — they improve the output
quality in AI Translation Agent and MT Optimize.

<Note>
  **New integrations should use the v2 endpoints** (`POST /api/v2/styleguides`, `PUT /api/v2/styleguides/{id}`). The
  v2 endpoints require a Content Group ID, which enables automatic rule application in TMS projects. The v1 create
  and update endpoints are deprecated.
</Note>

### Key Features

* **Markdown-first authoring** — upload Markdown files; the active version is always the latest revision
* **Multi-language** — manage one Style Guide per language
* **Versioning** — every revision is stored with optional change notes; previous versions stay accessible
* **Rules** — rules extracted automatically from each Style Guide, or created manually; improve AI Translation
  Agent and MT Optimize output quality
* **Content Group integration** — link a Style Guide to a Content Group so TMS projects inherit its rules automatically
* **Search and filter** — find Style Guides by name, description, language, or last-modified date
* **Bulk delete** — remove multiple Style Guides in a single call, with per-item success / failure reporting

### Base URLs

The Style Guide API is available in multiple regions:

| Region | Base URL                           |
| ------ | ---------------------------------- |
| EU     | `https://eu.phrase.com/styleguide` |
| US     | `https://us.phrase.com/styleguide` |

<DownloadOpenApiCard url="https://developers.phrase.com/public/assets/openapi/phrase-style-guides.json" />

### Quick Start

1. **Exchange your API token** for a JWT via the [Platform Authentication guide](/en/api/platform/authentication)
2. **Create a Style Guide** by uploading a Markdown file with a Content Group ID
3. **Poll the job status** endpoint until the job completes
4. **Reference the Style Guide** by ID in subsequent calls

```bash theme={null}
curl -X POST "https://eu.phrase.com/styleguide/api/v2/styleguides" \
  -H "Authorization: Bearer $JWT" \
  -F language=en-GB \
  -F name="English Style Guide" \
  -F description="Brand voice and grammar rules" \
  -F contentGroupId="my-content-group" \
  -F file=@./style-guide.md
```

The response returns a `jobId`. Poll **Get create job status** until `status` is `COMPLETED`:

```bash theme={null}
curl "https://eu.phrase.com/styleguide/api/v1/styleguides/async/create-jobs/$JOB_ID" \
  -H "Authorization: Bearer $JWT"
```

Browse the full operation set, request and response schemas, and per-endpoint examples in the **API Documentation**
section of the left navigation. For a conceptual overview of Style Guides, Rules, and Content Groups, see [Core Concepts](/en/api/style-guides/concepts).
