Error codes

This table summarizes the most common error messages returned by the CWS RGS. These help identify issues related to authentication, user management, and integration faults.

Code/ Message	Meaning	How to Fix
Error: No credentials sent	Missing `apiusername` or `apipass` in the request	Ensure both credentials are passed in every API request (see Chapter F)
ERROR 101	Invalid `apiusername` or `apipass`	Verify credentials are correct. Contact support if unsure.
ERROR 253	The user does not exist in the system	Check the `login` or `userid` being used. Ensure the player account is created.
ERROR 301 (if exists)	Invalid `gameid` or inactive game	Make sure you're using a valid, active game ID
ERROR 406 (if exists)	Session expired or already finalized	Request a new game play token or refresh the session
ERROR 409 (if used)	Duplicate transaction	Use a unique `uniqid` for each `balance_adj` or `freespin` call
ERROR 500 (if used)	Internal error	Retry after a delay or contact support

For other error codes, please refer to the documentation section of the method that you have used.

EG: If you try to get list of games and you get an error, see the documentation section of the list of games method to understand the possible problems. Most of the other error messages are intuitive.