> 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.5` (48 languages under one id, English included; recommended), `simba-3.2` (English) 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 requires verified consent on every API version

**The `consent` form field on `POST /v1/voices` is switched off, on every API version, whatever your workspace is pinned to.** Creating a cloned voice now requires proof that the speaker agreed: a consent challenge, and a recording of the speaker reading the phrase it issues. This is the switch-off the [2026-08-13 entry](/build/changelog/2026/8/13) announced and said would be dated here.

**What changes.** A `POST /v1/voices` that sends `consent` and no `consent_challenge_id` returns `400` with the error code `consent_verification_required`; the message links the migration guide. Requests that already send a challenge are unaffected, and so is every existing cloned voice and every synthesis call.

**What to do.** Create a challenge with `POST /v1/voices/consent-challenges`, show the speaker the phrase it returns, record them reading it, and send `consent_challenge_id` and `consent_recording` on the create. Re-pin `Speechify-Version: 2026-09-13` while you are there. The [migration guide](/build/migrating-voice-cloning-consent) walks the two calls, and the [consent guide](/build/guides/voice-cloning/consent) covers the flow end to end.

**Why the window was shorter than 12 months.** Our default sunset is a year, and this one was not, exactly as the 2026-08-13 entry said it would be. An endpoint that clones a voice without checking the speaker agreed is a safety liability rather than an old request shape.

**If this catches you mid-migration, [contact support](mailto:support@speechify.ai)** with your workspace and what you are moving. We keep the old flow open for individual workspaces with an end date while they finish.