Step 4 of 4
See your first player.
Run the example in your REST project and check the response there.
Finish setup before confirming your first request. Connect
Run the command in your terminal
Keep userId and accessToken from the response for later requests. ACCESS_TOKEN in feature examples refers to this accessToken.
Here is what should happen
The anonymous player signs in successfully. Your Console, Output or terminal shows a successful response with a player name or userId. You can also check the player in the selected project’s Users area.
Confirm the result from your own project. Existing dashboard players do not prove this new connection.
Open UsersNo response yet?
Check the active project key, JSON import and backend addresses. Restart your project after importing. For a 401, check the full key; for network errors, check the reachable backend address and console output.
Also: check the API in the dashboard
The API Explorer helps with debugging. Still verify the first request from your own game afterwards.