Developer documentation
Migration Guide
From internal APIs to SDK RC1
Use the published SDK packages instead of copying internal admin-console clients or hand-written fetch calls.
| Old pattern | New pattern |
|---|---|
| Manual TypeScript fetch wrappers in application code | @qvtm/control-plane |
| Browser-stored provisioning token | Backend-only provisioning token |
| Admin-console docs as integration source | Standalone Developer Portal |
| Tenant-only language | Customer/domain language where appropriate |
| Challenge status as final authority | Challenge status plus verifier evidence and local session policy |
Recommended migration sequence
- Freeze the current integration behavior.
- Replace manual API calls with the TypeScript SDK.
- Move provisioning tokens to backend-only configuration.
- Add verifier checks before creating local sessions.
- Add customer/domain validation to invite and challenge flows.
- Run SDK release gates.
- Document any local compatibility exceptions.