Okapi Okapi

Speechify consent body parameter removal on POST /v1/voices

Stopped workingSubscribe to SpeechifyShare

On September 23, 2026, the body parameter consent on POST /v1/voices was removed across every API version. Requests to POST /v1/voices that continue to include the consent form field fail since that day.


Calls it hits

  • POST /v1/voices
  • body parameter consent

What to use instead of these calls

Create a consent challenge and send a recording of the speaker reading its phrase instead.

In Speechify's words

The consent form field on POST /v1/voices is switched off, on every API version, whatever your workspace is pinned to.

Speechify, Announcement

Facts

API
Speechify api.speechify.ai
Kind
Parameter removal
Announced
August 13, 2026
Takes effect
September 23, 2026
Calls after that day
Fail
Source
Announcement
Last updated
Verified
, against Speechify's own pages

Questions

When does this change take effect?

Calls to POST /v1/voices, body parameter consent on Speechify stopped working on September 23, 2026.

What happens to calls after September 23, 2026?

They have failed since September 23, 2026.

How do I find the calls this hits in my code?

Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.


You fixed this one by hand.

Okapi opens the pull request with the fix before the next breaking change reaches your code.

Add to GitHub

Get notifications

Subscribe to Speechify

Hear about each breaking change Speechify announces, in your feed reader, calendar or Slack.

1What to follow

Provider
  • Speechify

2Where to get it

/breaking-changes/feed.xml

Paste it into Feedly, Inoreader, NetNewsWire or any reader. New changes show up as they're announced.