Players

Players are the end-users of your game or application who submit support tickets. Players are identified by a unique ID from your system. Keme stores profile data to provide context to support agents — including display name, email, metadata, ticket history, and activity timestamps.

All player endpoints are scoped to a workspace. The workspaceId field is required whenever it cannot be inferred from the authenticated API key. Player objects returned by the API use Keme's internal id (prefixed kpl_) in addition to your own playerId.

Create or Update Player

Upserts a player record. If a player with the given playerId and workspaceId already exists, their profile is updated in place. Otherwise a new player record is created. Call this endpoint when a player first authenticates in your game, or whenever their profile data changes.

1{
2  "id": "kpl_xxxx",
3  "playerId": "player_12345",
4  "workspaceId": "ws_xxxx",
5  "displayName": "GamerTag_XYZ",
6  "email": "player@example.com",
7  "ticketCount": 3,
8  "metadata": {
9    "level": "42"
10  },
11  "firstSeenAt": "2025-01-15T08: 32: 00Z",
12  "lastSeenAt": "2026-06-15T14: 07: 22Z"
13}

Get Player

Retrieve a player record by their Keme-assigned internal ID (kpl_...). Use this endpoint when you have the Keme ID from a previous API response or webhook payload. To look up by your own external player ID, use the GET /v1/players/lookup endpoint instead.

1{
2  "id": "kpl_xxxx",
3  "playerId": "player_12345",
4  "workspaceId": "ws_xxxx",
5  "displayName": "GamerTag_XYZ",
6  "email": "player@example.com",
7  "ticketCount": 3,
8  "metadata": {
9    "level": "42",
10    "platform": "PC",
11    "region": "EU"
12  },
13  "firstSeenAt": "2025-01-15T08: 32: 00Z",
14  "lastSeenAt": "2026-06-15T14: 07: 22Z"
15}

Lookup Player by External ID

Find a player using your own external playerId rather than Keme's internal ID. This is the most common retrieval pattern — you pass the player ID from your game backend and receive the full Keme player object including their Keme ID, ticket count, and metadata.

1{
2  "id": "kpl_xxxx",
3  "playerId": "player_12345",
4  "workspaceId": "ws_xxxx",
5  "displayName": "GamerTag_XYZ",
6  "email": "player@example.com",
7  "ticketCount": 3,
8  "metadata": {
9    "level": "42"
10  },
11  "firstSeenAt": "2025-01-15T08: 32: 00Z",
12  "lastSeenAt": "2026-06-15T14: 07: 22Z"
13}

List Player Tickets

Returns the paginated list of support tickets associated with a specific player. Results are ordered by creation date descending (most recent first). Use the status filter to narrow the response to tickets in a particular state.

1{
2  "total": 5,
3  "data": [
4    {
5      "id": "tkt_xxxx",
6      "title": "Items disappeared from inventory after server rollback",
7      "status": "open",
8      "createdAt": "2026-06-14T10: 22: 00Z"
9    },
10    {
11      "id": "tkt_yyyy",
12      "title": "Unable to complete Season 3 battle pass quest",
13      "status": "resolved",
14      "createdAt": "2026-05-30T08: 15: 00Z"
15    }
16  ]
17}

Delete Player (GDPR Erasure)

Permanently deletes a player's profile and anonymises all associated ticket history. This endpoint fulfils GDPR Article 17 right-to-erasure requests. Personal data — including display name, email address, and metadata — is purged from Keme's systems. Tickets are retained in anonymised form for operational integrity but can no longer be linked back to the player.

Player Object Reference

The following fields are present on every player object returned by the API.

Error Codes

The Players API returns standard HTTP status codes. Common error responses are listed below.

• 400 Bad Request — Missing required fields (workspaceId or playerId), invalid metadata structure, or metadata exceeds 50 keys.
• 401 Unauthorized — Missing or invalid API key. Include your key in the Authorization: Bearer <key> header.
• 403 Forbidden — The authenticated API key does not have access to the specified workspace.
• 404 Not Found — No player found with the given id or playerId + workspaceId combination.
• 429 Too Many Requests — Rate limit exceeded. Retry after the duration specified in the Retry-After response header.