Douyin Video Detail API

Douyin Video Detail

Features

• Supported Douyin URLAccept one URL on douyin.com, iesdouyin.com, or a supported subdomain. When /video/ appears, it must be followed by a numeric ID.
• Bounded single-video resultRun one provider detail request and store at most one normalized video record without source pagination or results_limit.
• Caption and creator contextReturn available video text alongside normalized creator ID, username, display name, profile URL, avatar, and account flags.
• Media and duration fieldsKeep available video or image references, previews, dimensions, media duration, and the normalized duration_seconds field.
• Time-stamped engagement snapshotPair available like, comment, share, play, and view counts with published_at and collected_at instead of presenting them as live counters.

Parameters

How to Use

Submit one supported Douyin video URL, track the asynchronous task, and read its stored normalized result after success.

1. Set DOUYIN_VIDEO_URL to a public URL whose host is douyin.com, iesdouyin.com, or a subdomain. A /video/ segment, when present, must be followed by a numeric ID.
2. POST the url string to /v1/douyin/video-detail and save the returned task_id.
3. Poll /v1/tasks/{task_id} until the task succeeds or fails; result fields are not available while it is incomplete.
4. After success, read data.results.items. The provider produces at most one item, while limit and next_cursor belong to SocQ's stored-results reader.

curl -X POST "https://api.socq.ai/v1/douyin/video-detail" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d "{\"url\":\"$DOUYIN_VIDEO_URL\"}"

# Poll GET /v1/tasks/{task_id}
# Read the normalized video from data.results.items

Best Use Cases

• Enrich known-video catalogs: Add normalized identity, caption, creator, publication time, duration, media, and source fields to approved Douyin video links.
• Connect discovery to detail: Use a supported video URL retained from a Douyin user-video or video-search record as the exact input for a focused detail lookup.
• Prepare point-in-time comparisons: Store repeated successful results with collected_at to compare available public engagement snapshots on a defined schedule.

Pro Tips

• Use a direct public video reference on a supported hostname for meaningful provider resolution; if it contains /video/, keep the numeric video ID intact.
• Leave the Playground field empty until you have a real public video URL; this endpoint has no reliable universal default.
• Submit one URL per task and omit results_limit, cursor, and unrelated IDs because the public request accepts only url.
• Treat missing creator, media, audio, hashtag, mention, or engagement fields as unavailable rather than as empty strings or zero.
• Use collected_at for metric comparisons and published_at for content chronology; they describe different moments.
• If you continue to video comments, pass an available supported video URL to that separate endpoint instead of assuming the detail task expands into comments.

Related APIs