FetchPI
登录

X user_posts API

一次 REST 调用获取 X user_posts 数据——按 FetchPI 全平台共享的稳定 JSON 模式标准化输出。

  • 1 个已发布端点
  • GET /v1/x/users/{username}/posts

契约摘要(英文): List recent posts of a user (capability x.user_posts)

标准化响应实体
x/user_posts
capability
x.user_posts

每个响应还携带新鲜度(cache / default / live)与计费元数据。

使用场景

  • 按顺序监测 {{platform}} 账号发布的内容,每条都带标准化指标。
  • 定时任务重新查询该 feed 即可发现新动态,适合告警与摘要流程。
  • 用口径一致的结构化输出,横向对比各账号的发布节奏与互动表现。

返回字段

X user posts response (normalized envelope)

Response envelope for GET /v1/x/users/{username}/posts. Cursor is opaque and platform-independent; when the upstream provider is switched the old cursors become invalid.

字段类型必填说明
datapost[]必填—
next_cursorstring | null必填Opaque pagination cursor; null when the list is exhausted.
meta.request_idstring必填—
meta.freshness.modecache | default | live必填—
meta.freshness.age_secondsinteger | null可选—
meta.freshness.source_layercache | db | upstream必填—
meta.freshness.staleboolean可选—
meta.billing.cache_hitboolean必填—
meta.billing.amount_creditsinteger必填Credits actually charged for this request (the settlement unit; 1 credit = $0.0001, permanent).

字段备注为契约英文原文。

响应元数据

字段类型必填说明
modecache | default | live必填Effective mode after merging param > max_age > source policy (D-004).
age_secondsinteger | null可选Age of served data; null when unknown.
source_layercache | db | upstream必填Which layer served the response (PRD §10).
staleboolean可选True when stale data was served under stale_if_error / SWR (D-004).
billing.amount_creditsinteger必填Micro-USD (1e-6 USD) actually charged for this request.
billing.cache_hitboolean必填—

字段备注为契约英文原文。

请求与响应示例

GET/v1/x/users/{username}/posts
curl -H "Authorization: Bearer $MESHDATA_API_KEY" \
  "https://api.fetchpi.com/v1/x/users/newdev/posts"
{
  "data": [
    {
      "id": "1842951234567890123",
      "platform": "x",
      "type": "post",
      "author": {
        "id": "2244994945",
        "username": "newdev",
        "display_name": "New Dev",
        "verified": false
      },
      "text": "One API for internet data.",
      "lang": "en",
      "created_at": "2026-09-17T12:34:56Z",
      "metrics": {
        "likes": 128,
        "reposts": 12,
        "replies": 4,
        "quotes": 1,
        "views": 5230
      },
      "in_reply_to": null,
      "attachments": [],
      "fetched_at": "2026-09-18T09:00:00Z"
    },
    {
      "id": "1842909876543210987",
      "platform": "x",
      "type": "post",
      "author": {
        "id": "2244994945",
        "username": "newdev",
        "display_name": "New Dev",
        "verified": false
      },
      "text": "Freshness modes explained.",
      "lang": "en",
      "created_at": "2026-09-16T08:00:00Z",
      "metrics": {
        "likes": 64,
        "reposts": 3,
        "replies": 1,
        "quotes": 0,
        "views": 1200
      },
      "in_reply_to": null,
      "attachments": [
        {
          "type": "photo",
          "url": "https://cdn.example.com/p/1.jpg",
          "width": 1024,
          "height": 512
        }
      ],
      "fetched_at": "2026-09-18T09:00:00Z"
    }
  ],
  "next_cursor": "eyJpZCI6IjE4MjkwMDAwMDAwMDAwMDAwIn0",
  "meta": {
    "request_id": "req_01HTXQ8Z9HTQ",
    "freshness": {
      "mode": "default",
      "age_seconds": 0,
      "source_layer": "upstream",
      "stale": false
    },
    "billing": {
      "amount_credits": 300,
      "cache_hit": false
    }
  }
}

免费试用

注册免费账号、获取 API Key,即可在浏览器版 Playground 中直接调用该端点。

在 Playground 中试用

该端点的参数表、错误码与响应语义见 API 文档。

查看端点参考

常见问题

可以按计划轮询 feed 吗?

可以——这就是普通的 REST 调用,任何调度器都能定期查询。用新鲜度参数控制每次返回的数据新旧与计费方式。

可以免费试用该端点吗?

可以——注册账号、拿到 API Key 后,即可在控制台的 Playground 中调用该端点。

user_posts 能力怎么计费?

Data API 按请求以积分计费,cache/live 新鲜度有不同倍率。当前各能力的价格以价格页为准。

价格

按请求以积分计费,支持 cache/live 新鲜度选项——最新价格以价格页为准。