DataNavoAPI / DOCS / WECHAT

Account owner fields and sources

Account owner fields and sources. Follow concrete contracts, examples and reviewable steps using WeChat Official Accounts.

LOCAL SIMULATIONAll displayed records are fictional fixtures. Live APIs, payments and external email are disabled.中文版 ↗
01

Object and null semantics

Account owner (account_owner) is referenced by 1 capabilities across 1 platforms. Shared names help organize records; they do not guarantee identical data coverage.

Preserve identifiers as strings. Null, absent, zero and empty arrays mean different things. Fields under ext are platform extensions, not universal guarantees.

02

Complete field paths

Field facts come from the preserved public contracts. The table merges platform extensions and identifies the platforms whose contracts declare each field.

Field pathTypeRequirementDeclaring platforms
namestring | nullOptional in contractWeChat Official Accounts
typestring | nullOptional in contractWeChat Official Accounts
registration_idstring | nullOptional in contractWeChat Official Accounts
countrystring | nullOptional in contractWeChat Official Accounts
verificationstring | nullOptional in contractWeChat Official Accounts
verification_typestring | nullOptional in contractWeChat Official Accounts
verified_atstring | nullOptional in contractWeChat Official Accounts
account_idstring | nullOptional in contractWeChat Official Accounts
account_created_atstring | nullOptional in contractWeChat Official Accounts
authorized_servicesarray | nullOptional in contractWeChat Official Accounts
approximatearray | nullOptional in contractWeChat Official Accounts
approximate[].fieldstring | nullOptional in contractWeChat Official Accounts
approximate[].kindstring | nullOptional in contractWeChat Official Accounts
extobjectOptional in contractWeChat Official Accounts
03

Capabilities returning this object

CapabilityObjectShapePagination
wechat_mp.accounts.owner.getAccount owneritemNo cursor
TRY THE CONTRACT

Clear inputs. Inspectable output.

Each click runs a local fixture. Advanced JSON inputs are checked against the selected method. Editing does not execute a request.

Copying does not execute. CLI quote is read-only and needs a local customer TEST key. Configure MCP in demo mode first. GET and POST batches both return only fictional local fixtures.

Download contract example (no execution) ↗

For TEST budgets, Key scopes or failure scenarios, open the account console. Customer sandbox ↗