Changelog

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 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 walks the two calls, and the consent guide 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 with your workspace and what you are moving. We keep the old flow open for individual workspaces with an end date while they finish.