获取话题搜索 V2/Fetch hashtag search V2
Changed on[中文]
用途:
- 获取抖音 App 中话题(挑战/标签)搜索的结果,使用 V2 版本 API。
- 支持关键词搜索,返回匹配的话题详情,包括话题名称、话题封面、浏览量、参与人数等。
备注:
- 本接口专注于搜索话题(Challenge/Hashtag)内容,不包含视频或直播等其他类型。
- 初次请求时 cursor 传入 0,search_id 传空字符串,后续翻页请使用上一次返回的 cursor 和 search_id。
参数:
- keyword: 搜索关键词,如 "游戏"
- cursor: 翻页游标(首次请求传 0,翻页时使用上次响应的 cursor)
- sort_type: 排序方式
- 0: 综合排序
- 1: 最多点赞
- 2: 最新发布
- publish_time: 发布时间筛选
- 0: 不限
- 1: 最近一天
- 7: 最近一周
- 180: 最近半年
- filter_duration: 视频时长筛选
- 0: 不限
- 0-1: 1 分钟以内
- 1-5: 1-5 分钟
- 5-10000: 5 分钟以上
- content_type: 内容类型筛选
- 0: 不限
- 1: 视频
- 2: 图片
- 3: 文章
- search_id: 搜索ID(分页时使用)
请求体示例:
payload = {
"keyword": "游戏",
"cursor": 0,
"sort_type": "0",
"publish_time": "0",
"filter_duration": "0",
"content_type": "0",
"search_id": ""
}
返回(部分常用字段,实际返回字段更多,一切以实际响应为准):
- business_data(话题搜索结果列表)
- data_id: 结果的唯一编号
- type: 数据类型(固定为 2)
- data.challenge_info:
- cid: 话题ID
- cha_name: 话题名称
- desc: 话题描述
- schema: 话题跳转链接(aweme://开头,可跳转抖音 App 内话题详情)
- hashtag_profile: 话题封面图 URL
- user_count: 参与人数
- view_count: 话题浏览量
- challenge_status: 话题状态(1=正常,其他=异常)
- author: 创建者信息
- uid: 创建者抖音用户ID
- nickname: 昵称
- avatar_thumb.url_list: 缩略头像URL列表
- is_verified: 是否认证
- follower_count: 粉丝数
- share_info:
- share_url: 话题分享链接
- share_title: 分享标题
- share_desc: 分享描述
[English]
Purpose:
- Fetch hashtag/challenge search results from Douyin App using V2 API.
- Supports searching by keyword and returns detailed challenge information, including name, cover image, view count, and participant count.
Notes:
- This API focuses on searching challenges (hashtags), not including videos or live streams.
- Set cursor to 0 and search_id to an empty string for the first request. For pagination, use the cursor and search_id from the last response.
Parameters:
- keyword: Search keyword, e.g., "game"
- cursor: Pagination cursor (0 for first request)
- sort_type: Sorting method
- 0: Comprehensive
- 1: Most likes
- 2: Latest
- publish_time: Publish time filter
- 0: Unlimited
- 1: Last day
- 7: Last week
- 180: Last half year
- filter_duration: Video duration filter
- 0: Unlimited
- 0-1: Under 1 minute
- 1-5: 1-5 minutes
- 5-10000: Over 5 minutes
- content_type: Content type filter
- 0: Unlimited
- 1: Video
- 2: Image
- 3: Article
- search_id: Search ID for pagination
Request Body Example:
payload = {
"keyword": "game",
"cursor": 0,
"sort_type": "0",
"publish_time": "0",
"filter_duration": "0",
"content_type": "0",
"search_id": ""
}
Response (common fields, actual response may contain more fields):
- business_data (list of hashtag search results)
- data_id: Unique identifier for the result
- type: Data type (fixed 2)
- data.challenge_info:
- cid: Challenge ID
- cha_name: Challenge name
- desc: Challenge description
- schema: Challenge detail schema link (aweme:// schema, used to deep link inside Douyin App)
- hashtag_profile: URL of the hashtag cover image
- user_count: Number of participants
- view_count: Number of views
- challenge_status: Status (1 = active, others = abnormal)
- author: Creator info
- uid: User ID
- nickname: Nickname
- avatar_thumb.url_list: Thumbnail avatar URLs
- is_verified: Whether the creator is verified
- follower_count: Number of followers
- share_info:
- share_url: Shareable URL
- share_title: Title for sharing
- share_desc: Description for sharing
Request
- Base URLhttps://api.tikhub.io (the document declares no server; this is the origin it was published from)
- AuthHTTP bearer
Request body
Response
Successful Response
Changes
- info
added the optional property
//to the response with the status - info
added the optional property
//to the response with the status
- info
- info
the
response's property default value changed fromThis request will be cached. You can access the cached result directly using the URL belowvalid for 24 hours. Accessing the cache will not incur additional charges.toThis response is cached and accessible via the URL below for 24 hours at no extra cost. The cache is for request tracing only — it doesn't affect the API's data freshness and won't be returned through the API again.for the status - info
the
response's property default value changed from本次请求将被缓存,你可以使用下面的 URL 直接访问缓存结果,有效期为 24 小时,访问缓存不会产生额外费用。to本次响应已缓存,可通过下方 URL 直接查看,有效期 24 小时,访问缓存链接无额外费用。缓存仅用于请求溯源,不影响接口数据的时效性,也不会再次通过接口返回。for the status
- info