Follow these steps to integrate AuthFlow's email/password authentication endpoints into your backend applications.
Sign up for AuthFlow and create your first project. You'll get your server-side API key instantly for secure email/password authentication.
Use our /auth endpoints from your backend to handle user authentication. All endpoints require your organization's API key for secure email/password login.
All /auth endpoints require your organization's API key in JWT tokens for secure email/password authentication
Call from your server-side code, never expose API keys to frontend
Handle user sessions with JWT tokens containing org API key for reliable email/password authentication
Wrap your app with your provider and start using authentication components. It's that simple with reliable email/password authentication!
Complete technical documentation for integrating AuthFlow's email/password authentication endpoints into your backend applications.
Your organization's API key is embedded in all JWT tokens for /auth endpoints. Store this securely in your backend environment variables for reliable email/password authentication.
Security Note: Security Note: Never expose your API key in frontend code or client-side JavaScript. All /auth endpoint calls must be made from your backend server for secure email/password authentication.
Generate temporary anti-abuse tokens for authentication flows
identity (string): User's email addressCreate new user accounts within your organization
foobar (string): Token from /auth/fooBarapi_key (string): Your organization's API keyemail (string): User's email addresspassword (string): User's password (8-32 chars, uppercase, lowercase, number, special char)fullname (string): User's full namedisclaimed (string): Must be "true"Authenticate users and receive session tokens
foobar (string): Token from /auth/fooBaremail (string): User's email addresspassword (string): User's passwordorg_id (string): Your organization's UUIDThe returned JWT contains: email, org_id, and your api_key
Validate user session tokens and check authentication status
sessionToken (string): JWT from /auth/loginemail (string): User's email addressAllow authenticated users to change their passwords
sessionToken (string): JWT from /auth/loginemail (string): User's email addressnewPassword (string): New password (same complexity requirements)End user sessions securely
sessionToken (string): JWT from /auth/loginemail (string): User's email addressImplementation Notes:
200: Success400: Bad Request (missing/invalid parameters)401: Unauthorized (invalid tokens, wrong API key, etc.)404: User not found409: Organization already exists (signup)500: Server errorCritical: All /auth endpoints must be called from your backend server only. Never expose your API key or make these calls from client-side JavaScript, as this would compromise your organization's security.
Wire the endpoints, we provide you the Sessions with reliable JWT tokens. It's that simple! 🤝