authentication
Refresh Token
Refresh access token using refresh token.
How it works:
- Client sends refresh_token (30-day validity)
- Server verifies refresh_token
- Server issues new access_token (24-hour validity)
- Server issues new refresh_token (30-day validity)
Use this when:
- Access token expires (after 24 hours)
- You want to extend user session without re-login
POST
Refresh Token
Documentation Index
Fetch the complete documentation index at: https://docs.mrassistant.ai/llms.txt
Use this file to discover all available pages before exploring further.
Previous
Sign UpSign up a new user and auto-create tenant for business users.
**PERMANENT USER STORAGE:**
- Users are stored in PostgreSQL database
- owner_id is generated ONCE and persists forever
- Agents are NEVER lost because owner_id never changes
**User Roles:**
- **BUSINESS**: Organization owner - automatically gets a tenant created
- **DEVELOPER**: Technical user - no tenant created (uses platform features only)
**What happens during signup:**
1. User account is created in DATABASE (not memory)
2. If role=BUSINESS → Tenant (organization) is automatically created
3. User becomes the owner of their tenant
4. Tenant ID = owner_id (for consistency)
**Business User Flow:**
- Sign up → Tenant auto-created → Create agents → Make calls
**Developer User Flow:**
- Sign up → Access platform APIs → No tenant needed
Next
Refresh Token