Username API

Game Username Lookup API for reseller platforms

Validate supported player IDs from your server before order creation using the same LioGames partner authentication model.

Username lookup API

Use this endpoint to validate a supported player/user ID and return the game username before creating an order.

POSThttps://distribution.liogames.com/api/v1/username-check

Supported games

Mobile Legends: Bang Bangmobile-legendsUser ID + Server ID
Free Fire Globalfree-fire-globalUser / Player ID
Honkai: Star Railhonkai-star-railUser ID + Server ID
Honor of Kingshonor-of-kingsUser / Player ID
Magic Chess: Go Gomagic-chess-go-goUser ID + Server ID
PUBG Mobile Globalpubg-mobile-globalUser / Player ID
PUBG Mobile Litepubg-mobile-liteUser / Player ID
Stumble Guysstumble-guysUser / Player ID
Super Sussuper-susUser / Player ID
Yalla Ludoyalla-ludoUser / Player ID
Zenless Zone Zerozenless-zone-zeroUser ID + Server ID
JawakerjawakerUser / Player ID
Blood Strikeblood-strikeUser ID + Server ID
Genshin Impactgenshin-impactUser ID + Server ID

Authentication

Partner API calls require member_code plus x-liog-sign, generated from the exact raw JSON body with your private Secret.

$signature = hash_hmac('sha256', $rawJson, $secret);

Request body

{
  "member_code": "YOUR_MEMBER_CODE",
  "game": "mobile-legends",
  "user_id": "1393323764",
  "server_id": "15748"
}

server_id is required only for games configured with a server/zone field.

Response

{
  "ok": true,
  "found": true,
  "game": "MLBB",
  "username": "PLAYER_NAME",
  "server_id": "15748"
}

Region or account-status fields are returned when available for the selected game.

cURL example

BODY='{"member_code":"YOUR_MEMBER_CODE","game":"mobile-legends","user_id":"1393323764","server_id":"15748"}'
SIGNATURE=$(php -r 'echo hash_hmac("sha256", $argv[1], "YOUR_SECRET");' "$BODY")

curl -X POST 'https://distribution.liogames.com/api/v1/username-check' \
  -H 'Content-Type: application/json' \
  -H "x-liog-sign: $SIGNATURE" \
  --data "$BODY"

Usage & caching

Successful lookups are cached server-side for a short period to improve speed and reduce repeated upstream checks. Integrations should validate input before sending requests and avoid rapid repeated checks for the same player ID.