OAuth 2.1 + OIDC · Official Standard

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.

OP

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.

Choose your integration method

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.

Standard · OAuth 2.1★ Recommended

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-configuration

For: production apps, user login, long-term

Create app on the platform
Lite · One address

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-configuration

For: scripts, prototypes, quick internal tests

Open Yunjii API →

Flexible options on top of the standard

📦

SDK (PHP / JS / Python / Mini-program)

Official Recommended Wrapper

Wraps 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
View docs →
🔗

REST direct (connect.php)

Low-level REST on top

Best 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
View docs →

QR code direct (api/qrcode.php)

Lightweight

Fastest login QR. Pure frontend: one <img> + polling. No backend required.

  • Frontend polling
  • UM-generated QR
  • SPA / H5 friendly
  • No backend
View docs →
🖼️

iframe / widget embed

Legacy only

Embed 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
View docs →

Not sure which to pick?

Read the integration overview to choose in 30s, or jump to the OAuth 2.1 guide.