Examples

Real-world examples of Auth HI! configurations.

Multi-Environment API

Configure different tokens for dev, staging, and production:

# Development
Pattern: api.dev.example.com
Token: dev_token_here
Label: Dev API

# Staging
Pattern: api.staging.example.com
Token: staging_token_here
Label: Staging API

# Production
Pattern: api.example.com
Token: prod_token_here
Label: Production API

GitHub Personal Access Token

Access GitHub APIs with your PAT:

Pattern: *github.com
Token: ghp_yourPersonalAccessToken
Label: GitHub API

This covers:

• github.com/api/...
• api.github.com/...
• raw.githubusercontent.com/...

Internal Company Services

Match multiple internal services:

Pattern: *.company.internal
Token: your_internal_token
Label: Internal Services

Matches all internal subdomains but not the base domain.

Third-Party API with Multiple Endpoints

Pattern: *://api.service.com/*
Token: your_api_key
Label: Service API

Explicit scheme and path matching for precise control.

Testing Local Development

Pattern: localhost:3000
Token: dev_token
Label: Local API

Perfect for local development against your own API.

Multiple Rules for Same Domain

You can have multiple rules that match the same domain. When multiple rules match, the most specific pattern wins:

# Rule 1: General API access (less specific)
Pattern: *.api.example.com
Token: general_token
Scheme: Bearer
Label: Example API

# Rule 2: Specific service (more specific - wins!)
Pattern: auth.api.example.com  
Token: auth_service_token
Scheme: Bearer
Label: Auth Service

When a request matches both patterns, Rule 2 wins because auth.api.example.com is more specific than *.api.example.com. The extension will show a warning when 2+ rules are active on the same page.

Pattern Specificity:

• More specific parts = higher priority
• Fewer wildcards = higher priority
• Example: api.staging.example.com > *.example.com > *.com

Pro Tips

1. Use labels - Make it easy to identify rules at a glance
2. Start broad - Use *domain.com first, then narrow if needed
3. Test incrementally - Add one rule, verify it works, then add more
4. Check the context bar - Shows which rules are active for the current page