> **For coding agents and LLMs:** This is one page from the Social Fetch docs (markdown export). For curated orientation and workflow guidance, start with [`/llms.txt`](https://www.socialfetch.dev/llms.txt); for agent onboarding and crawl rules, use [`/agents.txt`](https://www.socialfetch.dev/agents.txt); for the full endpoint list with links to pages like this one, use [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt); for one platform's parameters and curls, use [`/llms-{platform}.txt`](https://www.socialfetch.dev/llms-tiktok.txt); use [`/llms.json`](https://www.socialfetch.dev/llms.json) when you need structured JSON for tool registration.

## This page

- **On-site (HTML):** <https://www.socialfetch.dev/docs/api/v1/weibo/search/posts/get>
- **Markdown (.mdx) URL:** <https://www.socialfetch.dev/docs/api/v1/weibo/search/posts/get.mdx>

## API base URL and authentication

- **API origin (from OpenAPI `servers`):** `https://api.socialfetch.dev`
- **Authentication:** send `x-api-key: sfk_...` on `/v1/**` and `/v2/**` routes unless the operation is explicitly anonymous (check OpenAPI `security`, the [API reference hub](https://www.socialfetch.dev/docs/api.mdx), [`/llms.txt`](https://www.socialfetch.dev/llms.txt), or [`/llms.json`](https://www.socialfetch.dev/llms.json) for each route).
- **OpenAPI JSON:** <https://www.socialfetch.dev/openapi.json>

## Recommended docs entrypoints (this site)

- [Documentation overview](https://www.socialfetch.dev/docs.mdx) — top-level orientation (markdown).
- [Quickstart](https://www.socialfetch.dev/docs/quickstart.mdx) — authenticate with `x-api-key`, validate auth with `whoami`, and understand the JSON envelope.
- [SDK](https://www.socialfetch.dev/docs/sdk.mdx) — official TypeScript SDK guide, including `SocialFetchClient`, `Result`, and `unwrap()`.
- [Capability matrix](https://www.socialfetch.dev/docs/capability-matrix.mdx) — every operation with identifiers, pagination, outcomes, media download, credits, and its SDK method. Generated from OpenAPI, so use it for route selection instead of scanning individual pages.
- [Recipes](https://www.socialfetch.dev/docs/recipes.mdx) — copyable workflows (brand monitoring, transcripts, Ad Library, creator scoring, Reddit research) with credit callouts and SDK examples.
- [Integrations](https://www.socialfetch.dev/docs/integrations.mdx) — MCP for AI clients, n8n verified node, Apify Store Actors, Make custom app, SDK, and REST API connection paths.
- [MCP product page](https://www.socialfetch.dev/mcp) — hosted MCP overview, OAuth, Skills install.
- [MCP integration](https://www.socialfetch.dev/docs/integrations/mcp.mdx) — hosted `/mcp` server, OAuth, Cursor/VS Code/Claude install snippets, 1112 endpoint tools, plus docs_search/docs_read for implementation help.
- [n8n integration](https://www.socialfetch.dev/docs/integrations/n8n.mdx) — install `n8n-nodes-socialfetch`, credentials, and workflow examples.
- [Apify integration](https://www.socialfetch.dev/docs/integrations/apify.mdx) — Store Actors under @social-fetch, PPE billing, dataset export, and quick start.
- [Make integration](https://www.socialfetch.dev/docs/integrations/make.mdx) — custom app modules for Make scenarios, API key credentials, and module catalog.
- [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt) — every documented operation with a direct link to that route's agent-readable markdown page (prefer this over parsing OpenAPI).
- [`/llms-{platform}.txt`](https://www.socialfetch.dev/llms-tiktok.txt) — per-platform endpoint files generated from OpenAPI (parameters, credits, curls).
- [`/agents.txt`](https://www.socialfetch.dev/agents.txt) — agent crawl/onboarding file with capabilities, auth rules, and allowlist.
- [`/llms.json`](https://www.socialfetch.dev/llms.json) — structured machine-readable operation inventory with parameter names, pagination, outcomes, credits, and SDK mapping.
- [API reference hub](https://www.socialfetch.dev/docs/api.mdx) — human-friendly index of operations with links into generated pages.
- [Errors](https://www.socialfetch.dev/docs/errors.mdx) — shared error envelope and HTTP status guidance.
- [Credits](https://www.socialfetch.dev/docs/credits.mdx) — metering, `402`, and planning batch jobs.
- Outcome semantics such as `found`, `not_found`, and `private` are documented in [Errors](https://www.socialfetch.dev/docs/errors.mdx) and on operation pages when present in the OpenAPI contract.

## Markdown docs convention

- Every docs page has a markdown twin: append **`.mdx`** to the docs pathname (for example `/docs/quickstart` → `/docs/quickstart.mdx`).
- Agents that send `Accept: text/markdown` on `/docs/**` HTML URLs may receive markdown directly (same URL, `Vary: Accept`).
- Published blog posts use the same convention: `/blog/{slug}` → `/blog/{slug}.mdx`, or `Accept: text/markdown` on the HTML URL (`Vary: Accept`).

---
# Search Weibo posts (https://www.socialfetch.dev/docs/api/v1/weibo/search/posts/get)

## Summary

Search Weibo posts by keyword, popular or newest first, from the first page of results.

**Tags:** `Weibo`

## HTTP

- **Method:** GET
- **Path:** `/v1/weibo/search/posts`
- **Base URL:** `https://api.socialfetch.dev`

## Capability summary

- **SDK mapping:** `client.weibo.searchPosts({ query: "苹果", sort: "top" })`
- **Accepted identifiers:** `query` (query)
- **Pagination:** none
- **Business outcome field:** `data.lookupStatus` with values `found`, `empty`

## Credits

- 1 credit
- Failed requests are free
- Found, empty and not-found answers are all charged

## Authentication

- **`x-api-key`**: API key (`sfk_...`)

## Parameters

### `query` (query)

- **Required:** yes
- **Constraints:** type `string`; minLength: 1; maxLength: 100
- **Description:** What to search for, in any language. Chinese text works as typed, for example `苹果`.

### `sort` (query)

- **Required:** no
- **Constraints:** type `string`; enum: top, recent; default: `top`
- **Description:** `top` (the default) is Weibo's own mix, popular posts first; `recent` is the real-time feed, newest first.

## Responses (status codes)

- **200**: Weibo posts that match a query.
- **400**: Invalid request
- **401**: Missing or invalid API key
- **402**: Insufficient credits
- **500**: Unexpected or billing error
- **502**: Lookup could not be completed.
- **503**: Service temporarily unavailable; safe to retry with backoff.

## Response body (200)

Weibo posts that match a query.

### Field outline

- **data** (required) — type `object`. Endpoint-specific response payload.
  - **lookupStatus** (required) — type `string`; enum: found, empty. `empty` when the search has no results.
  - **query** (required) — type `string`. The query as searched.
  - **sort** (required) — type `string`; enum: top, recent. `top` (the default) is Weibo's own mix, popular posts first; `recent` is the real-time feed, newest first.
  - **posts** (required) — type `array`. Matching posts from the first page of results, as Weibo shows them logged out: about 10 to 20. Long posts are shortened (`isTextTruncated`). `page.truncated` says whether there are more.
    - _items:_
      - **id** (required) — type `string`. Post id (16 digits). Pass it as `postId` to the post and comments endpoints.
      - **shortCode** (required) — type `string`; nullable. The short code in the post's weibo.com link.
      - **url** (required) — type `string`. Post page.
      - **text** (required) — type `string`; nullable. The post's text as plain text, with topics written `#name#`, mentions `@name` and emoji as `[name]`.
      - **isTextTruncated** (required) — type `boolean`. True when this is a shortened copy of a long post: the post endpoint returns the whole text.
      - **title** (required) — type `string`; nullable. The headline Weibo shows above some posts, when it has one.
      - **createdAt** (required) — type `string`; nullable. When the post was published, ISO 8601 UTC.
      - **editedAt** (required) — type `string`; nullable. When the post was last edited, ISO 8601 UTC; null if never.
      - **region** (required) — type `string`; nullable. The region Weibo shows the post was published from, such as `湖南`.
      - **source** (required) — type `string`; nullable. The app or device the post was sent from, when shown.
      - **topics** (required) — type `array`. Topics (hashtags) in the text, without the `#` marks.
        - _items:_
          - type `string`
      - **mentions** (required) — type `array`. Screen names the text mentions, without the `@`.
        - _items:_
          - type `string`
      - **images** (required) — type `array`. The pictures, in order.
        - _items:_
      - **video** (required) — type `object`; nullable. The video, for a video post; otherwise null.
      - **stats** (required) — type `object`. Engagement counters. Weibo rounds large counts (`100万+`); those read as the number shown.
      - **author** (required) — type `object`; nullable. Who posted it; null when Weibo hides the account.
      - **repostOf** (required) — type `object`; nullable. For a repost, the post it shares; null for an original post or when the shared post was deleted.
  - **page** (required) — type `object`. Pagination state. Weibo shows logged-out visitors the first page of a list, so there is never a next page.
    - **hasMore** (required) — type `boolean`. Whether another page is available.
    - **nextCursor** (required) — type `string`; nullable. Cursor to pass in the next request when more pages exist; null on the last page.
    - **truncated** (required) — type `boolean`. True when the list has more rows than Weibo shows logged out: it stops here before its end.
    - **total** (required) — type `integer`; nullable. How many rows the list has in all, as Weibo counts them.
- **meta** (required) — type `object`. Metadata describing the request and billing outcome.
  - **requestId** (required) — type `string`; minLength: 1. Unique request identifier for tracing this API call.
  - **creditsCharged** (required) — type `integer`; minimum: 0. Credits charged for this request.
  - **version** (required) — type `string`; enum: v1. Public API version that served the response.
  - **stale** (optional) — type `boolean`; enum: true. Present, and `true`, only when the source couldn't be reached and this is the last good answer for the same request instead, up to 24 hours old. Absent on every live answer.
  - **fetchedAt** (optional) — type `string`. When a stale answer (`stale: true`) was originally fetched (ISO 8601, UTC). Absent on every live answer.

### Example JSON (OpenAPI example)

```json
{
  "data": {
    "lookupStatus": "found",
    "query": "苹果",
    "sort": "top",
    "posts": [
      {
        "id": "5341489761618229",
        "shortCode": "RhpkY6MYt",
        "url": "https://weibo.com/6529876887/RhpkY6MYt",
        "text": "折叠屏iPhone Duo、18 Pro系列现场上手！\n#苹果发布会##苹果发布会有何亮点##何同学##iPhoneDuo# 老师好我叫何同学的微博视频",
        "isTextTruncated": false,
        "title": null,
        "createdAt": "2026-09-09T22:44:22.000Z",
        "editedAt": null,
        "region": "浙江",
        "source": "微博视频号",
        "topics": [
          "苹果发布会"
        ],
        "mentions": [],
        "images": [],
        "video": {
          "url": "https://f.video.weibocdn.com/o0/KuAzwbLrlx08AGcwlUre01041200IZwf0E010.mp4?label=mp4_720p&template=720x1280.24.0&ori=0&ps=1BVp4ysnknHVZu&Expires=1794917565&ssig=qeE38KmFbn&KID=unistore,video",
          "coverUrl": "https://wx1.sinaimg.cn/orj480/0077UHgXly1igy6qy2qocj31401hchdt.jpg",
          "title": "折叠屏iPhone Duo、18 Pro系列现场上手！\n#苹果发布会##苹果发布会有何亮点##何同学##iPhoneDuo#",
          "durationSeconds": 115.542,
          "playCount": 10220000,
          "playCountLabel": "1022万次播放"
        },
        "stats": {
          "reposts": 1138,
          "comments": 1306,
          "likes": 20289
        },
        "author": {
          "id": "6529876887",
          "displayName": "老师好我叫何同学",
          "avatarUrl": "https://wx2.sinaimg.cn/orj480/0077UHgXly8gdirkwcpwmj306y06zdfp.jpg",
          "url": "https://weibo.com/u/6529876887",
          "isVerified": true
        },
        "repostOf": null
      }
    ],
    "page": {
      "hasMore": false,
      "nextCursor": null,
      "truncated": true,
      "total": 1000
    }
  },
  "meta": {
    "requestId": "req_01example_weibo_search_posts",
    "creditsCharged": 1,
    "version": "v1"
  }
}
```

### Machine-readable error codes

When an error JSON body is returned, it may include one of these `error.code` values (derived from the OpenAPI schemas for this operation; additional codes may exist at runtime):

- `bad_request`

## Error handling & retries

Interpret HTTP status codes using the descriptions below. Do not assume a JSON body unless the OpenAPI schema defines one for that status.

- **400**: Invalid request **Retry:** Fix the request; retrying the same invalid payload will not help.
- **401**: Missing or invalid API key **Retry:** Fix the API key first; retrying without changes will not help.
- **402**: Insufficient credits **Retry:** Do not retry without resolving billing/credits (retrying the same request will not help).
- **500**: Unexpected or billing error
- **502**: Lookup could not be completed. **Retry:** May be transient; a few retries with backoff are reasonable.
- **503**: Service temporarily unavailable; safe to retry with backoff. **Retry:** Usually safe to retry with exponential backoff and jitter.

### Suggested client defaults

- Send the API key using the `x-api-key` header on every request.
- On `503` (and sometimes `502`), retry with backoff; cap retries and surface a clear error to the user.
- On `402`, surface an actionable billing message rather than blind retries.

## Examples

### TypeScript SDK

```typescript
import { SocialFetchClient } from "@socialfetch/sdk";

const client = new SocialFetchClient({
  apiKey: process.env.SOCIALFETCH_API_KEY!,
});

const result = await client.weibo.searchPosts({
  query: "苹果",
});

if (!result.ok) {
  console.error(result.error);
} else {
  console.log(result.value.data);
}
```

### Node.js

```javascript
const response = await fetch(
  "https://api.socialfetch.dev/v1/weibo/search/posts?query=苹果",
  {
    headers: {
      "x-api-key": "YOUR_API_KEY"
    }
  }
);

const data = await response.json();
console.log(data);
```

### cURL

```bash
curl "https://api.socialfetch.dev/v1/weibo/search/posts?query=苹果" \
  -H "x-api-key: YOUR_API_KEY"
```

### Python

```python
import requests

response = requests.get(
    "https://api.socialfetch.dev/v1/weibo/search/posts?query=苹果",
    headers={"x-api-key": "YOUR_API_KEY"},
)
data = response.json()
print(data)
```