Hi team, I’d like to launch an entire Squad (not a single assistant) from a custom “Call” button on my website. • The legacy html-script-tag widget lets you pass

squad

, but it now breaks because it loads an old daily-js build. • The modern Web SDK (@Vapi-ai/web) works great but only accepts

assistantId

/

assistant

in

vapi.start()

and returns 400 when I send

squadId

. Is there a recommended way to start a Squad-level web call (WebRTC) from the browser, or should that always be done via the Server SDK? Thanks in advance!

Hey there! It's recommended to use either the Web SDK or the HTML script tag to use squads. Don't worry about the old build; it won't impact any performance issues with your calls. Regarding the server side SDK, the decision is yours if its required for your product.

I’ve been testing both methods and ran into a bit of a blocker: With the legacy HTML script tag, I can launch the squad, which is great—but I’m struggling to capture the call_id or hook into the session lifecycle programmatically. The embed doesn’t expose enough control for that. On the other hand, the modern Web SDK gives me all the flexibility I need—I can access the call_id, handle events, customize UI, etc. But unfortunately, it doesn’t support squads, and sending a squadId in vapi.start() just returns a 400. Ideally, I’d love to launch a squad-level call with the Web SDK (to get both control and group logic). Is there any workaround for this?

vapi.start(assistantID, assistantConfig, squadID) You need to pass squadID as third parameter, and the first two params as null.