Web API overview

The GAMPEON web API is what the portal, game servers and the MCP server use. You can use it too, for example to show your servers on your own website or to automate releases.

Base URL	https://api.gampeon.com
Version	/v1/ in every path. Breaking changes get a new version. During the preview, /v1/ can still change; see the changelog.
Format	JSON in and out (Content-Type: application/json). File uploads use application/octet-stream.
Request body	At most 64 KB of JSON. Files have their own limits.
Times	Milliseconds since 1970-01-01 UTC, as numbers.
Description	OpenAPI 3.1: /v1/openapi.json, also at /reference/openapi.json

Reference

The API reference lists every operation with its parameters, answers, required login and rate limit. It is generated from the same description the API server serves, and a test in the platform makes sure every route is described.

Quick examples

Public, no login:

curl https://api.gampeon.com/v1/servers
curl "https://api.gampeon.com/v1/resources?q=garage&kind=vehicle"
curl https://api.gampeon.com/v1/projects/neon-racers

With login:

curl https://api.gampeon.com/v1/me -H "Authorization: Bearer $GAMPEON_TOKEN"

See Authentication for how to get a token and Errors and limits for what can go wrong.

Browsers

The API allows cross-origin requests (CORS) only from the GAMPEON portal. Call it from your own server or scripts, not directly from a browser page on another domain.

For AI assistants

AI assistants should use the MCP server instead of calling the API directly: it adds checks, clear tool descriptions and an activity log.