Documentation / API / Steam Link Testing
On this page
Your First Request Player Profile List Players Rate Limit

Steam Links — Testing Premium

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.

Your First Request

Player Profile

  1. Click + NewHTTP Request.
  2. Set the method to GET.
  3. Enter the URL: {{$baseUrl}}/steam-link/player-profile?discord_id=575805961315287061
  4. Go to the Authorization tab → type Bearer Token → token: {{$token}}.
  5. Click Send.

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.

List Players

  1. Create another HTTP request, method GET.
  2. URL: {{$baseUrl}}/steam-link/players?limit=25&page=0
  3. Same Authorization setup (Bearer Token with {{$token}}).
  4. Click Send.

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
Pages are zero-indexed. The first page is page=0, not page=1. The meta.page field in the response is also zero-indexed.

Rate Limit

Watch the rate limit in Postman. If you click Send more than 100 times in a minute, your token will be banned for 15–30 minutes. Check the 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.