X profile API
一次 REST 调用获取 X profile 数据——按 FetchPI 全平台共享的稳定 JSON 模式标准化输出。
- 1 个已发布端点
- GET /v1/x/users/{username}
契约摘要（英文）: Get a normalized X profile (capability x.profile)
- 标准化响应实体
- x/profile
- capability
- x.profile
每个响应还携带新鲜度（cache / default / live）与计费元数据。
使用场景
- 用最新的 {{platform}} 主页数据充实 CRM 与外联工具——粉丝数、认证状态与简介，全部为结构化 JSON。
- 投放前用一致、可查询的主页指标筛查创作者与合作账号。
- 定期查询同一账号并对比标准化字段，持续跟踪主页变化。
返回字段
X Profile (normalized)
Normalized X profile entity. This is the ONLY upper-layer format. Provider-private fields MUST NOT appear here; unknown provider fields are dropped by the Normalizer, never passed through.
| 字段 | 类型 | 必填 | 说明 |
|---|---|---|---|
| id | string | 必填 | Platform-stable user id (numeric string on X). |
| platform | "x" | 必填 | — |
| type | "profile" | 必填 | — |
| username | string | 必填 | Handle without leading @. |
| display_name | string | null | 可选 | — |
| description | string | null | 可选 | — |
| url | string | null | 可选 | — |
| profile_image_url | string | null | 可选 | — |
| banner_image_url | string | null | 可选 | — |
| location | string | null | 可选 | — |
| verified | boolean | 必填 | Legacy verified flag. Subscription badges are NOT surfaced (provider-specific). |
| created_at | string | null | 可选 | Account creation time, UTC RFC3339; null when the provider does not expose it. |
| metrics.followers | integer | 必填 | — |
| metrics.following | integer | 必填 | — |
| metrics.posts | integer | 必填 | — |
| metrics.likes | integer | 可选 | Lifetime likes received; omitted when unknown. |
| fetched_at | string | 必填 | When the platform data was actually collected (UTC RFC3339). |
字段备注为契约英文原文。
响应元数据
| 字段 | 类型 | 必填 | 说明 |
|---|---|---|---|
| mode | cache | default | live | 必填 | Effective mode after merging param > max_age > source policy (D-004). |
| age_seconds | integer | null | 可选 | Age of served data; null when unknown. |
| source_layer | cache | db | upstream | 必填 | Which layer served the response (PRD §10). |
| stale | boolean | 可选 | True when stale data was served under stale_if_error / SWR (D-004). |
| billing.amount_credits | integer | 必填 | Micro-USD (1e-6 USD) actually charged for this request. |
| billing.cache_hit | boolean | 必填 | — |
字段备注为契约英文原文。
请求与响应示例
GET
/v1/x/users/{username}curl -H "Authorization: Bearer $MESHDATA_API_KEY" \
"https://api.fetchpi.com/v1/x/users/newdev"{
"data": {
"id": "2244994945",
"platform": "x",
"type": "profile",
"username": "newdev",
"display_name": "New Dev",
"description": "Building data APIs.",
"url": "https://x.com/newdev",
"profile_image_url": "https://cdn.example.com/avatar/newdev.jpg",
"banner_image_url": null,
"location": "Berlin",
"verified": false,
"created_at": "2019-04-01T10:15:00Z",
"metrics": {
"followers": 1204,
"following": 312,
"posts": 870,
"likes": 15200
},
"fetched_at": "2026-09-18T09:00:00Z"
},
"meta": {
"request_id": "req_01HTXQ8Z9HTQ",
"freshness": {
"mode": "default",
"age_seconds": 120,
"source_layer": "db",
"stale": false
},
"billing": {
"amount_credits": 100,
"cache_hit": false
}
}
}免费试用
注册免费账号、获取 API Key，即可在浏览器版 Playground 中直接调用该端点。
在 Playground 中试用该端点的参数表、错误码与响应语义见 API 文档。
查看端点参考常见问题
X profile API 返回什么？
一个标准化的主页对象——身份、简介与受众字段（见下方返回字段表），外加新鲜度与计费元数据。
可以免费试用该端点吗？
可以——注册账号、拿到 API Key 后，即可在控制台的 Playground 中调用该端点。
profile 能力怎么计费？
Data API 按请求以积分计费，cache/live 新鲜度有不同倍率。当前各能力的价格以价格页为准。