Get a TikTok live room and its status
Run job:tiktok.live.get through the looot API: 2 providers, from $0.001 per call. Inputs, prices, output shape and code for curl, JavaScript and Python.
Get a TikTok live room and its status.
Job id tiktok.live.get, in Social data (TikTok). As of 2026-10-01, 2 providers serve it through 8 tools. Run job:tiktok.live.get and looot picks one of them; with fallback on, a miss moves on to the next. See Jobs.
Inputs
A job run takes shared input names; looot maps them to each provider’s own fields. See Job inputs.
| Input | Taken by |
|---|---|
room_id |
4 of 8 providers |
handle |
2 of 8 providers |
url |
1 of 8 providers |
Any other key you send passes through unchanged. Each tool’s own fields are on its page below.
Providers and prices
| Provider | Tool | Price |
|---|---|---|
| TikHub | tikhub-api-tiktok-web-fetch-live-im-fetch |
$0.001 per call |
| TikHub | tikhub-api-tiktok-web-fetch-tiktok-live-data |
$0.001 per call |
| TikHub | tikhub-api-tiktok-web-fetch-user-live-detail |
$0.001 per call |
| TikHub | tikhub-api-tiktok-web-tiktok-live-room |
$0.001 per call |
| ScrapeCreators | scrapecreators-tiktok-live |
$0.00188 per call |
| ScrapeCreators | scrapecreators-tiktok-user-live |
$0.00188 per call |
| TikHub | tikhub-api-tiktok-web-fetch-check-live-alive |
$0.002 per call |
| TikHub | tikhub-api-tiktok-web-fetch-batch-check-live-alive |
$0.05 per call |
A call that fails at the provider costs $0. See What’s free.
Output
Each provider answers in its own shape. Shape of the run’s result from tikhub-api-tiktok-web-fetch-user-live-detail, checked against 3 real answers:
{ code, data: { data: { user: { ... }, stats: { ... }, liveRoom: { ... } }, extra: { id }, message, statusCode }, docs, time, params: { uniqueId }, router, message, support, cache_url, time_zone, message_zh, request_id, time_stamp, cache_message, cache_message_zh }
Run it
Every call needs your API token in LOOOT_TOKEN; Sign in shows how to get one. Each run also needs a new idempotency key, so a retry never pays twice. With wait: 30 the answer comes back inline when the run ends within 30 seconds. Otherwise you get the running run back: poll GET /v1/runs/<runId>.
Example input with placeholder values:
curl -X POST "https://api.looot.ai/v1/runs" \
-H "Authorization: Bearer $LOOOT_TOKEN" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: $(uuidgen)" \
-d '{"endpointId":"job:tiktok.live.get","input":{"url":"https://example.com"},"wait":30}'const response = await fetch("https://api.looot.ai/v1/runs", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.LOOOT_TOKEN}`,
"Content-Type": "application/json",
"Idempotency-Key": crypto.randomUUID(),
},
body: JSON.stringify({
endpointId: "job:tiktok.live.get",
input: {
url: "https://example.com",
},
wait: 30,
}),
});
const run = await response.json();
console.log(run.status, run.result);import os
import uuid
import requests
response = requests.post(
"https://api.looot.ai/v1/runs",
headers={
"Authorization": f"Bearer {os.environ['LOOOT_TOKEN']}",
"Idempotency-Key": str(uuid.uuid4()),
},
json={
"endpointId": "job:tiktok.live.get",
"input": {
"url": "https://example.com",
},
"wait": 30,
},
timeout=90,
)
run = response.json()
print(run["status"], run.get("result"))To pin one provider, send its tool id as endpointId instead of job:tiktok.live.get.