Error Handling - Gamification
Error Handling
14.1 Common Errors
| Error | Cause | Resolution |
|---|---|---|
| 401 Unauthorized | Invalid or expired KS | Generate a new ADMIN KS |
| 403 Forbidden | KS lacks GAME_MANAGE permission | Ensure the KS role includes GAME_MANAGE |
| 404 Not Found | Invalid game object ID | Verify the ID with a list call |
| 400 Bad Request | Missing required fields | Include all required fields for the endpoint |
14.2 Permission Errors
Read operations (list, get, userScore/list) require GAME_BASE.
Write operations (create, update, delete) require GAME_MANAGE.
If Game Services is not enabled for your partner account, all endpoints return 403. Enable via Kaltura Admin Console.
14.3 Standard List Filters
All list endpoints support these filter fields:
| Field | Type | Description |
|---|---|---|
idIn | string[] | Filter by specific IDs |
updatedAtGreaterThan | ISO 8601 | Filter by updated date range |
updatedAtLessThan | ISO 8601 | Filter by updated date range |
createdAtGreaterThan | ISO 8601 | Filter by created date range |
createdAtLessThan | ISO 8601 | Filter by created date range |
orderBy | string | Sort field and direction |
pager | object | {pageSize, pageIndex} for pagination |