Auth
API key rules, equivalent request headers, and the endpoint domains for the convert API.
Auth
One API key, three equivalent headers
Send the key with any one of these headers:
Md2wechat-API-Key: wme_your_api_keyX-API-Key: wme_your_api_keyAuthorization: Bearer wme_your_api_keyKey prefixes: wme_ (v1 formal), wme2_ (v2 formal), wmt_ (trial, time-limited).
Applies to
POST /api/convertwith a JSON body ofmarkdown,theme,fontSize, andbackgroundType
Conversion does not need WeChat AppID, AppSecret, or an IP whitelist, and it never creates WeChat drafts.
Endpoints
- Convert:
https://www.md2wechat.cn/api/convert - Key validation:
GET/HEAD https://www.md2wechat.cn/api/auth/validate(200/204 when the key is valid) - Backup domain:
https://md2wechat.app
Limits and rate limiting
- Request body ≤ 256 KB; markdown ≤ 50,000 characters; ≤ 100 images; ≤ 50 fenced code blocks; ≤ 20 Mermaid blocks (≤ 10,000 characters each)
- 100 requests per 60 seconds per key
Notes for agents
- Keep the API key on the server side.
- Do not expose the key to browser clients.
- Prefer raw
curlor server-side fetch.