Documentation Index
Fetch the complete documentation index at: https://docs.alterauth.com/llms.txt
Use this file to discover all available pages before exploring further.
Getting Started
The Developer Portal (portal.alterauth.com) is where OAuth providers are configured, security policies are set, and applications are managed.Create Account
Sign up at portal.alterauth.com
OAuth Provider Setup
Add OAuth Apps
For each provider you want to support:- Go to OAuth Providers → Add Provider
- Enter credentials from the provider’s console:
- Client ID
- Client Secret
- Redirect URI: Copy the Redirect URI shown on the provider setup page
- Select the scopes you need
- Save and activate
Provider Consoles
Managed Secrets
Managed Secrets store API keys, service tokens, and other credentials for internal APIs — no OAuth flow or end-user action needed.How is this different from OAuth? With OAuth grants, the
grant_id comes from the end user completing an OAuth flow via Alter Connect. With Managed Secrets, the grant_id comes from this portal when a credential is stored. No end user is involved — the developer stores the secret, gets a grant_id, and uses it in application code.When to Use Managed Secrets
- Internal APIs that require an API key or service token
- Partner APIs that provide static credentials
- SaaS platforms with API key authentication
- Any service where you already have the credentials
Setting Up a Managed Secret Provider
Add a Provider
Click Add Provider and configure:
- Provider Name: A descriptive name (e.g., “Loyalty API”, “Billing Service”)
- Credential Type: How the secret should be injected into requests
| Credential Type | Header Format |
|---|---|
| Bearer Token | Authorization: Bearer <token> |
| API Key | Custom header (e.g., X-API-Key: <key>) |
| Basic Auth | Authorization: Basic <base64> |
Secret values are write-only — once stored, you cannot view the raw value. You can only use it via
vault.request() or replace it by storing a new value.Using Managed Secrets
Use the samevault.request() method as OAuth grants:
Managing Secrets
- Rotate: Store a new secret value on the same provider — the
grant_idstays the same - Revoke: Delete a stored secret when it’s no longer needed
- Delete Provider: Remove the provider and all its stored secrets
Policies for Managed Secrets
Managed secrets support the same policy rules as OAuth providers. Go to Policies to configure time-based access or IP allowlists for managed secret providers.Custom Schemas
Add structured data to any OAuth connection for enhanced functionality.Use Cases
- Sync Settings: Which data to sync, how often
- User Preferences: Per-connection configuration
- Metadata: Labels, tags, categories
- Internal Mapping: Link to application database records
Creating a Schema
- Go to Application → Custom Schemas
- Click Create Schema
- Use the visual builder to add fields:
- Set field types and validation:
- Types: string, number, boolean, object, array
- Validation: required, min/max, enum values
- Defaults: Set default values
- Save and apply to connections
Using Schema Data
Security Policies
Control how and when OAuth tokens can be accessed. Policies are enforced in real-time before tokens are returned from the API.Policies can only be configured for OAuth providers that you’ve already set up in the OAuth Providers tab. Add a provider there first, then configure its policy.
Policy Rule Types
| Rule | Description | Example |
|---|---|---|
| Time-Based Access | Restrict to business hours or weekdays | Mon-Fri, 9am-5pm |
| IP Allowlist | Only allow access from specific IPs | Office network 203.0.113.0/24 |
Creating Policies
Configure a Provider
Open the application, then go to OAuth Providers in the sidebar and add at least one provider (e.g., Google)
Add Policy
Click Add Policy next to a provider and configure rules:
- Time Restrictions: Check “Business hours only” (9am-5pm) or “Weekdays only” (Mon-Fri), and select a timezone
- IP Allowlist: Add IPv4/IPv6 addresses or CIDR ranges
Policy Examples
Business hours + IP allowlist — restrict to office network during work hours:Policy Evaluation
All configured rules are evaluated with AND logic — every rule must pass for token access to be granted.- Time restrictions (is it within business hours / a weekday?)
- IP allowlist (is the client IP in the allowed list?)
Fail-Closed Security
If the policy service is unavailable, the system denies all token access rather than bypassing policies. This ensures security even during outages.API Keys
Create an API Key
- Go to Application → API Keys
- Click Create Key, name it (e.g., “Production Backend”), and choose an expiration
- Copy and save the key:
alter_key_...(shown only once)
Security Best Practices
- Backend Only: Never put API keys in frontend code
- Session Tokens: Create temporary tokens for frontend
- Set Expiration: Use 90-day or shorter expiration for production keys
- Name Keys Descriptively: Use descriptive names to track what each key is for
- Environment Variables: Never commit keys to code
Connection Management
View and manage all OAuth grants:Connections Dashboard
- Filter: By provider, user, date, or custom schema fields
- Search: Find specific users or connections
- Bulk Actions: Update or revoke multiple connections
- Export: Download connection data as CSV
Connection Details
For each grant, view:- Provider and account info
- Grant ID
- Custom schema data
- Token status and refresh history
- Audit logs of all access
Revoke Access
- Find the grant
- Click Revoke
- Choose:
- Soft Revoke: Mark inactive (can reactivate)
- Hard Revoke: Delete completely
Organizations & Teams
Team Management
- Go to Organization → Team
- Invite members with roles:
- Admin: Full access
- Developer: Manage apps and connections
- Viewer: Read-only access
Multiple Applications
Create separate apps for different environments:| Environment | Purpose | API Key Type |
|---|---|---|
| Development | Local testing | Auto-expires in 30 days |
| Staging | QA testing | Standard |
| Production | Live users | IP-restricted |
Audit Logs
View all activity for an application by opening the app and navigating to Audit Logs in the app sidebar.- Filter by event type, provider, user, actor, or date range
- Search for specific connections, users, or AI agents
- Click any entry for full details
- Export as CSV for compliance reporting
Monitoring
Dashboard Metrics
- Active Connections: Total by provider
- API Usage: Calls per day/month
- Token Refreshes: Automatic refresh count
- Error Rate: Failed requests percentage
- Policy Violations: Blocked requests
Alerts
Set up notifications for:- High error rates
- Policy violations
- Approaching rate limits
- Connection failures
Quick Reference
Backend Code
Frontend Code
Support
- Documentation: docs.alterauth.com
- API Reference: Available in the Developer Portal
- Email: [email protected]
- Status: status.alterauth.com