> This page is for Build.

> 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 cloning is not available in some jurisdictions

`POST /v1/voices` and `POST /v1/voices/consent-challenges` now return `403 voice_cloning_unavailable_in_region` for a request from a jurisdiction where voice cloning is not available.

- **Location is the IP address that sends the request.** When your backend calls the API, it is your server's location, not your end user's. A location header in the request is ignored.
- **Nothing is spent.** The refusal comes before consent verification, so a consent challenge you already hold stays usable until it expires.
- **Not retryable from that location.** No API key, role or plan change lifts it, and it is never stored against an `Idempotency-Key`.
- **Everything else is unchanged.** Listing voices, synthesizing with them and deleting them work from anywhere, cloned voices that already exist included.

No API version change is needed. See [Where voice cloning is available](/build/guides/voice-cloning/overview#where-voice-cloning-is-available).