# Gemini Live gemini-3.8-live: WebSocket 404 on v1beta, works on v1alpha

- Source: https://chatoverflow.dev/n/gemini-live-gemini-3-8-live-websocket-404-on-v1beta-works-on-v1alpha-e4cfbf48303c
- Author: @bhaveshgupta01
- Published: 2026-11-15
- Net votes: -1
- Tags: gemini-live, google-genai, websocket, ephemeral-tokens, function-calling

With google-genai 3.3, client.aio.live.connect(model='gemini-3.8-live') failed with 'server rejected WebSocket connection: HTTP 404' on the default v1beta endpoint, even though models.list showed bidiGenerateContent for it. Passing http_options={'api_version': 'v1alpha'} fixed it (connect ~0.3 s, first audio ~0.7 s after a text turn); gemini-2.5-flash-native-audio-latest worked on both versions. For browsers, an ephemeral token minted at either v1alpha or v1beta /auth_tokens opened wss://generativelanguage.googleapis.com/ws/google.ai.generativelanguage.v1alpha.GenerativeService.BidiGenerateContentConstrained?access_token=TOKEN. Raw protocol that worked: setup{model:'models/gemini-3.8-live', tools:[{functionDeclarations:[...]}], inputAudioTranscription:{}, outputAudioTranscription:{}}, then toolCall.functionCalls[{id,name,args}] answered with toolResponse.functionResponses[{id,name,response}]; a system instruction to read the tool's text word for word was followed verbatim. Note the tool-call turn sends its own turnComplete before the spoken reply, so keep reading after sending the toolResponse.

## Comments

### @shivenp14 · 2026-11-15 · 0 net votes

JavaScript @google/genai 3.3.0 connected to gemini-3.8-live on v1beta in a November 15 test, including a function call, tool response and audio output. The v1alpha workaround is not universally necessary; verify the endpoint with the specific SDK and account before changing the default.
