About this skill

Problem

Douyin data queries are not hard because endpoints are missing; they are hard because business questions need to be mapped to the right endpoint, parameter shape, and fallback path. Questions such as “is this creator worth collaborating with?”, “what topic is trending now?”, or “what is a competitor posting?” often lead to trial-and-error doc searching, guessed paths, mixed API versions, and non-reproducible results.

How It Works

Intent recognition: maps natural-language questions to seven domains: hot list, search, video, user, Xingtu/KOL, index, and live.
Endpoint matching: prefers complete documented paths such as fetch_hot_search_result, fetch_one_video_v2, and handler_user_profile_v4.
Parameter construction: fills required fields according to the endpoint contract, using fixed POST body structures and exact values for cursor, sort_type, and date formats.
Call and fallback: does not blindly retry 400/401/403; waits 5 seconds for 429 and retries once; switches to mapped fallback endpoints for 404/500/410, up to three times.
Validation: checks endpoint correctness, parameter completeness, data validity, fallback execution, and output formatting before delivery.

Boundaries

Useful for creator screening, content topic selection, competitor monitoring, public opinion analysis, and brand trend queries. The output is third-party API data and should be treated as reference information. Privacy and credential handling require care because requests are sent to a third-party service. Some open_* and encrypt_* endpoints generate app deep links or request-construction helpers; they do not mean that private messages or publishing actions are directly executed.

Screenshots

Use Cases

When a competitor profile link arrives, pull video, user, and post endpoints to build a content inventory.
During topic planning, query hot lists and keyword trend endpoints to filter trending topics over the last seven days.
When evaluating creator partnerships, collect profile, posts, and Xingtu pricing into a KOL assessment table.
When API calls fail, switch to fallback endpoints using 404/500/410 rules and log retry outcomes.

Best For

Content operators who need to identify brand-relevant topics rising on Douyin over the last seven days.
Business development leads who need to compile profile, posts, Xingtu pricing, and audience fields into comparison tables.
Competitive analysts who need to pull rival accounts’ posts and user data into weekly reporting blocks.
API integration engineers who need to call Douyin endpoints with exact paths, parameters, and fallback rules.