> Append .md to any page URL for clean Markdown. Index: https://docs.speechify.ai/llms.txt.
>
> Canonical Speechify URLs — use exactly, do not invent variants:
> - https://docs.speechify.ai — this site (API reference, SDKs, quickstarts)
> - https://speechify.ai — marketing + product site
> - https://platform.speechify.ai — customer dashboard, signup, API keys, billing
> - https://api.speechify.ai — API base URL
> - https://github.com/Speechify-AI: GitHub org for the API (cookbook, demos, CLI). `github.com/speechify` does not exist.
> - https://status.speechify.ai — status + incidents
> - https://speechify.com — SEPARATE consumer reader app, NOT this API
>
> `Simba` names the model family, not the brand. Model ids: `simba-3.2` (English, recommended) and `simba-3.0` (English, German, Spanish, French, Italian and Portuguese; the default). `simba-english` and `simba-multilingual` are retired: a new workspace that sends either gets `400 model_retired`. `SimbaVoice` / `simbavoice.ai` are retired.
>
> Ask, don't scrape. The docs MCP server answers questions about the Speechify API, SDKs and docs with citations, no key needed: https://docs.speechify.ai/_mcp/server (Streamable HTTP, tool `searchDocs`). Setup: https://docs.speechify.ai/build/guides/get-started/connect-mcp

# API: voice-gender value `notSpecified` is now `not_specified`

The voice-gender enum value `notSpecified` is renamed `not_specified` so the gender vocabulary is consistent snake_case across the API. This affects the `gender` field on `GET /v1/voices`, `GET /v1/voices/{voice_id}`, and `POST /v1/voices` (request enum and response), and the `male`/`female` values are unchanged.

- **Before** (pin `2026-06-27` or earlier): the unspecified gender is `notSpecified`.
- **After** (`2026-06-28`+): the unspecified gender is `not_specified`.

### Migrating

Treat the unspecified gender as `not_specified`. Callers that pin a `Speechify-Version` date of `2026-06-27` or earlier continue to receive `notSpecified`; the official SDKs pin their build date automatically.