API Versions & Compatibility
Separate complete source contracts, narrow profiles, and end-to-end verification scope.
API pages describe contracts for the current build. An unchanged URL does not make different server, SDK, or contract versions automatically compatible.
Current snapshot
- Documentation channel
- v3-beta-snapshot
- Server source revision
60cd7c70a3a792c40fcedcc02a04366b697934cf- Receipt schema
wukongim.docs.golden-path-verification/v1- Deployment topology
- single-node cluster
- Physical hash slots
- 256
- JavaScript SDK
wukongimjssdk@1.3.5- Golden scenario / lockfile
javascript-web-quickstart/alice-bob-reconnect-sync/v1
Node.js>=20.11
SHA-256a90bb7bf4ab6441eafc049c9f5d90441230fbd5db6170ee48b254c1fe43eaa10- Test runtime target
- Node.js 22.12.0 · npm · chromium 151.0.7922.34
@playwright/test@1.62.1· revision 1234 · other browsers unverified
The snapshot's verification status covers only this basic integration flow:
| Operation | Verified behavior |
|---|---|
POST /user/token | Create a development identity |
GET /route | Discover WebSocket ingress |
POST /channel/messagesync | Recover committed messages after reconnect |
The complete Product HTTP OpenAPI covers all 41 current registrations; Operations and Webhooks have separate contracts. Three narrow profiles remain available for controlled adoption, but the end-to-end status above covers only the three basic-integration operations. Source alignment, Schema checks, and protocol pages do not expand that runtime evidence.
Version rules
- Revalidate the application flow after changing the server, SDK, or contract.
- Treat an unverified combination as unknown, not compatible by default.
- Use the complete contract for the current source surface and a narrow profile for a specific adoption scope.
Compatibility does not make an API safe for public exposure. Keep Product HTTP behind a trusted network or authenticated proxy; see the Interface Inventory for private and experimental boundaries.