MINARABegin Minara OAuth PKCE flow
POST /v1/auth/minara/oauth/start — Start Minara OAuth 2.0 + PKCE with a DPoP-bound native session. Persist a signing key before opening the loopback callba
POST /v1/auth/minara/oauth/start
Start Minara OAuth 2.0 + PKCE with a DPoP-bound native session. Persist a signing key before opening the loopback callback flow, then return the authorization URL for the user's browser. After consent and successful exchange, save the new account profile with a stable refresh token.
| Method | POST |
| Path | /v1/auth/minara/oauth/start |
| Auth | No auth |
| Category | auth |
Notes
New sign-ins use the minara-agent-dpop client and require a compatible Core deployment with new DPoP sessions enabled. There is no automatic downgrade to an unbound session. Private signing keys and refresh tokens never appear in this response. A failed or cancelled flow preserves the previous account. Sign-out cancels in-flight login work. Normal access-token expiry uses silent refresh; temporary connection failures do not call this route automatically.