Parse a Weibo link
Whether a Weibo address is a post, an account, a search or a topic, with its ids, canonical address and the route that reads it. Fetches nothing and costs no credit.
/resolve-url Utilities https://api.fetchlayer.dev/weibo/resolve-url Headers
Authorization string required Bearer token — your FetchLayer API key.
Parameters
url string required Any Weibo address: weibo.com, m.weibo.cn or s.weibo.com.
format string optional json or markdown, lowercase; any other value is a 400. Over MCP, markdown returns the result rendered as text; the REST API accepts it and returns JSON. (default: json)
timeoutMs integer optional Time limit for the whole request, in milliseconds (1000–120000); a value outside that range is a 400. When it runs out, a paged request returns what it has with nextCursor, billed for the pages it read; a request with nothing to return yet fails with a 503 you can retry, marked with the response header X-Timeout-Source: caller.
Response Fields
resolve-url
Parse a Weibo link
kind string post, user, search, topic or unknown.
postId string | null The post’s numeric id, for a post.
shortId string | null The id in the post link, for a post.
userId string | null The account’s numeric id, when the link names one.
handle string | null The custom address, for weibo.com/<name>.
screenName string | null The display name, for a weibo.com/n/<name> link.
query string | null The search term or topic, for a search or topic link.
canonicalUrl string | null The canonical address.
route string | null The route that reads it, such as user-profile.
notes string[] What to do with a link that is not one of the above.
Request
curl -X POST "https://api.fetchlayer.dev/weibo/resolve-url" \
-H "Authorization: Bearer ss-your-key" \
-H "Content-Type: application/json" \
-d '{"url":"https://weibo.com/1642634100"}'Response
{
"skippedRecords": [],
"kind": "user",
"postId": null,
"shortId": null,
"userId": "1642634100",
"handle": null,
"screenName": null,
"query": null,
"canonicalUrl": "https://weibo.com/u/1642634100",
"route": "user-profile",
"notes": []
}