Spinning up a chat UI shouldn’t be the hard part.
Today we’re launching the Vapi Chat Widget, a prebuilt, drop-in component that lets you embed your Vapi assistant directly on your site. Zero backend required. Fully session-aware. Configurable via public key.
Why We Built This
Our chat API gives you full control but not everyone wants to own the UI.
Some teams are shipping fast and just want a working widget. Others are building platforms on top of Vapi and need something embeddable and white-labeled. Even developers building full apps often want a clean baseline they can fork and customize.
This widget exists for all of them.
What You Get
- Drop-in embed for any site (React SDK available)
- Session-based context(24h) via Session API
- Optional voice toggle (chat or voice)
- Switch between chat + SMS with context continuity
- Public key config that works entirely client-side
Built on top of the same chat infra you already use. You don't need any special setup. If your assistant runs on chat, it runs here.
Why This Matters
While you can roll your own UI, you don’t have to. This widget gives you:
- A fast path to production
- A reference implementation to fork or extend
Who It’s For
- Developers who want to ship fast without sacrificing reliability, quality, or customizability
- Platforms that want to embed ai chat assistants across everything from static sites to dynamic React apps
- Teams already using Vapi voice agents who want to add chat support without duplicating infrastructure
What’s Next
Cross-modality sessions (voice + chat memory sharing) are still in the works. Right now, chat and SMS share context; voice is separate. You can bridge them manually via API, but native continuity is coming soon.
Try It
You’ll find the widget, source code, and docs here. Add it to your site in minutes. Then go as deep as you want.
We’re excited to see how you use it and what you build on top.
