Skip to main content
GET
weibo fetch_user_following
Get user following Pricing — billed per successful call; the final charge scales by your plan multiplier. Charged only when the upstream response body code is 200.

Example

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Query Parameters

since_id
string | null

Pagination cursor in the format "timestamp|offset"; omit for the first request, then pass the since_id value from the previous response

Usage: Pagination cursor in "timestamp|offset" format. Don't pass for the first request, use the returned since_id for subsequent requests - since_id json path: $.data.since_id

sort_type
integer
default:2

Sort type: 1=by latest Weibo time, 2=by follow time (default)

Usage: Sort type - 1: Sort by latest post time in descending order (recently posted first) - 2: Sort by following time in descending order (recently followed first, default)

uid
string
required

User ID

Response

Successful Response

Return

  • Following list data
    • data.users: Array of followed users, each item holds the profile in its user field (data.users[].user)
    • data.since_id: Next pagination cursor, absent when there is no more data
    • data.total_cnt: Total following count
code
integer
default:200

HTTP status code

request_id
string | null

Unique request identifier

message
string
default:Request successful. This request will incur a charge.

Response message (EN-US)

message_zh
string
default:请求成功,本次请求将被计费。

Response message (ZH-CN)

support
string
default:Discord: https://discord.gg/aMEAS8Xsvz

Support message

time
string

The time the response was generated

time_stamp
integer

The timestamp the response was generated

time_zone
string
default:America/Los_Angeles

The timezone of the response time

docs
string | null

Link to the API Swagger documentation for this endpoint

cache_message
string | null
default: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.

Cache message (EN-US)

cache_message_zh
string | null
default:本次响应已缓存,可通过下方 URL 直接查看,有效期 24 小时,访问缓存链接无额外费用。缓存仅用于请求溯源,不影响接口数据的时效性,也不会再次通过接口返回。

Cache message (ZH-CN)

cache_url
string | null

The URL to access the cached result

router
string
default:""

The endpoint that generated this response

params
any
default:{}

The parameters used in the request

data
any

Endpoint-specific response payload. The official shared model does not declare a fixed type or field set. Use the operation's documented return fields or response example; an operation-specific schema, when present, describes the documented fields. Undocumented fields must be read from the actual response rather than assumed.