Create a game

POST /v1/admin/store/games

• Operation ID: createStoreGame
• Tags: Store games
• Base URL: http://localhost:8787

Creates the game row and links the given genres/developers/publishers. Writes go through audited database functions. Emits a dashboard event.

Workflow: Integration guide.

Authentication: staff Bearer JWT with permission store.write.

Authentication

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

Request body

Required: yes.

Content type: application/json

Schema: object

Field	Type	Required	Description
slug	string	yes	Pattern: ^[a-z0-9][a-z0-9-]{0,127}$
title	string	yes	Min length: 1. Max length: 200
summary	string	no	Max length: 2000
description	string	no	Max length: 20000
game_type	string	no	One of: "app", "game", "launcher". Default: "game"
status	string	no	One of: "draft", "published", "hidden". Default: "draft"
release_date	string<date>	no	-
controller_support	string	no	One of: "none", "partial", "full". Default: "none"
website	string<uri> | null	no	Max length: 500
required_age	integer	no	Default: 0. Min: 0. Max: 21
legal_notice	string | null	no	Max length: 5000
license_required	boolean	no	Default: false
content_description	string | null	no	Max length: 5000
genre_ids	integer[]	no	Max items: 50
developer_ids	integer[]	no	Max items: 50
publisher_ids	integer[]	no	Max items: 50

Example

{
  "slug": "example-game",
  "title": "Example Game",
  "status": "draft"
}

Responses

201

Created game row (without art or links).

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

Schema: object (StoreGame)

Field	Type	Required	Description
id	integer	yes	-
slug	string	yes	-
title	string	yes	-
summary	string | null	yes	-
description	string | null	yes	-
game_type	string	yes	One of: "app", "game", "launcher"
status	string	yes	One of: "draft", "published", "hidden"
release_date	string | null	yes	Date, YYYY-MM-DD.
controller_support	string	yes	One of: "none", "partial", "full"
website	string | null	yes	-
required_age	integer	yes	-
legal_notice	string | null	yes	-
license_required	boolean	yes	-
content_description	string | null	yes	-
metadata	object	yes	-
created_at	string	yes	ISO 8601 timestamp.
updated_at	string	yes	ISO 8601 timestamp.

Errors

400

Request validation failed.

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

Schema: object (ValidationErrorBody)

Field	Type	Required	Description
success	boolean	yes	One of: false
error	object	yes	-
error.name	string	yes	One of: "ZodError"
error.issues	object[]	yes	-
error.issues[].code	string	yes	-
error.issues[].path	(string | number)[]	yes	-
error.issues[].message	string	yes	-

Request validation

{
  "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)

Field	Type	Required	Description
error	string	yes	Stable machine-readable error code, e.g. forbidden, not_found.
details	any	no	Optional structured context. For 403 it is { perm }.

Error response

{
  "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

{
  "error": "forbidden",
  "details": {
    "perm": "store.write"
  }
}

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

{
  "error": "internal"
}

Examples

curl

curl -X POST 'http://localhost:8787/v1/admin/store/games' \
  -H "Authorization: Bearer $ACCESS_TOKEN" \
  -H 'Content-Type: application/json' \
  --data '{"slug":"example-game","title":"Example Game","status":"draft"}'

TypeScript

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

const response = await fetch("http://localhost:8787/v1/admin/store/games", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${accessToken}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    "slug": "example-game",
    "title": "Example Game",
    "status": "draft"
  }),
});
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();