POST /application/{name}/tags — Enable an image tag

POST https://api.sandbox-gameye.gameye.net/application/{name}/tags

Enables a specific image tag for an application and triggers pre-loading across Gameye’s fleet. Once a tag is pre-loaded, sessions using that tag start faster. If the tag is already enabled, calling this endpoint again may bring it forward in preload priority. Publish a unique tag for each new build: nodes cache repository/tag pairs, so re-enabling a mutable tag does not guarantee a fresh download.

Use a setup token with both application:write and regions:read scopes. For a private GitHub Container Registry image, see Getting started with GHCR, which can also register new tags automatically with a webhook.

Path Parameters

Parameter	Type	Required	Description
name	string	Yes	The name of the application.

Request Body

Field	Type	Required	Description	Example
tag	string	Yes	The Docker image tag to enable.	"v1.2.3"

Code Examples

cURL

curl -X POST 'https://api.sandbox-gameye.gameye.net/application/my-game-server/tags' \
--header 'Authorization: Bearer YOUR_TOKEN' \
--header 'Content-Type: application/json' \
--data '{ "tag": "v1.2.3" }'

JavaScript

const response = await fetch('https://api.sandbox-gameye.gameye.net/application/my-game-server/tags', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer YOUR_TOKEN',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({ tag: 'v1.2.3' }),
});

Python

import requests

response = requests.post(
    'https://api.sandbox-gameye.gameye.net/application/my-game-server/tags',
    headers={
        'Authorization': 'Bearer YOUR_TOKEN',
        'Content-Type': 'application/json',
    },
    json={'tag': 'v1.2.3'},
)

Responses

204

The tag was successfully enabled. Pre-loading has been initiated. No response body.

401

You are not authorized. Make sure your bearer token is correct.

403

Your API token does not have the required permissions to invoke this endpoint.

404

The application could not be found. Tag enablement does not verify upstream availability; confirm that the publishing workflow succeeded and check fleet availability before starting a session.

422

Bad request. The given request has invalid syntax.