FetchPI
Log in

Douyin live_room API

Douyin live_room data in one REST call — normalized to the stable JSON schema shared across every FetchPI platform.

  • 1 documented endpoints
  • GET /v1/douyin/live/{id}

Contract summary (English): Get the Douyin live room info (capability douyin.live_room)

Normalized response entity
douyin/live_room
capability
douyin.live_room

Every response also carries freshness (cache / default / live) and billing metadata.

Use cases

  • Feed content-analysis pipelines with structured {{platform}} posts: text, metrics, timestamps and media references.
  • Power moderation, research and monitoring workflows that need the original content plus engagement counts.
  • Archive {{platform}} content as stable, normalized JSON instead of brittle page scraping.

Response fields

Douyin live room (normalized non-entity payload)

Non-entity payload (type live_room) — the entity layer clean-skips it; served by the /v1/douyin surface.

FieldTypeRequiredDescription
idstring | nullRequired—
titlestring | nullOptional—
usernamestring | nullOptional—
display_namestring | nullOptional—
statusstring | nullOptional—
viewer_countintegerOptional—
started_atstring | nullOptional—
cover_image_urlstringOptional—
platform"douyin"Required—
type"live_room"Required—
fetched_atstringRequiredNormalization time (UTC).

Field notes are shown in the contract's original English.

Response meta

FieldTypeRequiredDescription
modecache | default | liveRequiredEffective mode after merging param > max_age > source policy (D-004).
age_secondsinteger | nullOptionalAge of served data; null when unknown.
source_layercache | db | upstreamRequiredWhich layer served the response (PRD §10).
stalebooleanOptionalTrue when stale data was served under stale_if_error / SWR (D-004).
billing.amount_creditsintegerRequiredMicro-USD (1e-6 USD) actually charged for this request.
billing.cache_hitbooleanRequired—

Field notes are shown in the contract's original English.

Example request & response

GET/v1/douyin/live/{id}
curl -H "Authorization: Bearer $MESHDATA_API_KEY" \
  "https://api.fetchpi.com/v1/douyin/live/1842951234567890123"
{
  "data": {
    "id": "8800000000000001001",
    "platform": "douyin",
    "type": "live_room",
    "title": "直播:数据 API 问答",
    "username": "meshdata_dev",
    "display_name": "MeshData 抖音站",
    "status": "LIVE",
    "viewer_count": 3456,
    "started_at": "2026-09-21T08:00:00Z",
    "cover_image_url": "https://cdn.example.com/cover/douyin-live.jpeg",
    "fetched_at": "2026-09-21T09:00:00Z"
  },
  "meta": {
    "request_id": "req_01HTXQ8Z9HTQ",
    "freshness": {
      "mode": "default",
      "age_seconds": 0,
      "source_layer": "upstream",
      "stale": false
    },
    "billing": {
      "amount_credits": 100,
      "cache_hit": false
    }
  }
}

Free demo

Create a free account, grab an API key and call this endpoint from the browser-based Playground.

Try it in the Playground

Parameter tables, error codes and response semantics for this endpoint live in the API documentation.

Open the endpoint reference

Frequently asked questions

Which content fields are included?

The normalized content entity — text, author, timestamps, engagement metrics and media references — as documented in the field table below, plus freshness and billing metadata.

Can I try this endpoint for free?

Yes — register an account, grab an API key and call it from the Playground in the console.

How is the live_room capability billed?

Data API calls are billed per request in credits, with different cache/live freshness multipliers. Current per-capability prices live on the pricing page.

Pricing

Per-request credit billing with cache/live freshness options — current prices live on the pricing page.