Changelog

June 23, 2026

Docs: response-streaming behaviour on POST /v1/audio/stream clarified

The documentation for POST /v1/audio/stream now describes the endpoint’s response shape accurately:

  • The response body is the raw audio bytes delivered over HTTP chunked transfer encoding. There is no JSON envelope and no Base64 encoding — that shape is what POST /v1/audio/speech returns.

  • The Accept header selects the container/codec. Each format’s response Content-Type and codec are now listed explicitly:

    AcceptResponse Content-TypeCodec
    audio/mpegaudio/mpegMP3, 64 kbps
    audio/oggaudio/oggOpus
    audio/aacaudio/aacAAC-LC
    audio/pcmaudio/L16; rate=24000; channels=1Raw 16-bit signed little-endian PCM

  • audio/pcm returns the IANA-registered audio/L16 type with rate and channels parameters per RFC 4856. Byte order is little-endian (industry convention, not the big-endian default the RFC specifies). The 200 response in the API reference now lists audio/L16 alongside audio/mpeg / audio/ogg / audio/aac.

All formats deliver 24 kHz mono audio.

No API behaviour changed. This is a documentation correction only.