User-facing authentication uses email and password, JWT access and refresh tokens, and optional device (OAuth-style) flows. These endpoints are used by the web app, CLIs, and native clients.Documentation Index
Fetch the complete documentation index at: https://docs.planasonix.com/llms.txt
Use this file to discover all available pages before exploring further.
For REST automation with an API key, see API keys. Send
Authorization: Bearer plus your API key on resource requests.https://api.planasonix.com
Session and password flows
POST /api/login
Sign in with email and password. Returns short-lived access and long-lived refresh tokens.
Account email address.
Account password.
JWT sent as
Authorization: Bearer followed by this value for API calls until it expires.Opaque token used with
POST /api/auth/refresh to obtain a new access token.POST /api/auth/refresh
Exchange a valid refresh token for a new access token (and optionally a rotated refresh token).
Refresh token returned from login or a prior refresh.
POST /api/register
Create a new user account (when self-registration is enabled for your workspace).
Email for the new account.
Password meeting your organization’s policy.
Display name.
POST /api/forgot-password
Trigger a password reset email containing a time-limited token.
Email associated with the account.
POST /api/reset-password
Complete a password reset using the token from the email.
Reset token from the email link.
New password.
POST /api/verify-email
Mark the user’s email as verified using the token from the verification email.
Verification token from the email link.
Device authorization (v2)
Headless apps (CLI, desktop, TV) use the device code pattern: the user opens a browser, enters a code, and the client polls until authorized.POST /api/v2/auth/device
Start the flow. Returns a device code, user code, and verification URI for the user.
Minimum seconds to wait between polling
POST /api/v2/auth/device/token.POST /api/v2/auth/device/token
Poll with the deviceCode until the user completes authorization or the code expires.
deviceCode from the device start response.Same client identifier used when starting the device flow.
POST /api/v2/auth/device/authorize
Browser or authenticated session confirms the userCode and grants the requested scopes to the device client.
Code shown to the user (for example
WDJB-JQKL).Typically the logged-in user’s session or Bearer access token for the approving browser session.
Using tokens on the REST API
| Credential | Typical use |
|---|---|
| JWT access token | Interactive apps after login or device flow |
| API key | Servers, CI, and long-lived integrations |