GameQuery API

Back to Docs Page

Raw markdown source view for LLM workflows.

---
title: GameQuery API
description: Query game servers, track runtime data, and integrate status feeds with predictable API contracts.
---

GameQuery is built for developers who need stable server telemetry and simple ingestion flows.

With a single API key, you can fetch live payloads and consume updater metadata for dashboards, bots, and analytics jobs.

## API host

- Production API base URL: `https://api.gamequery.dev`
- Current stable API version: `v1`

## What you can do

- Fetch the supported game catalog.
- Query live runtime payloads in batches.
- Auto-insert valid unknown `game_id + ip:port` pairs while fetching.
- Read per-server updater metadata for freshness-aware clients.
- Capture invalid input diagnostics from `_meta.invalid_servers`.

<Cards>
  <Card title="Quickstart" href="/docs/quickstart" description="Go from API key to first payload in minutes." />
  <Card title="Versioning and Migration" href="/docs/versioning-and-migration" description="Set up your client now so upgrading from v1 to v2 is low risk." />
  <Card title="Authentication" href="/docs/authentication" description="Understand headers, package types, and whitelist behavior." />
  <Card title="Endpoint Reference" href="/docs/endpoints/get-games" description="See request and response contracts for active v1 routes." />
  <Card title="Integration Guides" href="/docs/guides/nodejs-integration" description="Production-friendly Node.js and Python examples." />
  <Card title="LLM Integration" href="/docs/llms-full" description="Optimize your API for AI Agents and LLM function calling." />
</Cards>

## Endpoint map

| Method | Path | Auth required | Purpose |
| --- | --- | --- | --- |
| `GET` | `/v1/get/games` | No | Returns supported game IDs (`id`, `name`). |
| `POST` | `/v1/post/fetch` | Yes | Returns live payloads and auto-inserts valid pairs. |

## Compatibility note

The active public v1 contract consists of `GET /v1/get/games` and `POST /v1/post/fetch`.
Legacy routes are not part of the current API surface.