Request
For a new customer or a customer with an active LoginSession,
email is enough:
Authorized
Responses use the standard{ code, msg, data } envelope. The examples below show the full response.
Use the token as
Authorization: Bearer {PORTAL_TOKEN} on /agent/platform/**.
Authorization required
email prefill for the Portal login page when available. The user still completes email OTP verification; the prefill only saves retyping the address.
If the user cancels or denies authorization, do not retry in a way that bypasses the browser consent. Start a new authorization request instead.
New and existing users
The portal token is access-only. The platform does not receive a portal refresh token; it obtains a new portal token with the platform client token. The platform token remains the authority for obtaining a user token and must stay on the server.
Errors
Do not include the platform token or the portal token in browser URLs, logs, or Agent-visible output.