Douyin hashtag API
Douyin hashtag data in one REST call — normalized to the stable JSON schema shared across every FetchPI platform.
- 1 documented endpoints
- GET /v1/douyin/hashtags/{tag}
Contract summary (English): Get the Douyin hashtag detail (capability douyin.hashtag)
- Normalized response entity
- douyin/hashtag
- capability
- douyin.hashtag
Every response also carries freshness (cache / default / live) and billing metadata.
Use cases
- Resolve {{platform}} hashtags and topics into structured metadata for trend dashboards.
- Track tag usage and related content volume around campaigns and events.
- Group content by topic across accounts with consistent, normalized tags.
Response fields
Douyin hashtag (normalized non-entity payload)
Non-entity payload (type hashtag) — the entity layer clean-skips it; served by the /v1/douyin surface.
| Field | Type | Required | Description |
|---|---|---|---|
| id | string | null | Required | — |
| name | string | null | Required | — |
| description | string | null | Optional | — |
| cover_image_url | string | Optional | — |
| metrics.views | integer | Required | — |
| metrics.posts | integer | Required | — |
| platform | "douyin" | Required | — |
| type | "hashtag" | Required | — |
| fetched_at | string | Required | Normalization time (UTC). |
Field notes are shown in the contract's original English.
Response meta
| Field | Type | Required | Description |
|---|---|---|---|
| mode | cache | default | live | Required | Effective mode after merging param > max_age > source policy (D-004). |
| age_seconds | integer | null | Optional | Age of served data; null when unknown. |
| source_layer | cache | db | upstream | Required | Which layer served the response (PRD §10). |
| stale | boolean | Optional | True when stale data was served under stale_if_error / SWR (D-004). |
| billing.amount_credits | integer | Required | Micro-USD (1e-6 USD) actually charged for this request. |
| billing.cache_hit | boolean | Required | — |
Field notes are shown in the contract's original English.
Example request & response
/v1/douyin/hashtags/{tag}curl -H "Authorization: Bearer $MESHDATA_API_KEY" \
"https://api.fetchpi.com/v1/douyin/hashtags/trending"{
"data": {
"id": "1655000000000001001",
"platform": "douyin",
"type": "hashtag",
"name": "数据API",
"description": "话题详情（按上游 ch_id 寻址）。",
"cover_image_url": "https://cdn.example.com/cover/douyin-hashtag.jpeg",
"metrics": {
"views": 960000000,
"posts": 128000
},
"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 PlaygroundParameter tables, error codes and response semantics for this endpoint live in the API documentation.
Open the endpoint referenceFrequently asked questions
Are hashtags and topics normalized?
Yes — the response schema defines stable field names for tag identity, counts and metadata, so dashboards need no per-platform parsing.
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 hashtag 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.