Gameye Tag API
The Tag API from Gameye — 1 operation(s) for tag.
The Tag API from Gameye — 1 operation(s) for tag.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.curl "https://apis.io/api/v1/apis/gameye:gameye-tag-api"
curl "https://apis.io/api/v1/apis?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: Gameye Session Tag API
version: 1.2.1
description: 'The Gameye Session API offers an agnostic way of hosting containerized game sessions without having to worry about geographic capacity or scalability issues. The API offers a complete suite of features to host a server based multiplayer game.
# Authentication
All endpoints of the Gameye Session API require authorization. This is done through Bearer Token Authentication. A bearer token is thus required in the HTTP header of each request.
For example: ```Authorization: Bearer ```'
x-logo:
url: https://static.gameye.com/images/android-chrome-512x512.png
altText: Gameye Logo
servers:
- url: https://api.sandbox-gameye.gameye.net
description: The main sandbox environment.
- url: https://api.production-gameye.gameye.net
description: The main production environment.
tags:
- name: Tag
paths:
/tag/{region}/{image}/{version}:
parameters:
- name: region
in: path
required: true
schema:
type: string
description: The name of the region
- name: image
in: path
required: true
schema:
type: string
description: The id of the image
- name: version
in: path
required: true
schema:
type: string
description: The image version otherwise known as the Docker 'tag'.
get:
operationId: tag-exists
summary: Check if tag exists in the Gameye fleet
security:
- api-token:
- regions:read
responses:
200:
description: Ok
content:
application/json:
schema:
$ref: '#/components/schemas/TagOk'
400:
description: 'Bad request.
'
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
401:
description: 'You are not authorized. Please make sure that
the included bearer token is correct.
'
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
403:
description: 'Your API token may not have the required permissions to invoke this endpoint.
'
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
404:
description: 'Image not found or you are not authorized to use this image.
'
content:
application/json:
schema:
$ref: '#/components/schemas/ErrorResponse'
tags:
- Tag
components:
schemas:
ErrorResponse:
type: object
required:
- statusCode
- code
- message
- details
- path
- identifier
- timestamp
properties:
statusCode:
type: integer
code:
type: string
message:
type: string
details:
type: string
path:
type: string
timestamp:
type: string
identifier:
type: string
violations:
type: array
items:
$ref: '#/components/schemas/FieldViolation'
FieldViolation:
type: object
additionalProperties: false
required:
- field
- description
properties:
field:
type: string
description:
type: string
TagOk:
type: object
required:
- exists
properties:
exists:
type: boolean
securitySchemes:
api-token:
type: http
scheme: bearer
bearerFormat: token
externalDocs:
url: https://docs.gameye.com
x-provenance:
method: harvested
publisher: Gameye
source: https://api.production-gameye.gameye.net/openapi.yaml
note: split by refine-openapis from the provider's own published document, verified by fetch (openapi/_original/*.fetch.json);
stamped by stamp-openapi-provenance.py (roadmap#793)