Choose an authentication flow
Find the right GOFA credential and guide for your integration.
GOFA uses different credentials for member sign-in, client administration, and
Hosted Inquiry requests. Choose the flow for the operation you need; the
credentials are not interchangeable.
- Flutter Lessons or WebView member sign-in: Start with
SDK authentication, then the
backend member sign-in API.
Keep GOFA client credentials on your backend and supply a Firebase custom token
to the SDK through
customTokenProvider.
- Client administration from a backend: Use
Existing client integrations.
Contact GOFA for supported credential and migration details.
- Hosted Inquiry from a backend: Use
API key authentication for Vital Scan and AI Nutrition.
Keep the enterprise key on your backend and send the returned launch URL to the customer.
- Existing GOFA password or Firebase sign-in: Use
User authentication. A Firebase
custom token signs the user in; the resulting ID token identifies the user
to protected routes.
GOFA enables member sign-in separately for each environment. Complete UAT and
confirm existing members keep their records before rolling out an app migration.