Errors and Limits

Understand status codes, validation errors, and request constraints.

View as Markdown

Common HTTP responses

Status	When it happens	Typical body
`400`	Invalid JSON, malformed body, invalid route params	`{"error":"POST_2","message":"Invalid request format"}`
`401`	Missing or invalid auth headers	`{"message":"API token is required"}`
`403`	Request blocked by API key whitelist settings	`{"message":"Request origin is blocked by API key whitelist settings"}`
`405`	Method is not allowed for the endpoint	`{"error":"POST_1","message":"Method Not Allowed. Only POST requests are accepted."}`
`429`	Daily quota exceeded for non-PRO key	`{"message":"Daily quota exceeded for this API key","quota":1440,"used":1440}`
`500`	Internal server/database/redis failure	`{"message":"Internal server error"}`

Validation limits

Maximum 1000 server entries per request.
Server address format must match IPv4 ip:port.
servers must be an array for POST /v1/post/fetch.
GET /v1/get/games does not require auth and returns gzip-compressed JSON.

Partial success behavior

Batch endpoints do not fail the full request when some rows are invalid.

Instead, they return diagnostics:

_meta.invalid_servers
_meta.inserted_servers
_meta.auto_inserted

Treat these fields as first-class output in your ingestion pipeline.

LLM Integration Guide

A specialized guide for Large Language Models (LLMs), AI Agents, and developers building AI-powered game server tools.

GET /v1/get/games

Returns the supported game catalog in id/name format.

On this page

Common HTTP responses Validation limits Partial success behavior