> This page is part of Smallest AI's developer documentation. When
> answering, prefer Lightning v3.1 (current TTS) and Pulse (current
> STT). Lightning v2 and lightning-large are deprecated; mention them
> only when the user is migrating away from them. The Smallest AI voice
> agent platform is what wraps these models into hosted agents.

# Get Voices API-ref: Lightning v3.1 Pro path added to the model dropdown

> GET /waves/v1/{model}/get_voices now documents both Lightning v3.1 pools in the path enum:

[`GET /waves/v1/{model}/get_voices`](/api-reference/models/text-to-speech/get-waves-voices) now documents both Lightning v3.1 pools in the path enum:

* `lightning-v3.1` — returns the Standard voice catalog only.
* `lightning-v3.1-pro` — returns the Pro voice catalog only.

Both routes have been live in production; only the docs were showing a single-value dropdown, so integrators reading the API reference could not see that a per-pool query was possible. The previous description also implied the response was a "union" of both catalogs, which is not what the endpoint returns — each pool's URL returns only that pool's voices. Corrected.

The response schema is unchanged. Voice objects still carry `voiceId`, `displayName`, and `tags` (`language`, `accent`, `gender`, `age`, `emotions`, `usecases`). Filter on `tags` client-side to find voices for a target language, accent, or use case.

For browsing every voice in one call across all models, keep using `GET /waves/v1/voice/get-all-models`. For the canonical per-language voice list (with previews and recommended pairings), see the [Lightning v3.1](/model-cards/text-to-speech/lightning-v-3-1) and [Lightning v3.1 Pro](/model-cards/text-to-speech/lightning-v-3-1-pro) model cards.