Choose how users will connect their account to your app.

Choose Connection Type
Select the method your API supports.
Quick Comparison
Connection Type | When to use | Recommended |
|---|---|---|
Basic Auth | API key or username/password | ⚠️ For simple or internal use |
OAuth 1.0 | Legacy APIs only | ❌ Avoid if possible |
OAuth 2.0 | User login and secure access | ✅ Best for most apps |
🔐 Basic Auth
Simple authentication using an API key or username/password.
Use when your API requires:
API key
Username and password
Simple to set up
Works for internal tools or testing
Less secure than OAuth 2.0
🔁 OAuth 1.0
An older authentication method used by some APIs.
Use only if your API specifically requires it.
Older authentication method
Used by legacy APIs
Not recommended for new integrations
📘 View OAuth 1.0 setup guide
🔁 OAuth 2.0 (Recommended)
Secure authentication where users log in and grant access.
Use when users need to log in and grant access.
Secure and widely used
No password sharing
Supports user-based access
👉 Most apps should use this option
Grant Types
Choose how the login flow works.

Grant Types (Quick Comparison)
Grant Type | When to use | Recommended |
|---|---|---|
Authorization Code Guide | User login with backend (secure) | ✅ Best for most apps |
Client Credentials Guide | Server-to-server (no user login) | ⚠️ Backend only |
Implicit Guide | Browser-only apps | ❌ Less secure |
Password Credentials Guide | Direct username/password | ❌ Avoid |
What happens next
After selecting a connection type:
Configure authentication settings
Users connect their account
viaSocket handles authentication automatically
Common Authentication FAQs
Q: When should I avoid Basic Auth?
→ Use Basic only for internal or secure environments. Prefer OAuth when possible.
Q: My Auth fails—what now?
→ Check correct redirect URI, grant type, and ensure tokens refresh correctly. Expose errors clearly in Test API logs.
Q: Are tokens encrypted?
→ viaSocket stores encrypted tokens securely; tokens refresh automatically when configured.