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

# Get supported locales

> Returns the locales supported for transcription/translation/summary. The handler itself doesn't use the Tiro token, but the route still runs the Tiro auth middleware — so a Tiro connection must be configured (server-side stored token), same as the other endpoints. **Pro license required.**



## OpenAPI

````yaml /api-reference/tiro/openapi.json get /tiro/locales
openapi: 3.1.0
info:
  title: Magic Meal Kits — Tiro API
  version: 1.0.0
  description: >-
    Upload audio to Tiro and manage meeting notes — transcripts, summaries,
    threads (folders), webhooks, and API keys — through your Magic Meal Kits
    server. Backs the **티로 Tiro (Magic Meal Kits)** Make.com app.


    Every endpoint requires a **Pro** license (a Basic key gets `400` `you are
    not a magic meal kits PRO user`). Auth uses the MMK `X-API-KEY` only; your
    Tiro token is set on the connection page in the Magic Meal Kits app and
    resolved server-side — no per-request token header is needed.


    This documents the MMK-proxy app only. The separate official-API-direct Tiro
    app (which calls `api.tiro.ooo` directly) is not covered here.
  license:
    name: Proprietary
    identifier: LicenseRef-Proprietary
servers:
  - url: https://{deployment}/api/v1
    description: Your Magic Meal Kits deployment
    variables:
      deployment:
        default: magic-meal-kits-xxxxx.run.app
        description: Your Cloud Run host (without protocol)
security:
  - ApiKeyAuth: []
tags:
  - name: Upload
    description: Upload audio for transcription.
  - name: Notes
    description: Create, read, update, and delete meeting notes.
  - name: Content
    description: Transcripts and summaries.
  - name: Config
    description: Threads (folders) and supported locales.
  - name: Webhooks
    description: Subscribe to note events.
  - name: API keys
    description: Manage Tiro API keys.
paths:
  /tiro/locales:
    get:
      tags:
        - Config
      summary: Get supported locales
      description: >-
        Returns the locales supported for transcription/translation/summary. The
        handler itself doesn't use the Tiro token, but the route still runs the
        Tiro auth middleware — so a Tiro connection must be configured
        (server-side stored token), same as the other endpoints. **Pro license
        required.**
      operationId: tiroGetLocales
      responses:
        '200':
          description: Supported locales
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GetSupportedLocalesResponse'
        '400':
          $ref: '#/components/responses/BadRequest'
components:
  schemas:
    GetSupportedLocalesResponse:
      type: object
      properties:
        success:
          type: boolean
        locales:
          type: array
          items:
            type: object
            additionalProperties: true
    ErrorResponse:
      type: object
      properties:
        success:
          type: boolean
          example: false
        error:
          type: string
  responses:
    BadRequest:
      description: >-
        Invalid request, or a Basic key on this Pro route (`you are not a magic
        meal kits PRO user`).
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ErrorResponse'
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: X-API-KEY
      description: Your deployment's API key (MMK_API_KEY).

````