Search user posts

Search for user posts with the Weibo API. Supply an uid and optionally set a page number. Use it to surface relevant records in a search or discovery tool. The GET request schema also lists q. Use the results to organize a research workflow and cross-check the relevant source records.

Selected price
$0.001 / callPublished pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
用户ID/User ID
Optional parameters (10)
搜索关键词/Search keyword
页数/Page number
开始时间戳/Start timestamp
结束时间戳/End timestamp
是否包含原创微博,1=包含,0=不包含/Include original posts, 1=include, 0=exclude
是否包含转发微博,1=包含,0=不包含/Include retweets, 1=include, 0=exclude
是否包含文字微博,1=包含,0=不包含/Include text posts, 1=include, 0=exclude
是否包含图片微博,1=包含,0=不包含/Include image posts, 1=include, 0=exclude
是否包含视频微博,1=包含,0=不包含/Include video posts, 1=include, 0=exclude
是否包含音乐微博,1=包含,0=不包含/Include music posts, 1=include, 0=exclude

Sample response

{
  "cache_message": "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_zh": "本次响应已缓存,可通过下方 URL 直接查看,有效期 24 小时,访问缓存链接无额外费用。缓存仅用于请求溯源,不影响接口数据的时效性,也不会再次通过接口返回。",
  "cache_url": "<cache_url>",
  "code": 200,
  "data": null,
  "docs": "<docs>",
  "message": "Request successful. This request will incur a charge.",
  "message_zh": "请求成功,本次请求将被计费。",
  "params": {},
  "request_id": "<request_id>",
  "router": "",
  "support": "Discord: https://discord.gg/aMEAS8Xsvz",
  "time": "<time>",
  "time_stamp": 0,
  "time_zone": "America/Los_Angeles"
}

Response result

Response structure

Inferred from examples
  • cache_messagestring
  • cache_message_zhstring
  • cache_urlstring
  • codeinteger
  • datanull
  • docsstring
  • messagestring
  • message_zhstring
  • paramsobject
  • request_idstring
  • routerstring
  • supportstring
  • timestring
  • time_stampinteger
  • time_zonestring

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use Search user posts with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.