WeChat Official Account API
Provides programmatic access to WeChat Official Accounts for sending messages, managing menus, and handling user interactions on WeChat, the dominant super-app in mainland China.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
AppSecret must be stored securely and never exposed client-side. access_token caching is required but creates a shared secret distribution problem in multi-instance deployments. All server IPs must be whitelisted in WeChat dashboard.
⚡ Reliability
Best When
Your business operates in or targets mainland China and you have completed Chinese business registration for a verified WeChat Official Account.
Avoid When
Your users are outside China or you lack a Chinese business entity, as API access is severely limited or unavailable.
Use Cases
- • Send templated customer service messages (order confirmations, logistics updates) to WeChat followers in China
- • Build a menu-driven service bot within a WeChat Official Account for Chinese market customers
- • Handle inbound user messages and media (images, voice, location) received via WeChat webhooks
- • Manage WeChat followers — retrieve user info, segmentation tags, and subscription events
- • Integrate WeChat Pay notifications and transaction callbacks for e-commerce workflows in China
Not For
- • Reaching users outside mainland China — WeChat has minimal penetration in other markets
- • Programmatic use without Chinese business registration (a valid Chinese business license is required for most API tiers)
- • Real-time two-way messaging without user-initiated conversations (unsolicited outbound messages are heavily restricted)
Interface
Authentication
access_token obtained via AppID + AppSecret; expires every 7200 seconds (2 hours) and must be refreshed proactively. Only 2 access_token refreshes allowed per day before hitting daily limits. Webhook payloads verified via signature using token + timestamp + nonce.
Pricing
API access itself is free but requires completing Chinese business verification (营业执照). Subscription Accounts have more restrictions than Service Accounts.
Agent Metadata
Known Gotchas
- ⚠ access_token expires every 2 hours — agents must implement proactive token refresh with distributed locking to avoid parallel refresh collisions that waste the daily refresh quota
- ⚠ WeChat will redeliver webhook events multiple times if the server doesn't respond with 'success' within 5 seconds — agents must acknowledge immediately and process asynchronously
- ⚠ MsgId deduplication is the agent's responsibility; duplicate processing without tracking MsgId causes double-replies visible to users
- ⚠ Most documentation is in Chinese only; English docs are incomplete and often outdated, making error diagnosis difficult
- ⚠ API endpoints and behavior differ significantly between Subscription Accounts and Service Accounts — confirm account type before building
Alternatives
Full Evaluation Report
Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for WeChat Official Account API.
Scores are editorial opinions as of 2026-03-06.