WeChat

Gated

weixin.qq.comPartialUpdated 27 Oct 2026 · yesterday

Getting to public launch is hard. You must register a company with the WeChat Open Platform (open.weixin.qq.com), pay for developer verification and pass a manual review of your website app, and until that review passes, not even your own account can connect.

Your work: 2–6 h
Waiting on WeChat: 4–14 days
First user connects: Only after developer verification and website app review both pass, roughly 1 to 2 weeks according to developer reports

5 not confirmed 8 sources Why this tier How did it go?

.md JSON

Use with your agent

Set up a WeChat OAuth app for our integration, as far as you can.
Guide: https://oauth-guide.akshatsethi.com/apps/wechat.md (updated 27 Oct 2026)

Gated. Hands-on work: 2–6 h. Waiting on WeChat: 4–14 days.

Check these exist first:
- WeChat Open Platform developer account [human]
- Registered company or organization [human]
- Developer verification fee [human]
- Live website and callback domain [human]
- Signed website information registration form [human]

Steps, in order:
1. [human] Register a WeChat Open Platform account
2. [human] Apply for developer verification and pay
3. [provider] Wait for verification approval (wait 1–7 days)
4. [human] Create a website app
5. [provider] Wait for website app review (wait 3–7 days)
6. [agent] Confirm WeChat Login is granted. Open the approved app. Check that 微信登录 (WeChat Login) shows as granted under 接口信息 (interface info), and note the AppID. Watch out: If WeChat Login isn't granted, authorization fails with a scope error.
7. [human] Store the AppSecret in your OAuth client
8. [agent] Configure your OAuth client endpoints. Set the authorize URL to https://open.weixin.qq.com/connect/qrconnect with appid, a URL-encoded redirect_uri, response_type=code, scope=snsapi_login and state. The token URL is https://api.weixin.qq.com/sns/oauth2/access_token, which takes appid, secret, code and grant_type=authorization_code. Watch out: WeChat uses non-standard parameter names (appid and secret instead of client_id and client_secret), so generic OAuth clients often need custom configuration. Codes expire in 10 minutes and access tokens in 2 hours.

Rules:
- Do [agent] steps yourself. Steps in WeChat's dashboard need a browser I'm signed in to; without one, give me the exact clicks and values instead, then carry on with the code.
- At each [human] or [provider] step, stop and tell me exactly what's needed.
- Never put client secrets in chat, code or commits. I paste them into our OAuth client or secret manager myself.
- Claims marked Inferred or low confidence in the guide are unverified. Check them and tell me what you find.
- If the guide doesn't match what you see (a page, field or requirement), tell me and report it so it gets fixed: POST https://oauth-guide.akshatsethi.com/api/reports with {"app": "wechat", "step": 2, "message": "what you saw"} (step is optional), or call the report_problem MCP tool. Never put secrets or personal data in a report.
- When setup ends (users can connect, or it's waiting on WeChat's review) or you can't get past a step, report how it went so the guide improves: POST https://oauth-guide.akshatsethi.com/api/reports with {"app": "wechat", "outcome": "worked" | "waiting" | "stuck", "step": 3, "message": "what happened"}, or call the report_setup MCP tool. Stopping for me at a [human] step isn't stuck: don't report that.
- Finish with what's done, the redirect URI and scopes used, and what's left before public launch.

Paste into Claude Code, Cursor or any agent.

WeChat

Plan

SetupBefore you start

BuildApproved website app

LaunchPublic launch

Why gated

Scopes

When you get stuck

Not confirmed

Sources

Feedback

WeChat

Plan

SetupBefore you start

BuildApproved website app

LaunchPublic launch

Why gated

Scopes

When you get stuck

Not confirmed

Sources

Feedback