Changelog

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.