> ## Documentation Index
> Fetch the complete documentation index at: https://aisa.one/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Get WeChat MP Account Profile

> Get WeChat MP Account Profile

Get WeChat MP Account Profile

**Pricing** — billed per successful call; the final charge scales by your plan multiplier. Charged only when the upstream response body `code` is `200`.

<Note>
  Response structure is not yet fully documented — **refer to the actual API response**.
</Note>

## Example

```bash theme={null}
curl -X POST "https://api.aisa.one/apis/v1/tikhub/wechat_mp/v2/fetch_account_profile" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{}'  # see request schema below
```


## OpenAPI

````yaml openapi/tikhub.json POST /tikhub/wechat_mp/v2/fetch_account_profile
openapi: 3.0.0
info:
  title: TikHub API
  description: >-
    Multi-platform social media data — Douyin, TikTok, Bilibili, Kuaishou,
    Weibo, Xiaohongshu, Zhihu, and commercial (Xingtu/Huahuo/Billboard)
    endpoints.
  version: 1.0.0
servers:
  - url: https://api.aisa.one/apis/v1
security:
  - bearerAuth: []
paths:
  /tikhub/wechat_mp/v2/fetch_account_profile:
    post:
      tags:
        - TikHub - Wechat_mp
      summary: Get WeChat MP Account Profile
      description: >-
        WeChat Official Accounts (v2). Pricing and billing notes describe the
        upstream provider. Use the AIsa price quote for gateway calls.


        ### Purpose

        - Pass an account username to get the profile: nickname / IP region /
        original article count / verification entity type / linked Channels
        account, etc.

        - NOTE: **signature and avatar are not obtainable through this path** —
        WeChat's profile response carries neither. They are always `null` and
        listed in `$.data.unavailable[]` (never faked as empty strings).

        - For the **avatar**, use `/tikhub/wechat_mp/v2/fetch_article_detail_h5`
        instead (pass any article URL of that account with `raw=true`):
        `$.data.content.round_head_img` / `$.data.content.hd_head_img`. No
        endpoint currently exposes the signature.

        - Some accounts (like the example) have sparse fields; `nick_name` /
        `signature` / `head_url` may be `null`.

        - ⏱️ Due to WeChat server latency, this endpoint responds slowly; please
        set your client request timeout to 30 seconds — a timeout that is too
        small may result in being billed without receiving the response.


        ### Parameters

        - username: Official account `gh_username` (`gh_…`). Sources:
        `content.user_name` from article detail, or `jumpInfo.userName` from
        WeChat Search V2 `fetch_search` (business_type=account) results. E.g.
        `gh_363b924965e9`

        - raw: Optional, default True. True=raw; False=simplified parsing.


        ### Return

        - Official account profile info


        ### Response structure & JSON Path

        #### `raw=false` (simplified, snake_case):

        - Account username (`gh_…`): `$.data.user_name`

        - Nickname (may be null): `$.data.nick_name`

        - User role: `$.data.user_role`

        - Service type (subscription / service account code):
        `$.data.service_type`

        - Signature / description (may be null): `$.data.signature`

        - Avatar (may be null): `$.data.head_url`

        - Ban type (0=normal): `$.data.ban_type`

        #### `raw=true` (raw, default for this endpoint):

        - `data` is the full raw response (dozens of top-level fields);
        simplified fields map to nested locations:
            - Base info block: `$.data.baseInfo` (raw source of nickname / avatar / description)
            - Account info: `$.data.accountInfo` (with `userName` etc.)
            - Stats info: `$.data.statInfo`
            - Linked Channels account: `$.data.videoFinderInfo`
            - Service info (raw source of custom menu): `$.data.serviceInfo`
            - Article tab / message list: `$.data.articleTab` / `$.data.msgList`
            - IP region: `$.data.ipwording`
            - Others: `liveInfo` / `nameCard` / `gender` / `setting` / `funcFlag` etc.

        API references: `fetch_article_detail_h5` = `POST
        /tikhub/wechat_mp/v2/fetch_article_detail_h5` (operationId:
        `post_tikhub_wechat_mp_v2_fetch_article_detail_h5`); `fetch_search` =
        `POST /tikhub/wechat_search/v2/fetch_search` (operationId:
        `post_tikhub_wechat_search_v2_fetch_search`).
      operationId: post_tikhub_wechat_mp_v2_fetch_account_profile
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/FetchAccountRequest'
        required: true
      responses:
        '200':
          description: >-
            Successful response. The outer object follows `ResponseModel`; the
            endpoint-specific payload is in `data`.


            ### Return

            - Official account profile info


            ### Response structure & JSON Path

            #### `raw=false` (simplified, snake_case):

            - Account username (`gh_…`): `$.data.user_name`

            - Nickname (may be null): `$.data.nick_name`

            - User role: `$.data.user_role`

            - Service type (subscription / service account code):
            `$.data.service_type`

            - Signature / description (may be null): `$.data.signature`

            - Avatar (may be null): `$.data.head_url`

            - Ban type (0=normal): `$.data.ban_type`

            #### `raw=true` (raw, default for this endpoint):

            - `data` is the full raw response (dozens of top-level fields);
            simplified fields map to nested locations:
                - Base info block: `$.data.baseInfo` (raw source of nickname / avatar / description)
                - Account info: `$.data.accountInfo` (with `userName` etc.)
                - Stats info: `$.data.statInfo`
                - Linked Channels account: `$.data.videoFinderInfo`
                - Service info (raw source of custom menu): `$.data.serviceInfo`
                - Article tab / message list: `$.data.articleTab` / `$.data.msgList`
                - IP region: `$.data.ipwording`
                - Others: `liveInfo` / `nameCard` / `gender` / `setting` / `funcFlag` etc.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ResponseModel'
