douyin/
live-room-detail

The Douyin Live Room Detail API retrieves one public Douyin live room from a known numeric room_id, returning its title, status, host identity, media, visible viewer and like counts, and collection time.

Douyin Live Room Detail API

Known room lookup
Host context
Audience snapshot
0.1 credits / request
Ready
Ready

Enter parameters and send a request. The task status and normalized results will appear here.

README

By SocQ · Updated

Douyin Live Room Detail

Douyin live rooms are public broadcast sessions with a title, current status, host identity, media, and visible viewer and like counts. These fields support room catalog enrichment, session-state tracking, and point-in-time comparison.

Douyin Live Room Detail API Features

  • Known-room detail lookupResolve one known numeric room_id into at most one normalized live_room record through a single source request without source pagination.
  • Room and host contextThe Douyin Live Room Detail API keeps the available room title, status, host identity, source URL, and collection time together in one consistent shape.
  • Visible session snapshotCapture available viewer and like counts alongside public media for a time-stamped view of the room.

Douyin Live Room Detail API Parameters

ParametersRequiredDescription
room_idRequiredRequired Douyin live-room identifier containing digits only. Send it as a string so long identifiers are not rounded by a client.

How to Use the Douyin Live Room Detail API

Start with a known numeric room ID, submit the asynchronous Douyin Live Room Detail API task, then read its normalized stored result.

  1. Obtain room_id from a live-room context that exposes the numeric identifier; this endpoint does not discover room IDs.
  2. POST the identifier as a non-empty digit-only string to /v1/douyin/live-room-detail.
  3. Poll /v1/tasks/{task_id} until status becomes succeeded or failed.
  4. Read data.results.items from /v1/tasks/{task_id}?limit=50; a resolved room produces at most one item, while next_cursor belongs only to SocQ stored-result pagination.
# Set DOUYIN_ROOM_ID to a known numeric room_id before sending.
curl -X POST "https://api.socq.ai/v1/douyin/live-room-detail" \
  -H "Authorization: Bearer $SOCQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d "{\"room_id\":\"${DOUYIN_ROOM_ID}\"}"

# Poll GET /v1/tasks/{task_id}, then read data.results.items from /v1/tasks/{task_id}?limit=50.

Douyin Live Room Detail API Use Cases

  • Live-room catalog enrichment: Add available title, status, host, media, visible metrics, and collection time to a catalog that already stores the room ID.
  • Session-state snapshot tracking: Retain separately collected records with collected_at to distinguish point-in-time room status and audience observations.
  • Host-room context review: Review the available host identity beside the room title, status, media, and visible session counts in one normalized record.

Douyin Live Room Detail API Pro Tips

  • Submit room_id as a quoted digit-only string, not a JavaScript number, so a long identifier keeps every digit.
  • Obtain a known room_id before calling the Douyin Live Room Detail API because the request performs detail retrieval rather than live-room discovery.
  • Retain the submitted room_id in your own record; the canonical live-room result does not guarantee that the source echoes it as id.
  • Treat title, status, author, metrics, media, URL, and timestamps as nullable because the source may omit individual public fields.
  • Do not send results_limit or a source cursor; next_cursor, when present, paginates stored SocQ result items rather than the provider request.

Beyond the Douyin Live Room Detail API, use these APIs when you need a different type of public Douyin data.

Explore other platforms

Combine Douyin data with public data from other supported social platforms.

Douyin Live Room Detail API — FAQ

Douyin Live Room Detail API retrieves one known public live room from its numeric room_id. It returns available room, host, media, audience, and collection-time fields as a normalized point-in-time record.

Use a public live-room context that exposes the room's numeric identifier and retain it with your record. This endpoint does not search for live rooms or discover room IDs.

The runtime validator requires a string matching the digit-only room ID format. Keeping the value as text also prevents long IDs from being rounded by numeric clients.

The normalized record can include title, status, author, URL, media, visible viewers_count and likes_count, created_at, and collected_at. Any optional source field can be null or absent.

No. It makes one detail request and yields at most one normalized record; the task-results next_cursor is only the standard cursor for already stored SocQ items.

A successful task has a fixed cost of 0.10 SocQ credits. The charge does not change with a result count or pagination setting.