OAuth 2.0 - Password Credentials

Use this legacy flow only for internal, trusted environments where the user provides credentials directly to your app.

⚠️ Security Warning: This grant is deprecated for modern apps. It bypasses the provider's login UI, placing full responsibility for credential security on your app. Use Authorization Code instead whenever possible.

1. Configure your Fields: Add optional inputs (e.g., Region).

2. Configure Access Token API: Enter the endpoint where viaSocket sends credentials to obtain an access_token.

3. Configure Refresh Token API: (Optional) Endpoint to extend session life automatically.

4. Configure Revoke Token API: (Optional) Endpoint to programmatically invalidate tokens.

5. Configure Test (Me) API: A lightweight GET endpoint (e.g., /me) to validate the connection.

6. Add Connection Label: Dynamic name for the connection (e.g., {{email}}).

7. Add Icon: Enter the key from your Test Endpoint response for the user's avatar URL (e.g., {{profile_image}}).

8. Add URLs to Whitelist: Whitelist the base domains for your API calls.

9. Add Unique Connection Identifier: Field to prevent duplicate connections (e.g., account_id).

10. Set Request Parameters: Default headers/params applied to every API call.

Disable Whitelist Domain Validation - Allows API calls to any domain, not just the ones listed above.