Live Room

GET/v1/tiktok/live1 credit

Returns a TikTok live room by id: title, cover, like and viewer counts, status and the host.

01Query parameters

Name	Type	Description
room_idrequired	string	The live room's numeric id (`roomId` in the User Live Status response).
user_idoptional	string	The host's user id. Accepted for compatibility; not needed.

02Request

curl "https://api.scrapesocial.ai/v1/tiktok/live?room_id=7523685855395842871" \
  -H "x-api-key: $SCRAPESOCIAL_KEY"

03Responses

Real answers from the API. Lists are shortened to 2 items.

GET /v1/tiktok/live?room_id=7700625972861324065

{
  "success": true,
  "credits_remaining": 4980,
  "credits_charged": 1,
  "room_id": "7700625972861324065",
  "like_count": 0,
  "viewer_count": 5,
  "status": 2,
  "title": "",
  "cover_url": "https://p16-common-sign.tiktokcdn.com/tos-useast2a-avt-0068-euttp/d58764c4552bc4800c6bb20740590c50~tplv-tiktokx-cropcenter:720:720.webp?dr=14579&refresh_token=a8c18134&x-expires=1793120400&x-signature=%2BKag3Sk7d8xu3JvmCs40Nj7PPFw%3D&t=4d5b0474&ps=13740610&shp=a5d48078&shcp=fdd36af4&idc=my2",
  "owner": {
    "id": "7308031192074126369",
    "username": "babagaming_22",
    "display_name": "BABA GAMING"
  }
}

Common to every endpoint

Any route can answer these: a missing or wrong key, no credits left, the platform not answering, or a failure on our side. None of them costs credits.

GET /v1/cosmos/profile?handle=design

{
  "success": false,
  "message": "Invalid API key"
}

04Notes

The answer is `room_id`, `like_count`, `viewer_count`, `status`, `title`, `cover_url` and `owner` (`id`, `username`, `display_name`). A room that has ended is still returned (with its `status`) and costs 1 credit. A non-numeric `room_id` is a free 400; an unknown room is a free 404.

05Errors & credits

Every error has success: false, a real HTTP status and costs no credits.

400missing_parameter
A required parameter is missing or invalid.
403private_account
The account is private or age-restricted.
404not_found
No such account.
503upstream_error
The platform did not answer; retry shortly.