DataNavoAPI / ANSWERS / WECHAT

How do I distinguish an account's original ID from its handle?

How do I distinguish an account's original ID from its handle? 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

Answer

Start by inspecting the contracts and local samples for WeChat Official Account profile, WeChat Official Account articles. Establish the input for wechat_mp.accounts.get, then check whether its account object contains the fields your task needs.

Treat identifiers as typed values: content, account, comment and share-link identifiers are not interchangeable. Preserve the original string instead of converting large IDs to JavaScript numbers, and submit only fields explicitly defined by the contract.

02

Relevant contracts

CapabilityObjectShapePagination
wechat_mp.accounts.getAccountitemNo cursor
wechat_mp.accounts.articles.listPostitemsExplicit cursor
03

Input contract

Inspect meanings, examples and conditional rules for the selected method. view and fields control the response without changing the TEST unit price.

  • Only send fields defined for this method; unknown fields are rejected before execution.
MethodFieldTypeRequirementMeaningEnum or boundExample
GETidstringRequiredThe 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"
GETviewstringOptional / conditionalHow much of each item: compact (the most used fields, long text cut short), standard, or full (adds `ext`).["compact","standard","full"]—
GETfieldsarrayOptional / conditionalReturn only these fields of each item, by path (`author.name`).maxItems: 64—
04

Complete one verification

Run one local fixture for a listed capability and inspect the object structure. Then filter, classify or export according to the question. A local sample cannot replace evidence for a real-platform conclusion.

json
{
  "capability": "wechat_mp.accounts.get",
  "method": "GET",
  "params": {
    "id": "gh_13c97ab93ce8"
  }
}
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 ↗