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

# Supported Locales

> Locales used for transcription, translation, and summaries

## Overview

`SupportedLocale` values follow the pattern `language_COUNTRY` where `language` is lowercase (ISO 639-1) and `COUNTRY` is uppercase (ISO 3166-1 alpha-2).

* Examples: `en_US`, `ko_KR`, `ja_JP`, `zh_CN`, `es_ES`, `fr_FR`
* Used by fields like `transcribeLocale`, `translateLocale`, and `summaryLocale`.

<Note>
  If a locale is not specified for a field, it may be `null`.
</Note>

## Supported List

The `SupportedLocale` enum only contains the values below. `auto` is not part of this enum. Automatic detection only applies when you omit `transcriptLocaleHints` in a Create Voice File Job request (`POST /v1/external/voice-file/jobs` family) — omitting it detects the language from the audio, rather than sending the string `"auto"` as a value. The response fields `transcribeLocale`, `translateLocale`, and `summaryLocale` are not values you set on the request; they report the locale actually used after processing. Document generation (`GenerateNoteDocumentRequest.locale`) does not support automatic detection, so one of the values below must be specified explicitly.

* `de_DE` – German (Germany)
* `en_US` – English (United States)
* `es_ES` – Spanish (Spain)
* `fr_FR` – French (France)
* `hi_IN` – Hindi (India)
* `id_ID` – Indonesian (Indonesia)
* `it_IT` – Italian (Italy)
* `ja_JP` – Japanese (Japan)
* `ko_KR` – Korean (Korea)
* `ms_MY` – Malay (Malaysia)
* `ru_RU` – Russian (Russia)
* `sv_SE` – Swedish (Sweden)
* `th_TH` – Thai (Thailand)
* `tr_TR` – Turkish (Turkey)
* `uk_UA` – Ukrainian (Ukraine)
* `vi_VN` – Vietnamese (Vietnam)
* `zh_CN` – Chinese (Simplified, China)

## Guidelines

* `transcribeLocale`, `translateLocale`, and `summaryLocale` are read-only fields that report the locale actually used, returned in the response. They are not request parameters for choosing a locale.
* To specify a locale on a request, use the field each endpoint defines. For example, use `transcriptLocaleHints` when creating a Voice File Job (omit it to auto-detect from the audio), and `GenerateNoteDocumentRequest.locale` when generating a document.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.