Open Weibo Weibo API

Name: Weibo API
Brand: Weibo API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentSocial MediaSocial Publishingoauth2, apiKey19 EndpointsREST

For Agents

Read Weibo timelines, post and repost statuses, manage comments and friendships, and search statuses or users on the Weibo open platform. Useful for agents that publish or monitor Weibo content.

Use for: Post a new weibo status from this account, Repost a Weibo status with my own commentary, Pull the latest weibos from the public timeline, Search Weibo for posts mentioning a brand

Not supported: Does not handle Weibo Pay, livestreaming, or video upload - use for status, comment, user, friendship, and search operations on the v2 open platform only.

Jentic publishes the only available OpenAPI specification for Weibo API, keeping it validated and agent-ready. Weibo is one of China's largest microblogging platforms, and its v2 open-platform API exposes the core social graph and content surface - public and friend timelines, status posting and deletion, comments, reposts, user lookup, friendship management, and search across statuses and users. The API supports OAuth 2.0 authorisation-code flow plus a simple access_token query parameter, and the endpoint shape is consistent with how Weibo apps and bots have been built since v2 launched.

Jentic One on Github

Install Jentic One Beta

Connect the Weibo API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Weibo API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fopen.weibo.com%2Fweibo" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fopen.weibo.com%2Fweibo" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Weibo API.

Pull the public, friends, or home timeline for the authenticated user

Post a new status to Weibo, with or without an attached image

Repost an existing status and add a comment to it

Comment on a status, reply to a comment, or delete a comment

Look up a user profile by user id and list their friends

GET STARTED

Start building with Weibo API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Weibo API for, with concrete tasks.

★ Brand Mention Monitoring

Search Weibo for posts mentioning a brand and route any high-engagement matches into a community-management queue. GET /search/statuses.json takes a keyword query and returns matching statuses with author and engagement metrics, suitable for a daily brand-monitoring agent.

Call GET /search/statuses.json for the brand keyword every hour and post any results with more than 100 reposts to the community-management Slack channel.

Scheduled Status Publishing

Publish a queue of approved status updates to Weibo on a schedule, optionally attaching an image. POST /statuses/update.json posts the text and POST /statuses/upload.json posts text plus an image, so a content-scheduling agent can emit posts without using the Weibo web interface.

At each scheduled time, call POST /statuses/update.json with the queued post text, or POST /statuses/upload.json if the post has an attached image.

Comment-Section Moderation

Moderate the comment section under a brand's Weibo posts by listing comments, replying, and deleting offending entries. GET /comments/show.json returns the comments for a status, POST /comments/reply.json replies in-thread, and POST /comments/destroy.json removes a comment, covering the moderation loop end to end.

For each new status, call GET /comments/show.json, run the comments through a moderation classifier, and call POST /comments/destroy.json on any flagged as abusive.

Follower-Graph Analysis

Analyse the follower graph of a Weibo account to identify influential followers or build look-alike audiences. GET /users/show.json returns the profile, GET /friendships/friends.json returns the friend list, and GET /suggestions/users/hot.json supplies the system-recommended hot users for cross-reference.

Call GET /users/show.json for the target account, then GET /friendships/friends.json to pull the friend list and rank by follower count returned in each profile.

AI Agent Weibo Publishing

Let a Jentic-orchestrated agent post and monitor Weibo content without holding the OAuth refresh token. The agent searches Jentic for a publishing intent, the OAuth-issued access_token is injected at execution time, and the post is delivered through POST /statuses/update.json.

Search Jentic for 'post to Weibo', load the POST /statuses/update.json schema, and execute it with the agent-generated status text, returning the new status id.

Key Endpoints

19 endpoints — jentic publishes the only available openapi specification for weibo api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/statuses/update.json

Post a new status

POST

/statuses/upload.json

Post a new status with an image

POST

/statuses/repost.json

Repost an existing status

GET

/statuses/home_timeline.json

Get the home timeline

GET

/comments/show.json

Get the comments on a status

POST

/comments/create.json

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Weibo API by hand means running its OAuth2 authorization-code flow, then passing the access_token query parameter on every v2 call and handling status and comment payloads yourself. Through Jentic you install once, import the Weibo API from the API Directory, store the token once, and your agent calls it.

Permission scoping

Weibo takes its status and comment targets in the request body and query rather than a resource id in the URL path, so limit the agent to the operations it needs, such as reading the home timeline or fetching comments on a status. You credit the agent only with the operations you allow, so posting or reposting stay out unless you add them.

Credential isolation

Your Weibo access token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'read the home timeline' or 'post a status update', and Jentic returns the matching Weibo operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Weibo API through Jentic.

Why is there no official OpenAPI spec for Weibo API?

Weibo's v2 open platform documentation is published as HTML wiki pages and does not ship a machine-readable OpenAPI document. Jentic generates and maintains this spec so AI agents and developers can call Weibo API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Weibo API use?

Weibo uses OAuth 2.0 authorisation-code flow with POST /oauth2/access_token, plus an access_token query parameter on subsequent calls. Through Jentic the OAuth handshake is handled in the platform and the access_token is injected at execution time so the agent never sees the raw token.

Can I post images to Weibo through this API?

Yes. POST /statuses/upload.json accepts a multipart request with the status text and a picture attachment, returning the newly created status. Use POST /statuses/update.json for text-only posts.

What are the rate limits for the Weibo API?

Weibo applies per-application rate limits documented on its open-platform wiki rather than in this spec; expect different ceilings per endpoint family (write endpoints are more strictly limited than reads). Plan for 429 responses and back off, and read the live limits on open.weibo.com for the current app tier.

How do I post a status to Weibo through Jentic?

Run pip install jentic and search for 'post to Weibo'. Jentic returns the POST /statuses/update.json operation; load the schema and execute it with the status text, and Jentic injects the access_token query parameter at execution time.

Does this API let me delete comments on my own posts?

Yes. POST /comments/destroy.json removes a comment by id, which is the canonical endpoint for moderating the comment section of a status owned by the authenticating account.

Can I limit what my agent is allowed to do with the Weibo API?

Yes. Because you run Jentic One yourself, your own rules decide which Weibo operations and credentials the agent may use, so you can grant only what a task needs, such as reading GET /statuses/home_timeline.json or fetching GET /comments/show.json. Weibo takes its status and comment targets in the request body and query rather than in the URL path, so you scope at the operation level: write actions like POST /statuses/update.json, POST /statuses/repost.json, and POST /comments/create.json stay unavailable unless you explicitly allow them. The access token is injected at execution time under those same rules, so the agent only ever exercises the operations you have permitted.

Open Weibo Weibo API

Connect the Weibo API to your agent

Capabilities

Start building with Weibo API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs