Inngame documentation
Add a support chat to your game, answer players from your inbox, Telegram or Discord, and let AI agents help through the API.
Unity quickstartInstall the package, configure your app key, open the chat. About 15 minutes.
iOS SDKSwift package for SwiftUI and UIKit apps (iOS 16+).
Web SDKOne script tag for HTML5 games and web apps.
Player identityAnonymous players, signed JWTs and Steam tickets.
Agents, MCP & CLIRun support from Claude Code, Cursor or Codex.
REST API & webhooksEndpoints, scopes, signed events.
IntegrationsTelegram, Discord, Steam, GitHub, payments, push, RevenueCat.
Set up in five steps
- Create your account. Sign in at app.inngame.app with Google, GitHub or an email link. You get an organization and a 14-day trial.
- Create an app for each game (or each platform build, if you prefer separate inboxes). Each app has a public app key (
app_…) and a private identity secret. - Install the SDK in your game: Unity for games, Swift for iOS apps, one script tag for web games. Or paste the output of
npx inngame init unityinto your coding agent (install in one prompt). - Choose where your team answers: the web inbox works out of the box; connect Telegram or Discord if you like.
- Decide what the AI does (Settings → AI): off, draft or auto. Import your FAQ first so it has something to answer from.
Concepts
| Thing | What it is |
|---|---|
| Organization | Your studio. Holds members (Admin or Member), apps, API keys, webhooks and the subscription. |
| App | One game or app. Has its own settings: appearance, AI mode, translation, moderation, FAQ, integrations. |
| Player | A person playing your game (an "end user" in the API). Starts anonymous on a device, can be identified so history follows them across devices. |
| Conversation | The thread between a player and your team. One open thread per player per app; it can be closed, snoozed, reopened, tagged and assigned. |
| Message | From the player, the team, the AI, or an internal note (never shown to the player). Carries translations, attachments, an optional card and, for player messages, the game context. |
| Card | An interactive message: review request, offer, link, game screen, claimable item, Apple refund sheet, restore purchases. |
Keys and secrets
| Key | Looks like | Where it goes |
|---|---|---|
| App key | app_… | In your game build. Public: it only lets a device open a chat for that app. |
| Identity secret | random string | On your game server only. Signs the JWTs that verify players. Rotate it from the app settings. |
| API key | ig_sk_… | For agents, scripts, the CLI and MCP. Scoped to read, reply or all. Shown once. Details. |
| Webhook secret | whsec_… | On the server that receives webhooks, to check signatures. |
Base URL
The hosted service runs at:
https://app.inngame.appThe REST API lives under /v1, the SDK endpoints under /v1/sdk, and the MCP server at /mcp. The SDKs and CLI use this URL by default; you can override it (InngameOptions.BaseUrl in Unity, baseURL: in Swift, INNGAME_URL for the CLI).
The previous address, https://inngame.meffysto.workers.dev, keeps working for the API, the SDK endpoints, real time, webhooks and the MCP server: games and integrations that already use it need no change. SDK 0.2.1 and earlier still default to it; 0.2.2 and later default to https://app.inngame.app.