Problem
Chinese social media platforms — Xiaohongshu (小紅書), Bilibili, and WeChat Official Accounts (微信公眾號) — have massive user bases but no public APIs for direct publishing. This forces a "copy-ready" workflow where agents can only format content and provide manual instructions, creating significant friction.
Use Case
- Cross-post content to Chinese platforms as part of a multilingual distribution strategy
- Reach Chinese-speaking audiences without maintaining a separate manual workflow
- Support the growing demand for EN→ZH content localization and cross-posting
Context
In our cross-posting pipeline, we implemented a dual-track architecture:
- Direct Publish (via Typefully): X, LinkedIn, Threads
- Copy-Ready (manual): Xiaohongshu, Bilibili, WeChat
The copy-ready approach works but is the biggest friction point in the entire workflow. Users need to manually open each platform, paste content, adjust formatting, and publish — for every single post.
Challenges
These platforms don't offer standard REST APIs for content publishing. Possible approaches:
- Browser automation (Playwright/Puppeteer)
- Mobile API reverse-engineering (fragile, ToS concerns)
- Official partnerships or developer programs
- Enhanced copy-ready with deep-linking to reduce manual steps
Suggested Scope (incremental)
- Phase 1: Enhanced copy-ready — platform-specific formatting, deep links, clipboard integration
- Phase 2: Xiaohongshu web publishing (if API or automation becomes viable)
- Phase 3: Bilibili article publishing (Bilibili has some developer APIs)
- Phase 4: WeChat Official Account API (requires verified account)
Platforms
| Platform |
Users |
Content Type |
API Status |
| Xiaohongshu (小紅書) |
300M+ |
Image + text notes |
No public API |
| Bilibili |
400M+ |
Articles, videos |
Partial (article API exists) |
| WeChat Official (微信公眾號) |
1B+ |
Articles |
Official API (requires verification) |
Problem
Chinese social media platforms — Xiaohongshu (小紅書), Bilibili, and WeChat Official Accounts (微信公眾號) — have massive user bases but no public APIs for direct publishing. This forces a "copy-ready" workflow where agents can only format content and provide manual instructions, creating significant friction.
Use Case
Context
In our cross-posting pipeline, we implemented a dual-track architecture:
The copy-ready approach works but is the biggest friction point in the entire workflow. Users need to manually open each platform, paste content, adjust formatting, and publish — for every single post.
Challenges
These platforms don't offer standard REST APIs for content publishing. Possible approaches:
Suggested Scope (incremental)
Platforms