TikTok LIVE Room by User API

Endpoint facts

Method

GET

API path

/tiktok/mobile/live/room-by-user

Auth

apiKey

Credits

8 credits/request

Charged on

Successful 2xx responses only

Platform

TikTok

Execution

Managed browser rendering where the target needs it

Response schema

#/definitions/tiktokmobile.liveRoomInfoResponseDoc

How this endpoint behaves

The LIVE room a user is currently streaming, keyed by user_id. The upstream is GET /webcast/room/info_by_user/ on the webcast edge host (no x-tt-ttnet-origin-host header), captured from the running 47.4.3 app and reproduced end-to-end against the live gateway.

Same room payload as live/room. The response carries the same projections as /api/v1/tiktok/mobile/live/room: title, status (2 = live), user_count (concurrent viewers), create_time, owner (user id, nickname, avatar), stats (cumulative enter_count / total_user, watch_user_count, like/comment/share/follow counters, replay_viewers), stream (flv_pull_url per resolution plus default_resolution/candidate_resolution, HLS/RTMP URLs) and cover, with the ~500-key upstream room object unmodified in data. The difference is the address: you give a user, and the response fills room_id from the payload, echoing both user_id and room_id.

user_id is the address. anchor_id alone answers a 57-byte empty payload, and a bare call answers the same 57-byte empty success envelope — so this endpoint requires user_id rather than silently returning nothing. A user who is not live answers the webcast status 30003 "room has finished", surfaced as a 400.

Two measured webcast hosts answer this route; the other six answer 403, so the service uses the family's measured edge.

Query parameters:

• user_id: required. The numeric TikTok user id (profile owner id, video author id, or the owner.user_id that live/room returns).

Errors:

• 400 — user_id is missing or not numeric (upstream 10011), or the user has no live room right now (upstream 30003 "room has finished").
• 500 — the upstream failed (including login-gated states).

Measured 2026-10-22:

Example request:

GET /api/v1/tiktok/mobile/live/room-by-user?user_id=6707748031095751686

Example response (truncated):

{
  "code": 200,
  "msg": "OK",
  "data": {
    "room_id": "7699244186013010702",
    "user_id": "6707748031095751686",
    "title": "",
    "status": 2,
    "user_count": 468,
    "create_time": 1792608000,
    "owner": {"user_id": "6707748031095751686", "nickname": "kira lise🐉", "avatar_url": {"url_list": ["..."]}},
    "stats": {"enter_count": 1200, "total_user": 1300, "watch_user_count": 1300},
    "stream": {"flv_pull_url": {"FULL_HD1": "https://pull-flv-...tiktokcdn.com/...flv"}, "candidate_resolution": ["SD1", "SD2", "HD1", "FULL_HD1"]},
    "cover": {"uri": "...", "url_list": ["..."]},
    "data": {"title": "", "status": 2, "...": "the upstream room object"},
    "host": "webcast16-normal-c-useast2a.tiktokv.com",
    "fetched_at": "2026-10-22T08:16:12Z"
  }
}

Notes for callers:

• Use this route when you have a creator's user id and want to know whether they are live; use live/room when you already have a room id (e.g. from live/search).
• A 400 means "this user is not live right now", not a transient failure; re-discover later instead of retrying.
• Some rooms carry an empty title (measured on one live room); the rest of the payload is complete.

Shared guides

Related