Console APIs - Authentication
Mobile Registration
Simplified registration endpoint for mobile applications
POST
Mobile Registration
Simplified registration endpoint designed specifically for mobile applications without organization creation.Authentication
This endpoint does not require authentication as it’s used for new user registration.Request Body
string
required
User’s full name. Must be between 2-100 characters.
string
required
User’s email address. Must be a valid email format and unique in the system.
string
required
User’s password. Must meet security requirements (min 8 characters, uppercase, lowercase, number, special character).
Response Fields
object
required
Registration data object containing OTP session information.
string
required
Human-readable message describing the result of the operation.
string
required
Operation status. Always “success” for successful registration.
Error Responses
400 Bad Request
400 Bad Request
409 Conflict
409 Conflict
Usage Examples
Mobile Registration Flow
User Input
Collect user’s fullname, email, and password through mobile UI.
Register
Submit registration data to mobile registration endpoint.
OTP Verification
Guide user to enter OTP received via email.
Complete Setup
After verification, user can complete profile and join/create organization.
Differences from Standard Registration
No Organization Creation
No Organization Creation
Mobile registration doesn’t create an organization. Users can join existing organizations or create one later.
Simplified Flow
Simplified Flow
Streamlined for mobile UX with fewer required fields.
Same Verification
Same Verification
Uses the same OTP verification process as standard registration.
Best Practices for Mobile Apps
Input Validation
Input Validation
- Validate email format before submission
- Show password strength indicator
- Provide real-time validation feedback
- Disable submit button until all fields are valid
Error Handling
Error Handling
- Display user-friendly error messages
- Handle network failures gracefully
- Implement retry logic for transient failures
- Provide offline state handling
Security
Security
- Store OTP session securely in device keychain
- Clear sensitive data from memory after use
- Implement certificate pinning for API calls
- Use secure storage for user credentials
User Experience
User Experience
- Auto-focus on email field
- Show loading indicators during API calls
- Provide clear next steps after registration
- Implement email verification reminders
Related Endpoints
Validate Registration
Verify email with OTP to activate account.
Resend OTP
Resend OTP if it expires or wasn’t received.
Standard Registration
Full registration with organization creation.
Login
Login after successful registration and verification.