TItikhub
Weibo-App-API

获取热搜榜/Get hot search

Changed on

[中文]

用途:

  • 获取微博热搜榜，支持多个分类。

参数:

  • category: 热搜分类
    • mineband: 我的热搜
    • realtimehot: 实时热搜（默认）
    • social: 社会热搜
    • fun: 文娱热搜
    • technologynav: 科技热搜
    • lifenav: 生活热搜
    • region: 同城热搜（需配合 region_name 指定城市）
    • sportnav: 体育热搜
    • gamenav: ACG热搜
  • page: 页码，从1开始（默认1）
  • count: 每页数量，默认20，最大50
  • region_name: 同城热搜城市名称，仅 category=region 时有效，默认北京

返回:

  • 热搜榜数据，包含热搜词条、热度等

注意:

  • 热搜榜实时更新

[English]

Purpose:

  • Get Weibo hot search ranking, supports multiple categories.

Parameters:

  • category: Hot search category
    • mineband: My hot search
    • realtimehot: Realtime hot search (default)
    • social: Social hot search
    • fun: Entertainment hot search
    • technologynav: Technology hot search
    • lifenav: Life hot search
    • region: Local hot search (use region_name to specify city)
    • sportnav: Sports hot search
    • gamenav: ACG hot search
  • page: Page number, starts from 1 (default 1)
  • count: Items per page, default 20, max 50
  • region_name: City name for local hot search, only effective when category=region, default Beijing

Return:

  • Hot search ranking data, including search terms, popularity, etc.

Note:

  • Hot search ranking updates in real-time

[示例/Example]

category = "realtimehot" page = 1 count = 20

get/api/v1/weibo/app/fetch_hot_search

Request

  • Base URL
    https://api.tikhub.io (the document declares no server; this is the origin it was published from)
  • Auth
    HTTP bearer

Query parameters

categorystring

热搜分类: mineband=我的, realtimehot=热搜, social=社会, fun=文娱, technologynav=科技, lifenav=生活, region=同城, sportnav=体育, gamenav=ACG

pageinteger

页码

countinteger

每页数量

region_namestring

同城热搜城市名称，仅 category=region 时有效，支持: 北京/上海/广州/深圳/杭州/成都/重庆/武汉/南京/天津/西安/长沙/郑州/苏州/东莞/青岛/沈阳/合肥等，默认北京

Response

Successful Response

codeinteger

HTTP status code | HTTP状态码

request_idstring nullable

Unique request identifier | 唯一请求标识符

messagestring

Response message (EN-US) | 响应消息 (English)

message_zhstring

Response message (ZH-CN) | 响应消息 (中文)

supportstring

Support message | 支持消息

timestring

The time the response was generated | 生成响应的时间

time_stampinteger

The timestamp the response was generated | 生成响应的时间戳

time_zonestring

The timezone of the response time | 响应时间的时区

docsstring nullable

Link to the API Swagger documentation for this endpoint | 此端点的 API Swagger 文档链接

cache_messagestring nullable

Cache message (EN-US) | 缓存消息 (English)

cache_message_zhstring nullable

Cache message (ZH-CN) | 缓存消息 (中文)

cache_urlstring nullable

The URL to access the cached result | 访问缓存结果的 URL

routerstring

The endpoint that generated this response | 生成此响应的端点

paramsunknown
dataunknown

Changes

  • 96a122a5f220Revision changes
    • info

      added the optional property // to the response with the status

    • info

      added the optional property // to the response with the status

  • 50f9ec6e1cd3Revision changes
    • info

      the response's property default value changed from This request will be cached. You can access the cached result directly using the URL below valid for 24 hours. Accessing the cache will not incur additional charges. to This 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