Choose yourintegration method
The only official standard of the Yunjii Open Platform is OAuth 2.1 + OIDC. REST / QR / SDK / iframe are flexible options on top of the standard, all converging to one identity backend.
Yunjii family open platform
The open platform spanning UM and the whole Yunjii family. Market ecosystem at its core, reachable via Yunjii API standardized integration.
Two ways to integrate — pick by scenario
Both reach Yunjii API; the only difference is whether you register an app first — standard for production, lite for quick tests.
Registered app · full auth
The standard interface of the Yunjii ecosystem. Plug in with Auth.js / Spring etc. — no SDK needed, stable long-term.
GET https://open.yunjii.cn/.well-known/openid-configurationFor: production apps, user login, long-term
Create app on the platform →Keyless direct · paste & go
Capability-domain routing: /user is the unified identity capability (powered by standard OAuth 2.1), consistent with /market and /models. No multi-domain juggling, no protocol trivia — paste the discovery URL and go.
GET https://api.yunjii.cn/.well-known/openid-configurationFor: scripts, prototypes, quick internal tests
Open Yunjii API → →Flexible options on top of the standard
SDK (PHP / JS / Python / Mini-program)
Official Recommended WrapperWraps signing & PKCE. Install & go. For teams who want less code (wrapper ②, the official low-code path).
- Auto sign / PKCE
- 4 languages
- MIT open source
- Rich examples
REST direct (connect.php)
Low-level REST on topBest for legacy systems needing server-side control. Hand-rolled signing + token swap, the most stable option today.
- Server-side appkey sign
- MD5 + timestamp anti-replay
- Direct userinfo / token
- Legacy compatible
QR code direct (api/qrcode.php)
LightweightFastest login QR. Pure frontend: one <img> + polling. No backend required.
- Frontend polling
- UM-generated QR
- SPA / H5 friendly
- No backend
iframe / widget embed
Legacy onlyEmbed login with zero frontend changes, but WeChat/Alipay forbid framing. Not recommended for new needs.
- Zero frontend change
- Blocked by X-Frame-Options
- Poor availability
- Use with care
Not sure which to pick?
Read the integration overview to choose in 30s, or jump to the OAuth 2.1 guide.