BIGO — Identify User

#GET /bigo/user/{bigo_id}

Resolve a public BIGO LIVE ID to the account's trusted identity before recharging. Show the nickname and avatar to your customer for confirmation, then pass bigo_uid to the recharge call.


Method	`GET`
URL	`https://api.boostigo.io/bigo/user/{bigo_id}`
Auth	`Authorization: Bearer YOUR_API_KEY` (a BIGO API key)

#Path parameters

Name	Type	Description
`bigo_id`	string	The public BIGO ID your customer typed (2–40 chars: letters, digits, `_ . -`), e.g. `yehya_aali`.

#Request

curl --request GET \
  "https://api.boostigo.io/bigo/user/yehya_aali" \
  --header "Authorization: Bearer YOUR_API_KEY" \
  --header "Accept: application/json"

#Response `200`

{
  "success": true,
  "data": {
    "platform": "bigo",
    "user": {
      "bigo_id": "yehya_aali",
      "bigo_uid": "502030637",
      "nickname": "يحيى 🇱🇧",
      "avatar": "https://esx.bigo.sg/…/avatar.jpg",
      "country": null
    }
  }
}

Field	Always present	Description
`bigo_id`	yes	Echo of the requested ID (canonical casing from BIGO)
`bigo_uid`	yes	Internal BIGO UID — required in `POST /bigo/recharge`
`nickname`	yes	Display name (may contain emoji)
`avatar`	optional	Signed image URL — display it, do not store it
`country`	optional	Often `null` for BIGO accounts

#Errors

HTTP	code	When
422	`INVALID_BIGO_ID`	Malformed ID
404	`USER_NOT_FOUND`	BIGO knows no such account
503	`SERVICE_UNAVAILABLE`	BIGO lookup temporarily unreachable — retry with backoff

Everything else (authentication, rate limits, response envelope) is identical to the Likee endpoints.