Chat API & WebSocket

The chat API hands a channel’s chat to other tools – multi-chat overlays, bots, Streamer.bot or your own code. It’s free, read-only and needs no key, and it carries exactly what everyone sees on the channel page. The full reference, with examples and a Try it box, is on /developers.

Your chat’s address

wss://camucam.com/api/v1/chat/ws?channel=yourname

Signed in, /developers shows yours ready to copy – and so does Go live → Settings → Chat overlay for OBS under Other tools. Open a WebSocket to it: every message is one JSON event. Add &history=20 to get the last 20 lines with the first event (up to 50).

What comes through

• chat lines, with their emotes (picture and position) and the line they reply to
• tips with their message and amount in US dollars
• offers and wheel spins, and when they’re done or refunded
• polls while they run, and their result
• emote combos, CamuCam’s own lines – raids, parties, goals – and translations when the streamer turned them on
• removed lines, the viewer count, and when the stream starts or ends

Every line names its author: handle, name, colour, avatar and badges.

Without a WebSocket

The same events also come as server-sent events. Plain HTTP gives you the latest lines (up to 50) and the channel itself – live or not, title, viewers. The addresses are on /developers.

Fair use

• Read only – nobody can write into a chat through the API.
• Up to 10 open connections and 120 requests a minute per IP address.
• When a delete event comes, remove that line. Moderation has to reach every screen.
• No WebSocket pings in your tool? Send {"type":"ping"} now and then.
• Version 1 only grows: new fields and events may come, existing ones stay.

Ready-made

• OBS chat overlay – your CamuCam chat in your video, Twitch’s next to it
• Social Stream Ninja – CamuCam next to Kick, YouTube and the rest
• Streamer.bot – the steps and a C# example are on /developers