Step-by-step walkthroughs for testing the two Steam Links endpoints in Postman.
This page assumes you have already set up Postman, your Mokito API environment, and Bearer authentication as described in the API → Testing page. If you haven't, start there first.
{{$baseUrl}}/steam-link/player-profile?discord_id=575805961315287061{{$token}}.If your token is valid and your server has Premium, you will see the JSON response in the lower pane, including the player's Discord account and their Steam connections.
You can also look up a player by Steam ID instead of Discord ID:
{{$baseUrl}}/steam-link/player-profile?steam_id=76561197960435530
Exactly one of discord_id or steam_id must be provided. Sending both returns 422; sending neither returns 422.
{{$baseUrl}}/steam-link/players?limit=25&page=0{{$token}}).The response includes the data array, the meta pagination block, and the X-Total / X-Total-Pages response headers (visible in the Headers tab of the response pane).
You can also filter by creation date:
{{$baseUrl}}/steam-link/players?created_after=2026-01-01T00:00:00Z&page=2&limit=50
page=0, not page=1. The meta.page field in the response is also zero-indexed.
X-RateLimit-Remaining response header to monitor your budget.
For the full rate limit rules, response headers, and ban mechanics, see API → Authorization → Rate Limiting.