Skip to content

Create a runtime app ​

POST /v1/admin/runtime/apps

  • Operation ID: createRuntimeApp
  • Tags: Runtime apps
  • Base URL: http://localhost:8787

runner, stream and other config records are opaque and validated by the runtime (422 invalid_request). Audited as runtime.app_create. Authenticates with a Platform staff JWT and permission, like every admin route; the backend calls the separate Runtime service on the caller's behalf (no Runtime API key is ever exposed or accepted).

Workflow: Integration guide.

Authentication: staff Bearer JWT with permission runtime.write.

Authentication ​

  • Auth: staff Bearer JWT (Authorization: Bearer <access_token>) with the permissions below.
  • Required permissions: runtime.write

Request body ​

Required: yes.

Content type: application/json

Schema: object

FieldTypeRequiredDescription
slugstringyesMin length: 1. Max length: 100
namestringyesMin length: 1. Max length: 200
runnerobjectyes-
streamobjectyes-
enabledbooleanno-
requiresobjectno-
resourcesobjectno-
resources.cpusnumbernoGreater than: 0
resources.memoryMbintegernoMin: 1
resources.gpuobjectno-
resources.gpu.sharenumbernoMin: 1. Max: 100
resources.gpu.vramMbintegernoMin: 1
resources.gpu.visualbooleanno-
resources.runnerCreateobjectno-
assetobjectno-
maxDurationSintegernoGreater than: 0

Example

json
{
  "slug": "example-game",
  "name": "Example Game",
  "runner": {},
  "stream": {},
  "enabled": false
}

Responses ​

201 ​

App created.

  • Header x-request-id: Request identifier; quote it when reporting an error. Content type: application/json

Schema: object (RuntimeApp)

FieldTypeRequiredDescription
idstringyes-
slugstringyes-
namestringyes-
enabledbooleanyes-
runnerobjectyes-
streamobjectyes-
requiresobjectyes-
resourcesobjectyesPer-session resource cost overrides.
resources.cpusnumberno-
resources.memoryMbintegerno-
resources.gpuobjectno-
resources.gpu.sharenumberno-
resources.gpu.vramMbintegerno-
resources.gpu.visualbooleanno-
resources.runnerCreateobjectno-
assetobject | nullyes-
maxDurationSintegeryes-
versionintegeryes-
createdAtintegeryesCreated (Unix epoch milliseconds).
updatedAtintegeryesUpdated (Unix epoch milliseconds).

Errors ​

400 ​

Request validation failed.

  • Header x-request-id: Request identifier; quote it when reporting an error. Content type: application/json

Schema: object (ValidationErrorBody)

FieldTypeRequiredDescription
successbooleanyesOne of: false
errorobjectyes-
error.namestringyesOne of: "ZodError"
error.issuesobject[]yes-
error.issues[].codestringyes-
error.issues[].path(string | number)[]yes-
error.issues[].messagestringyes-

Request validation

json
{
  "success": false,
  "error": {
    "name": "ZodError",
    "issues": [
      {
        "code": "custom",
        "path": [
          "field"
        ],
        "message": "Invalid value"
      }
    ]
  }
}

401 ​

Missing, malformed, expired or wrong-audience Bearer token (missing_token, invalid_token, invalid_audience).

  • Header x-request-id: Request identifier; quote it when reporting an error. Content type: application/json

Schema: object (ErrorBody)

FieldTypeRequiredDescription
errorstringyesStable machine-readable error code, e.g. forbidden, not_found.
detailsanynoOptional structured context. For 403 it is { perm }.

Error response

json
{
  "error": "missing_token"
}

403 ​

Authenticated but lacking the required permission. details.perm lists the accepted permission keys.

  • Header x-request-id: Request identifier; quote it when reporting an error. Content type: application/json

Schema: object (ErrorBody), fields as described above.

Error response

json
{
  "error": "forbidden",
  "details": {
    "perm": "runtime.write"
  }
}

404 ​

not_found: the runtime does not know this resource.

  • Header x-request-id: Request identifier; quote it when reporting an error. Content type: application/json

Schema: object (ErrorBody), fields as described above.

Error response

json
{
  "error": "not_found"
}

409 ​

conflict: the runtime rejected the change (details carry its message).

  • Header x-request-id: Request identifier; quote it when reporting an error. Content type: application/json

Schema: object (ErrorBody), fields as described above.

Error response

json
{
  "error": "conflict"
}

422 ​

invalid_request: the runtime rejected the payload (details carry its message).

  • Header x-request-id: Request identifier; quote it when reporting an error. Content type: application/json

Schema: object (ErrorBody), fields as described above.

Error response

json
{
  "error": "invalid_request"
}

500 ​

Unexpected server error (internal). No details are returned.

  • Header x-request-id: Request identifier; quote it when reporting an error. Content type: application/json

Schema: object (ErrorBody), fields as described above.

Error response

json
{
  "error": "internal"
}

503 ​

unavailable: the runtime could not be reached; retry.

  • Header x-request-id: Request identifier; quote it when reporting an error. Content type: application/json

Schema: object (ErrorBody), fields as described above.

Error response

json
{
  "error": "unavailable"
}

Examples ​

curl ​

bash
curl -X POST 'http://localhost:8787/v1/admin/runtime/apps' \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H 'Content-Type: application/json' \
  --data '{"slug":"example-game","name":"Example Game","runner":{},"stream":{},"enabled":false}'

TypeScript ​

ts
const accessToken = process.env.ACCESS_TOKEN; // user JWT from your sign-in flow

const response = await fetch("http://localhost:8787/v1/admin/runtime/apps", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${accessToken}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    "slug": "example-game",
    "name": "Example Game",
    "runner": {},
    "stream": {},
    "enabled": false
  }),
});
if (!response.ok) throw new Error(`HTTP ${response.status}: ${await response.text()}`);
const data = response.status === 204 || response.status === 205
  ? undefined
  : response.headers.get("content-type")?.includes("json")
    ? await response.json()
    : await response.text();

Try this endpoint

Requests go directly from your browser to the API. Send request executes this endpoint against the selected server.

POST/v1/admin/runtime/apps

Your token stays in this tab's memory and is sent only when you press Send request.

Request body (required)

Built for developers. Ready for agents.