GameDesk

Developer documentation · Web forms

One support form backend. Three ways to integrate.

Choose how much of the player-facing experience your team wants to build. Every option uses the same GameDesk validation, ticket creation, routing, and audit trail.

Public browser APIVersioned schemaCustom fields

Choose your integration

Start with the amount of control you need.

Available now

Headless API

Build every part of the form yourself with normal GET and POST requests.

Best for custom design systems and bespoke player flows.Read the API guide →In development

npm widget

Install a maintained form component in a React, Next.js, or other bundled app.

Best for product teams that want a fast default UI.See the planned install →Planned

Copy-paste script

Add a form to a CMS or plain website with a small pinned script and element.

Best for teams without a frontend build system.See the planned install →

Shared setup

Every integration starts in the dashboard.

  1. Open the web-form settings.In GameDesk, go to Games & integrations → Manage web form.
  2. Publish the exact website origin.Use only the scheme, host, and port—for example https://studio.example or http://localhost:5500. Never include a path.
  3. Copy the public installation key.It identifies this game’s form. It is safe in browser code, but is not a staff credential.
One backend contract.Widgets are convenience renderers. The Headless API remains available whenever a studio needs complete visual control.

Studio email

Use safe context in agent responses.

Studio email response formats and signatures can insert ticket-aware variables, resolved only by GameDesk at send time.

Read the email response variable reference →