components:
  schemas:
    FetchAccountRequest:
      properties:
        username:
          type: string
          maxLength: 80
          pattern: ^[0-9A-Za-z][-_0-9A-Za-z]{1,63}(@[0-9A-Za-z]{1,16})?$
          title: Username
          description: >-
            Official account username. Three forms are supported: `gh_…`,
            `gh_…@app` (mini-program-linked accounts) and custom WeChat IDs
            (e.g. `nikejdi`). Taken from `$.data.content.user_name` of the
            article detail endpoints
          example: gh_363b924965e9
        raw:
          type: boolean
          title: Raw
          description: True=raw response; False=simplified parsed structure
          default: true
      type: object
      required:
        - username
      title: FetchAccountRequest
    ResponseModel:
      properties:
        code:
          type: integer
          title: Code
          description: HTTP status code
          default: 200
        request_id:
          title: Request Id
          description: Unique request identifier
          nullable: true
          type: string
        message:
          type: string
          title: Message
          description: Response message (EN-US)
          default: Request successful. This request will incur a charge.
        message_zh:
          type: string
          title: Message Zh
          description: Response message (ZH-CN)
          default: 请求成功，本次请求将被计费。
        support:
          type: string
          title: Support
          description: Support message
          default: 'Discord: https://discord.gg/aMEAS8Xsvz'
        time:
          type: string
          title: Time
          description: The time the response was generated
        time_stamp:
          type: integer
          title: Time Stamp
          description: The timestamp the response was generated
        time_zone:
          type: string
          title: Time Zone
          description: The timezone of the response time
          default: America/Los_Angeles
        docs:
          title: Docs
          description: Link to the API Swagger documentation for this endpoint
          nullable: true
          type: string
        cache_message:
          title: Cache Message
          description: Cache message (EN-US)
          default: >-
            This response is cached and accessible via the URL below for 24
            hours at no extra cost. The cache is for request tracing only — it
            doesn't affect the API's data freshness and won't be returned
            through the API again.
          nullable: true
          type: string
        cache_message_zh:
          title: Cache Message Zh
          description: Cache message (ZH-CN)
          default: >-
            本次响应已缓存，可通过下方 URL 直接查看，有效期 24
            小时，访问缓存链接无额外费用。缓存仅用于请求溯源，不影响接口数据的时效性，也不会再次通过接口返回。
          nullable: true
          type: string
        cache_url:
          title: Cache Url
          description: The URL to access the cached result
          nullable: true
          type: string
        router:
          type: string
          title: Router
          description: The endpoint that generated this response
          default: ''
        params:
          title: Params
          description: The parameters used in the request
          default: {}
        data:
          title: Data
          description: >-
            Endpoint-specific response payload. The official shared model does
            not declare a fixed type or field set. Use the operation's
            documented return fields or response example; an operation-specific
            schema, when present, describes the documented fields. Undocumented
            fields must be read from the actual response rather than assumed.
          nullable: true
      type: object
      title: ResponseModel
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: AIsa API key. Get yours at https://aisa.one

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.