Skip to navigation

API: the 20,000-character limit on the stream endpoints counts spoken text, not SSML tags

POST /v1/audio/stream and POST /v1/audio/stream/with-timestamps now accept up to 20,000 characters of spoken text, the characters a request is billed for. SSML tags no longer count toward the limit, as on /v1/audio/speech since 9 Oct.

  • The number is unchanged; only what it counts is. Tags such as <speak>, <break> and <prosody> are not counted, an entity such as &amp; counts as one character, and a <sub> counts its alias.
  • The input as sent can be up to 32,000 characters, markup included.
  • A refusal says which limit it hit. It is still 400 validation_failed, and the message names either the spoken-text limit or the 32,000-character ceiling.
  • Nothing that was accepted before is refused. Plain text is counted exactly as before.

/v1/audio/speech is unchanged: 2,000 spoken characters, and up to 20,000 as sent.

No API version change is needed. See API Limits.