Weibo User Published Posts API

Call GET /api/weibo/get-user-post/v1 for Weibo User Published Posts through JustOneAPI with uid.

Weibo User Published Posts

Use this focused JustOneAPI skill for user Published Posts in Weibo. It targets GET /api/weibo/get-user-post/v1. Required non-token inputs are uid. OpenAPI describes it as: Get Weibo user Published Posts data, including text, media, and publish times, for account monitoring.

Endpoint Scope

• Platform key: weibo
• Endpoint key: get-user-post
• Platform family: Weibo
• Skill slug: justoneapi-weibo-get-user-post

Operation	Version	Method	Path	OpenAPI summary
getUserPublishedPostsV1	v1	GET	/api/weibo/get-user-post/v1	User Published Posts

Inputs

Parameter	In	Required by	Optional by	Type	Notes
page	query	n/a	all	integer	Page number, starting with 1
sinceId	query	n/a	all	string	Pagination cursor (since_id). Required if page > 1
uid	query	all	n/a	string	Weibo User ID (UID)

Request body: none documented; send parameters through path or query arguments.

Version Choice

Use getUserPublishedPostsV1 for the documented v1 endpoint. There are no alternate versions grouped in this skill.

Run This Endpoint

Supported operation IDs in this skill: getUserPublishedPostsV1.

node {baseDir}/bin/run.mjs --operation "getUserPublishedPostsV1" --token "$JUST_ONE_API_TOKEN" --params-json '{"uid":"<uid>"}'

Ask for any missing required parameter before calling the helper. Keep user-provided IDs, cursors, keywords, and filters unchanged.

Environment

• Required: JUST_ONE_API_TOKEN
• Pass the token with --token "$JUST_ONE_API_TOKEN"; do not paste token values into chat messages, screenshots, or logs.
• Get a token from Just One API Dashboard.
• Authentication details: Just One API Usage Guide.

Output Focus

• State the operation ID and endpoint path used, for example getUserPublishedPostsV1 on /api/weibo/get-user-post/v1.
• Echo the required lookup scope (uid) before summarizing results.
• Prioritize fields that support this endpoint purpose: Get Weibo user Published Posts data, including text, media, and publish times, for account monitoring.
• Return raw JSON only after the short, endpoint-specific summary.
• If the backend errors, include the backend payload and the exact operation ID.