Register new user
Creates a new user account
Query Parameters
Client type determines how refresh tokens are returned:
- web: Refresh token stored in httpOnly cookie, csrfToken returned in response
- mobile/desktop/server: refreshToken returned directly in response body
web, mobile, desktop, server Body
"user@example.com"
Password meeting configured requirements (check /api/auth/email/config for current requirements)
"securepassword123"
"John Doe"
Used for link-based email verification. The email link always opens an InsForge backend endpoint first; after the token is verified, InsForge redirects the browser to this URL. This URL must be included in allowedRedirectUrls. Recommended: use your app's sign-in page.
Response
User created successfully
JWT authentication token (null if email verification required)
CSRF token for use with refresh endpoint (web clients only, null if email verification required)
Refresh token for mobile/desktop/server clients (null for web clients or if email verification required)
Whether email verification is required before login