Sign in
Voices

Get voices for a pool

Return the voice catalog for the chosen Lightning v3.1 pool. Two pools:

  • lightning-v3.1 — the Standard catalog. Supports voice cloning; 20 language codes.
  • lightning-v3.1-pro — the Pro catalog. Curated set across American, British, and Indian accents plus 29 additional languages. Same latency and concurrency as Standard, on dedicated inference.

The endpoint is pool-scoped: /waves/v1/lightning-v3.1/get_voices returns Standard voices only; /waves/v1/lightning-v3.1-pro/get_voices returns Pro voices only. Call one or both depending on which pool you plan to use.

Each voice carries tags (language, accent, gender, age, emotions, usecases). Filter client-side to find the voices that match a target language, accent, or use case. Pass the returned voiceId as voice_id on the unified POST /waves/v1/tts route, together with "model": "lightning_v3.1" (Standard) or "model": "lightning_v3.1_pro" (Pro).

For the canonical per-language voice list (with previews and recommended pairings), see the Lightning v3.1 and Lightning v3.1 Pro model cards.

get/waves/v1/{model}/get_voices

Path parameters

model'lightning-v3.1' | 'lightning-v3.1-pro' required

The pool to query. lightning-v3.1 returns Standard voices; lightning-v3.1-pro returns Pro voices. Note the hyphenated path form differs from the underscored body form used on POST /waves/v1/tts (lightning_v3.1, lightning_v3.1_pro).

Response

Voices retrieved successfully.

Example response

{
  "voices": [
    {
      "voiceId": "avery",
      "displayName": "Avery",
      "tags": {
        "language": [
          "english"
        ],
        "accent": "american",
        "gender": "female",
        "age": "young",
        "emotions": [],
        "usecases": [
          "conversational"
        ]
      }
    }
  ]
}

Changes

Changed in 4 of the 9 revisions of this API.36

  • a06b74deb9541See the full diff
    • ○

      the endpoint scheme security bearerAuth was removed from the API

      api-security-removed

    This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

  • 4537cdb21a7d1See the full diff
    • ○

      added the new enum value lightning-v3.1-pro to the path request parameter model

      request-parameter-enum-value-added

  • ebe2d7d14c5933See the full diff
    • ▲

      removed the enum value lightning from the path request parameter model

      request-parameter-enum-value-removed

    • ▲

      removed the enum value lightning-large from the path request parameter model

      request-parameter-enum-value-removed

    • ▲

      removed the enum value lightning-v2 from the path request parameter model

      request-parameter-enum-value-removed

    • ○

      added the optional property /// to the response with the status

      response-optional-property-added

    • ○

      added the optional property /// to the response with the status

      response-optional-property-added

    • ○

      added the optional property /// to the response with the status

      response-optional-property-added

  • 5706e3f631c01See the full diff
    • ○

      endpoint added

      endpoint-added