SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillslinkfox-chuhaijiang-tiktok-live

linkfox-chuhaijiang-tiktok-live

Data & analytics

View repository

Updated 10-16 00:00

About this skill

TikTok Live Commerce Intelligence

Use this skill to research public TikTok livestream commerce: discover live sessions with market filters, inspect one session and its performance metrics, or identify the products sold in that session.

Core Concepts

  • This is read-only public-market research. It does not start, moderate, schedule, or manage a TikTok livestream.
  • Search returns data.items[] plus data.total_count. Reuse a search item's string id for detail or related-product calls.
  • Detail returns identity and creator context in data.items[]; include=core additionally returns performance metrics in data.core.items[].
  • Related-product rows use tiktok_live_detail_product_* fields. Read references/api.md before interpreting them.
  • Money fields are objects such as { "unit": "US", "value": 2015752.25 }. Preserve both fields and do not silently relabel or convert the unit.
  • A requested country is query context; preserve the row-level country_code because it is authoritative for the returned record.

Data Fields

Field Meaning
data.total_count Total matching live sessions or products
data.items[].id Live room ID, or product ID on the related-products endpoint
title / room_link Live title and public room URL
user_id / user_unique_id Host identifiers
gmv / gpm / opm Revenue, GMV per thousand viewers, and orders per thousand viewers
total_sold_count / product_count Units sold and products promoted in the live
total_user / max_user_count Total and peak audience counts
data.core.items[] Optional normalized performance metrics from detail include=core
tiktok_live_detail_product_* Related product, seller, price, sales, GMV, commission, and conversion fields

Endpoints

User goal Endpoint Script
Search public livestreams /chuhaijiang/lives/search chuhaijiang_live_search.py
Inspect one livestream /chuhaijiang/lives/detail chuhaijiang_live_detail.py
Find products sold in a livestream /chuhaijiang/lives/related-products chuhaijiang_live_related_products.py

Call only the endpoint needed for the user's current question. Do not automatically drill from search to detail or products because each endpoint is billed independently.

Parameter Guide

  • country: required lowercase marketplace code: br,de,es,fr,gb,id,it,jp,mx,my,ph,sg,th,us,vn.
  • page: starts at 1. Search and related products accept pageSize up to 10.
  • id: required for detail and related products. Pass 19-digit IDs as JSON strings to preserve precision.
  • include: detail-only optional string; use core when normalized performance metrics are needed.
  • Search supports keyword, category, productCategory, isLiving, isCommercial, sales/GMV/audience ranges, and sort in field:asc|desc form. The default sort is gmv:desc.
  • Use the camelCase request fields documented in references/api.md; do not send the upstream snake_case aliases.

How to call

  • API endpoints：POST /chuhaijiang/lives/search、POST /chuhaijiang/lives/detail or POST /chuhaijiang/lives/related-products(for full parameters/responses/error codes see references/api.md）
  • Python script：python scripts/chuhaijiang_live_<entry>.py '<JSON 参数>' [--inline], where <entry> is search、detail or related_products
  • Cost constraints: The business entry script by default caches only successful responses for 24 hours; business-successful empty results can also be cached; the cache is isolated by the current working directory, calling identity, gateway, endpoint, and complete request parameters. When the same combination hits, it outputs Cache hit, and no new paid request is made. HTTP or business failures are not cached;--inline does not bypass the cache;--no-cache forces a real request and may consume compute again, so use it only when the user explicitly agrees to additional consumption or when debugging.

Output strategy (default script behavior)：

  • Alwayswrite the complete response to <cwd>/linkfox/<YYYY-MM-DD>/<session>/data/linkfox-chuhaijiang-tiktok-live-<timestamp>.json（<cwd> is the working directory when the script is executed, which in Claude Code is the current project directory;<session> is taken from the environment variable SESSION_ID, automatically aggregated according to the user task;writing to /tmp is prohibited, and an error is reported if the current directory is not writable)
  • Response body ≤ 8 KB: after writing to disk, print the complete JSON to stdout
  • Response body > 8 KB: after writing to disk, stdout outputs only a summary (top-level fields, business total count, length of the largest list field + first 3 samples)
  • Add --inline to force full printing to stdout (also written to disk)

Data reading suggestions: First look at the summary to judge whether it is sufficient; when specific fields are needed, prefer using jq or ConvertFrom-Json to extract on demand from the saved JSON file, avoiding bringing the entire JSON into context.

Resolve authentication and compute issues

When the gateway returns an authentication or balance error, read references/onboarding.md, and use scripts/onboarding.pyaccording to the auth/billing routing in it. Do not write the API Key, verification code, payment link, or raw user message into feedback.

Usage Examples

python scripts/chuhaijiang_live_search.py '{"country":"us","isCommercial":true,"sort":"gmv:desc","page":1,"pageSize":3}'
python scripts/chuhaijiang_live_detail.py '{"country":"us","id":"7643101948819835678","include":"core"}'
python scripts/chuhaijiang_live_related_products.py '{"country":"us","id":"7643101948819835678","page":1,"pageSize":3}'

These examples were production-validated with non-empty semantic results on 2026-08-29. Public-market IDs are volatile; use a fresh search result if an example stops resolving.

Display Rules

  1. State the requested marketplace, filters, sort, page, page size, and returned total.
  2. For search, show title, room ID/link, host, time range, audience, products, units sold, GMV, GPM, and OPM when returned.
  3. For detail, separate identity/host fields from optional core metrics; label follower_conversion_rate as a decimal unless explicitly formatting it as a percentage.
  4. For related products, show product ID/title/image, country, price range, seller, units sold, GMV, commission rate, and conversion rate when present.
  5. Preserve 19-digit IDs as strings. Preserve raw epoch-millisecond timestamps and add readable dates only as derived labels.
  6. Report empty arrays honestly and never invent a product relationship or a currently-live status.

Important Limitations

  1. Data reflects the provider's indexed public snapshot and can lag TikTok.
  2. isLiving is a search filter, not proof that a returned room is still live when displayed later.
  3. Related products are available only when the indexed live session has product relationships.
  4. Search filters do not imply causality between audience, GMV, sales, and creator performance.
  5. Do not expose internal tool identifiers, credentials, cache files, or unrelated response fields.

User Expression & Scenario Quick Reference

Use this skill: "Use Chuhaijiang to search for US TikTok commerce livestreams", "Use Chuhaijiang to view this livestream's details", "Which products were sold in this livestream", "Chuhaijiang TikTok live analytics".

Adjacent: General TikTok livestream rankings or detail requests without a named source should use linkfox-kalodata-tiktok-livestream. Product-first research, including finding livestreams associated with a product, uses linkfox-chuhaijiang-tiktok-product. Creator-first live research uses linkfox-chuhaijiang-tiktok-creator.

Not applicable: starting or scheduling livestreams, moderation, seller-backend operations, order handling, replay downloading, transcription, or media generation/editing.

Compute consumption rules

Billed separately by endpoint: livestream details 9 compute units/time; livestream search and livestream-associated products 18 compute units/time.

Users pay fees due to compute consumption. Before high-frequency calls or multi-endpoint drilling, first explain the estimated number of calls and compute consumption.

Feedback: Use the Feedback API in references/api.md only when the user explicitly asks to submit feedback or authorizes it after an issue is identified. Sanitize the content and never include credentials, signed URLs, phone numbers, or unrelated task context.

For more high-quality, professional cross-border e-commerce skills, visit LinkFox Skills.