Migrate native voice-cloning recipes to the verified-consent flow - #7
Merged
2 commits merged intoSep 8, 2026
Merged
2 commits merged into
2 commits merged into
Conversation
added 2 commits
September 8, 2026 12:16
The SDK voice-cloning recipes moved to verified consent for SDK 4.x; the native (raw-HTTP) recipes still POSTed the deprecated `consent` form field. Migrate all three — TypeScript (fetch), Python (requests), Bash (curl) — to the consent- challenge flow and pin `Speechify-Version: 2026-09-13`: - POST /v1/voices/consent-challenges to get the phrase (cached single-use between runs in .consent-challenge.json), - POST /v1/voices multipart with consent_challenge_id + consent_recording, - bring-your-own-audio (the recording must be the same speaker as the sample), so the bundled NASA sample is removed. TS typechecks; Bash passes shellcheck + bash -n; Python compiles.
…via the SDK-recipes PR)
ghost
marked this pull request as ready for review
September 8, 2026 13:54
ghost
mentioned this pull request
ghost
pushed a commit
that referenced
this pull request
Sep 8, 2026
Adds runnable recipes for API surfaces the cookbook didn't cover yet, each in every applicable lane (TypeScript SDK/native, Python SDK/native, Bash): - list-models, list-voices, voice-language-model-support - version-pinning-and-idempotency, error-handling - multilingual (language param + simba-3.0), output-formats (telephony/bitrate) - watermark detect/verify (REST-only — not in the SDKs) Update the README index and COVERAGE matrix; ignore pcm/ulaw artifacts and agent worktrees. Also reformats five voice-cloning files that had drifted from Prettier on main, so format:check stays green. The v4 SDK bump and verified-consent voice cloning already landed (#6, #7); this builds on them. Verified end-to-end against the live API on every lane.
This pull request was closed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The SDK voice-cloning recipes moved to verified consent for SDK 4.x (PR #6). The native (raw-HTTP) recipes still POSTed the deprecated
consentform field (fullName+email) — they work today but are deprecated and will be switched off. This migrates all three to the consent-challenge flow.Changes (TypeScript
fetch, Pythonrequests, Bashcurl)POST /v1/voices/consent-challenges(JSON{ full_name }) → returns thephrase+id; cached single-use in.consent-challenge.jsonbetween runs.POST /v1/voicesmultipart now sendsconsent_challenge_id+consent_recording(wasconsent).Speechify-Version: 2026-09-13(the version the flow ships on).Mirrors the SDK recipes in #6 so the native and SDK paths teach the same flow.
Verified
shellcheck+bash -n; Python compiles.DRG-480