# 微信公众号资料

微信公众号资料：查看输入、账号字段、分页与使用边界，并在本地运行模拟请求。

规范页面: https://datanavoapi.com/apis/wechat_mp/accounts/get/

当前为本地模拟模式；样本由程序生成，不代表平台实时数据，也不证明真实供应商的可用性。

## 这条能力做什么

微信公众号资料以 /v1/wechat_mp/accounts/get 为入口；GET 返回 data.item，对象为账号。

当前为本地模拟模式；样本由程序生成，不代表平台实时数据，也不证明真实供应商的可用性。

- 能力标识：wechat_mp.accounts.get
- 分页：此能力没有游标分页，不应无限重复调用。

## 输入合同

按所选方法查看参数含义、示例和条件规则；view 与 fields 控制返回内容，不改变 TEST 单价。

- 只传本方法定义的参数；未知字段在执行前拒绝。

| 方法 | 字段 | 类型 | 要求 | 含义 | 枚举或边界 | 示例 |

| --- | --- | --- | --- | --- | --- | --- |

| GET | id | string | 必填 | The account's original ID, mostly starting with gh_ but not always, not the account's name; knowing only the name, find it with wechat.accounts.search and take id; an article's author.id is one too | — | "gh_13c97ab93ce8" |

| GET | view | string | 可选/条件 | How much of each item: compact (the most used fields, long text cut short), standard, or full (adds `ext`). | ["compact","standard","full"] | — |

| GET | fields | array | 可选/条件 | Return only these fields of each item, by path (`author.name`). | maxItems: 64 | — |

## 在本地试一次

先使用 demo 验证字段，再用客户测试 Key 显式选择 simulated 演练结算。不要把客户 Key 写入网址。

```json
{
  "capability": "wechat_mp.accounts.get",
  "method": "GET",
  "params": {
    "id": "gh_13c97ab93ce8"
  }
}
```

- [打开这条能力的调试台](https://datanavoapi.com/console/?mode=demo&capability=wechat_mp.accounts.get&method=GET&params=%7B%22id%22%3A%22gh_13c97ab93ce8%22%7D)

## 返回字段与解释

统一对象 account 允许空值；缺失字段不能替换成零。当前页展示主要结构，完整嵌套字段见对象文档。

| 字段 | 类型 | 含义 | 字段来源 |

| --- | --- | --- | --- |

| id | string \| null | ID | 微信公众号 |

| username | string \| null | Handle | 微信公众号 |

| name | string \| null | Display name | 微信公众号 |

| url | string \| null | Link to the profile | 微信公众号 |

| bio | string \| null | Bio | 微信公众号 |

| avatar_url | string \| null | Avatar (standard view and up) | 微信公众号 |

| verified | boolean \| null | Whether the account is verified (standard view and up) | 微信公众号 |

| created_at | string \| null | When the account was created (standard view and up) | 微信公众号 |

| metrics | object \| null | Account counts | 微信公众号 |

| metrics.followers | integer \| null | Followers | 微信公众号 |

| metrics.following | integer \| null | Following | 微信公众号 |

| metrics.posts | integer \| null | Posts published | 微信公众号 |

| approximate | array \| null | Which numbers of this item are approximate or lower bounds; absent when all are exact | 微信公众号 |

| approximate[].field | string \| null | Path of the field, such as metrics.views | 微信公众号 |

| approximate[].kind | string \| null | Approximate, or a lower bound | 微信公众号 |

| ext | object | — | 微信公众号 |

| ext.ip_location | string \| null | IP location as the platform shows it (a province or a country, without the IP属地 label); null for an account that shows none (full view) | 微信公众号 |

| ext.original_articles | integer \| null | Number of original articles (full view) | 微信公众号 |

| ext.channels_id | string \| null | ID of the linked Channels account (full view) | 微信公众号 |

| ext.biz | string \| null | The account's __biz: what follows __biz= in the links of its articles (full view) | 微信公众号 |

| ext.owner_name | string \| null | Name of the account's owner (a company or body); null for a personal account and where none is on record (full view) | 微信公众号 |

| ext.estimated_followers | integer \| null | Estimated active followers: a third-party database's estimate from reads and the like, not a follower count the platform publishes (it publishes none), and possibly weeks to months old (full view) | 微信公众号 |

| ext.estimated_headline_reads | integer \| null | Estimated average reads of the account's lead articles: a third-party database's estimate, possibly out of date (full view) | 微信公众号 |

| ext.estimated_headline_likes | integer \| null | Estimated average likes of the account's lead articles: a third-party database's estimate, possibly out of date (full view) | 微信公众号 |

| ext.estimated_weekly_articles | integer \| null | Estimated articles a week: as a third-party database counts them, possibly out of date (full view) | 微信公众号 |

| ext.estimated_last_published_at | string \| null | When the account last published, as a third-party database has it; earlier than the truth when the database has not caught up (full view) | 微信公众号 |

| ext.banned | boolean \| null | Whether the platform has banned the account (the ban type it gives is not "normal") (full view) | 微信公众号 |

- [完整对象字段](https://datanavoapi.com/docs/objects/account/)

## 明确缺失的字段

以下缺失原因来自公开合同，用于解释本接口边界；本地样本不证明真实平台可用。

| 字段 | 缺失原因 |

| --- | --- |

| username | capability |

| url | platform |

| bio | capability |

| avatar_url | capability |

| verified | capability |

| created_at | capability |

| metrics | capability |

## 边界与核对

接口成功不等于覆盖全部公开内容。保留请求编号、采样时间、参数和分页位置，先核对返回条目，再进行分析。

本地模拟只使用 TEST 积分；真实 API、正式支付和外部邮件均关闭。原站历史价格不作为DataNavoAPI收费标准。

- 媒体地址、计数和显示字段的可用性应逐项核验。

## 相关页面

- [微信公众号接口](https://datanavoapi.com/apis/wechat_mp/)
- [微信公众号 MCP](https://datanavoapi.com/mcp/wechat_mp/)
- [账号字段](https://datanavoapi.com/docs/objects/account/)
- [公众号 fakeid 与账号标识如何区分？](https://datanavoapi.com/answers/wechat-fakeid/)
- [公众号 biz 与微信号应该怎样使用？](https://datanavoapi.com/answers/wechat-official-account-biz/)
- [公众号账号、文章与互动有哪些接口？](https://datanavoapi.com/answers/wechat-official-account-data-apis/)
- [公众号粉丝数是否一定可通过公开接口获取？](https://datanavoapi.com/answers/wechat-official-account-follower-count/)

[English](https://datanavoapi.com/en/apis/wechat_mp/accounts/get/)
