WeChat Official Account owner API
Get who a WeChat Official Account is registered to, by its original ID: the owner's name, type, registration number, country, verification status, kind and date, and the account's registration date and authorised third-party services. One object a call; $0.1 per call. Errors and timeouts are not charged.
Try it
Change a value and the request on the right follows.Sign in to run it; it runs on your own balance. New accounts can try this endpoint free, up to 1 calls.
curl -G "https://api.dataxapi.com/v1/wechat_mp/accounts/owner/get" \ --data-urlencode "id=gh_3707d9541c3f" \ -H "Authorization: Bearer $DATAXAPI_API_KEY"
{
"code": "ok",
"request_id": "846a6dc4-e6a2-4a09-80d3-0c5e77f965f9",
"data": {
"item": {
"name": "阿杰爱折腾",
"type": "company",
"registration_id": null,
"country": "周末的周末露营日常,随手记录一下",
"verification": "verified",
"verification_type": "把周末露营从头到尾讲清楚,看完少走弯路",
"verified_at": "2025-11-13T00:00:00.000Z",
"account_id": "gh_9ceb787f0519",
"account_created_at": "2017-12-18T00:00:00.000Z"
}
},
"warnings": [],
"meta": {
"capability": "wechat_mp.accounts.owner.get",
"result_status": "complete",
"fetched_at": "2026-10-29T09:49:21.000Z",
"cached": false,
"replayed": false,
"unavailable": {},
"billing": {
"amount": "0.1",
"currency": "USD",
"balance_after": "9.9"
}
}
}From a response recorded 2026-10-29 09:49 UTC. Names, text and IDs are examples, and so are the links: none is the recorded one (the page shows no one's personal data); the figures are as recorded. Long lists are cut. The request ID, cursor and balance are made up.
Size as sent: 615 B in the standard view (472 B compact, 855 B full).
curl -G "https://api.dataxapi.com/v1/wechat_mp/accounts/owner/get" \ --data-urlencode "id=gh_3707d9541c3f" \ -H "Authorization: Bearer $DATAXAPI_API_KEY"
# pip install dataxapi from dataxapi import DataXAPI dx = DataXAPI() # reads DATAXAPI_API_KEY result = dx.wechat_mp.accounts.owner.get(id="gh_3707d9541c3f") print(result["data"]["item"])
// npm i @dataxapi/sdk import { DataXAPI } from "@dataxapi/sdk"; const dx = new DataXAPI(); // reads DATAXAPI_API_KEY const result = await dx.wechat_mp.accounts.owner.get({ id: "gh_3707d9541c3f" }); console.log(result.data.item);
dataxapi call wechat_mp.accounts.owner.get id=gh_3707d9541c3f
{
"mcpServers": {
"dataxapi": {
"type": "http",
"url": "https://api.dataxapi.com/mcp",
"headers": {
"Authorization": "Bearer ${DATAXAPI_API_KEY}"
}
}
}
}Add this to your MCP client, then ask your agent to call wechat_mp.accounts.owner.get.
Parameters
The account's original ID, starting with gh_; not knowing it, search the name with wechat_mp.accounts.search and take id. Example: gh_3707d9541c3f.
How much of each item to return. All three cost the same. Values: compact, standard (default), full.
Return only these fields. Each by its path, such as author.name.
Known limits
- One object per call: there is nothing to page.
Returned fields
data.item is one account owner object. Preview: the structure may change, announced beforehand.
The owner's name: the full name of a company or body, or a person's name for a personal owner
What the owner is: company, government, media, individual, or other (another kind of organisation)companygovernmentmediaindividualother
The number the owner is registered under (unified social credit code, business licence or organisation code); null where the platform gives none
The owner's country or region, in the platform's words
The account's verification: verified (a personal verification included), unverified, or expiredverifiedunverifiedexpired
The kind of verification, in the platform's words (such as 企业认证, company verification); null when not verified
Show all 13 fields →
The date the verification was granted, written as midnight UTC of that date
ID of the account asked about: this is its owner
The date the account asked about was registered, written as midnight UTC of that date
Third-party services the account asked about has authorised, in the platform's words (company names)
Which numbers of this item are approximate or lower bounds; absent when all are exact
Path of the field, such as metrics.views
Approximate, or a lower boundapproximatelower_bound
Typical size of one item: compact 146 B, standard 289 B, full 529 B (measured on the response recorded 2026-10-29 09:49 UTC).
When you are charged
X-Max-Price to refuse anything above your own limit)Prices as read 2026-10-30 14:10 UTC, under price book 6, in effect since 2026-10-29 13:23 UTC; the Playground reads the price in force before a run.
If the object does not exist
The answer is 404 not_found, charged the endpoint's price ($0.1): the data source answered it and billed for the answer. The error says so with charged: true and the amount. reason says which: not_found (it does not exist) or private_or_deleted.
Errors
What this endpoint can answer with; codes all endpoints share are on the full list.
invalid_paramsA parameter is invalidRetry: After a fixThe endpoint's price, when the data source billed the answerinsufficient_balanceThe balance is too lowRetry: After a fixNonot_foundThe object does not exist, is private or was deletedRetry: NoThe endpoint's price, when the data source billed the answerupstream_failedThe data source failedRetry: YesNotimeoutThe data did not arrive in time; retry with the same idempotency keyRetry: YesNoQuestions
How much does the WeChat Official Account owner API cost?
$0.1 per call. The most one call can cost is $0.1.
When am I not charged?
Errors and timeouts are not charged.
What happens if the object does not exist?
The answer is 404 not_found, charged the endpoint's price ($0.1): the data source answered it and billed for the answer. The error says so with charged: true and the amount. reason says which: not_found (it does not exist) or private_or_deleted.
30-day availability
13 days are on record. The share is written here once 14 days are.
It is not a success rate: how single calls went is not in it, and a failed call is not charged either way.
Every endpoint's state now, and each incident with whether anyone was charged: the status page →
All 8 WeChat Official Accounts endpoints
Use it in your AI
Copy this prompt
Your API key is built in, so there is nothing to configure.
No account yet? Sign-up takes an email and no card, and a failed call is never charged.
Paste it into your agent
It reads the page the prompt points to and connects itself.
Now ask something
Use one of these, or your own words.
Prefer to set it up by hand?
dataxapi setupgives the agents on your machine (Claude Code, Codex, Cursor) the DataXAPI MCP server and the base skill. The key is read from DATAXAPI_API_KEY; none is written into a file.MCP server: https://api.dataxapi.com/mcp. The entry for your client is under MCP in the request examples of this page; then ask your agent to call wechat_mp.accounts.owner.get.Other clients →Show the text
Use the DataXAPI endpoint wechat_mp.accounts.owner.get (WeChat Official Account owner). Get who a WeChat Official Account is registered to, by its original ID: the owner's name, type, registration number, country, verification status, kind and date, and the account's registration date and authorised third-party services. Call GET https://api.dataxapi.com/v1/wechat_mp/accounts/owner/get with the header "Authorization: Bearer $DATAXAPI_API_KEY". Read the key from the environment variable DATAXAPI_API_KEY; never write it into code. Parameters: - id (required): The account's original ID, starting with gh_; not knowing it, search the name with wechat_mp.accounts.search and take id. Example: gh_3707d9541c3f. - view: How much of each item to return. All three cost the same. Values: compact, standard (default), full. - fields: Return only these fields. Each by its path, such as author.name. Price: $0.1 per call. Errors and timeouts are not charged. The answer is JSON: data.item holds account owner; meta.billing.amount is what this call was charged. Example: curl -G "https://api.dataxapi.com/v1/wechat_mp/accounts/owner/get" \ --data-urlencode "id=gh_3707d9541c3f" \ -H "Authorization: Bearer $DATAXAPI_API_KEY" Full reference in Markdown: https://dataxapi.com/apis/wechat_mp/accounts/owner/get.md
Names and identifiers
- In Chinese
- 微信公众号主体信息 API
- Endpoint ID
wechat_mp.accounts.owner.get- Endpoint
GET /v1/wechat_mp/accounts/owner/get
Start with one key.
224 endpoints on 21 platforms, from $0.0003 a call. Errors and timeouts are not charged.