Integrate your games with TikXander

What is local game integration?

Local integration means your game or widget runs as a normal web page (browser, OBS Browser Source, or desktop WebView) and connects to a WebSocket on the streamer's machine. The Local Agent is the bridge: it handles the TikTok Live connection (including browser-mode capture) and fans out normalized events to apps that the streamer has allowed.

Events stay on localhost (127.0.0.1). Your game never needs a public backend to receive gifts during the stream — ideal for OBS overlays, custom minigames and developer prototypes.

Who is this for?

• Game and widget developers who want TikTok Live gifts and chat to drive gameplay.
• Studios building OBS overlays that react to gift, like, follow and chat in real time.
• Creators and teams prototyping custom interactive formats before publishing a full product.
• Anyone who prefers a local, low-latency event pipe on the streamer's PC instead of only cloud relays.

How it works

1) The streamer installs and signs into the TikXander Local Agent, then starts capturing the live (browser-mode on the agent is the preferred path).

2) Your app connects to the local event channel on port 8767. Two public surfaces exist on the same localhost server: the versioned developer channel at ws://127.0.0.1:8767/events/v1 (query app id / permissions) and the local DAPI channel at ws://127.0.0.1:8767/dapi for lightweight local consumers.

3) When a viewer sends a gift, likes, chats or follows, the agent emits a normalized event frame. Your game maps that frame to spawn enemies, fill progress bars, show alerts or update scores.

4) Optional helpers on the same host include long-poll (/events/v1/poll), simulate (POST /events/v1/simulate) and status (GET /events/v1/status) so you can develop without a full live every time.

Local endpoints (streamer PC)

• WebSocket developer API: ws://127.0.0.1:8767/events/v1 — versioned, app-scoped events for games and widgets.
• WebSocket local DAPI: ws://127.0.0.1:8767/dapi — local event stream for integrations on the same machine.
• HTTP helpers (same port): /events/v1/poll, /events/v1/simulate, /events/v1/status — poll, inject test events and diagnose presence.
• Bind is localhost only (127.0.0.1:8767): traffic does not leave the streamer's PC for this channel.

Event types you can react to

• gift — viewer gift with identity and gift metadata (streaks resolved before fan-out).
• like — likes during the live (great for soft progress and speed boosts).
• chat — comments for keyword games, polls and shout-outs.
• follow / join — growth moments for welcome effects and counters.
• live_status — session started/ended so your UI can idle cleanly when the capture stops.

How to get started

1. 1. Create a TikXander account

   Sign up at games.tikxander.com — the same dashboard streamers use to manage games, plans and live tools.

2. 2. Install the Local Agent

   Use the Local Agent product page to understand overlays, widgets and the desktop agent that exposes the localhost event ports.

3. 3. Connect your game to localhost

   Open a WebSocket to ws://127.0.0.1:8767/events/v1 (with your app id when required) or ws://127.0.0.1:8767/dapi, parse gift/like/chat/follow frames, and map them to your game logic.

4. 4. Test without a full live

   Use POST /events/v1/simulate and GET /events/v1/status on the same host to inject fake gifts and verify your handlers before going on air.

5. 5. Ship with the streamer workflow

   When you are ready, streamers can pair your experience with TikXander's catalog, widgets and live session tools from the dashboard.

Why developers choose TikXander

You get a real-time event pipe next to OBS, clear event types (gift, like, chat, follow), simulation for development, and a product surface streamers already trust for interactive TikTok Live. Plans and the dashboard live at games.tikxander.com; marketing and docs for the Local Agent live on this site under the local-agent path for each language.

Frequently asked questions