Group Configuration Management

Complete guide for group creation and configuration, including detailed configuration instructions for basic settings, upstream addresses, advanced settings and other features

Basic Configuration

Group Name

Unique identifier for the group, used for internal system identification and management. Recommend using meaningful naming

Display Name

Friendly display name for the group, used for frontend interface display to improve readability

Channel Type

Type identifier of upstream service, determines API compatibility and request format

Test Model

Model name used for connection testing to ensure configuration correctness

Proxy Key

System-generated proxy key for API access authentication, supports generation and copy operations

Priority Weight

Priority weight of the group, higher values have higher priority, affecting load balancing strategy

Upstream Address Configuration

Multi-Address Load Balancing

Supports configuring multiple upstream addresses for load distribution and high availability. Note: Multiple addresses should be different access points of the same service, not different service providers.

• Weight-based round-robin algorithm distributes requests

• All addresses must be different nodes of the same upstream service

• Supports weighted round-robin for intelligent load distribution

Configuration Examples

https://api.openai.com

Weight: 1 (Primary address)

https://ai.proxy.com/openai

Weight: 1 (Backup address)

Feature Advantages

• High availability: Automatic switching during single point failures
• Automatic failover: Abnormal nodes automatically removed
• Performance optimization: Nearby node access improves response speed
• Real-time monitoring: Node status and response time monitoring

Advanced Configuration

Group Configuration Override

Group-level configuration parameters with higher priority than global system configuration. Unconfigured parameters will use system defaults.

Configuration Priority

1. Group Configuration (Highest priority)
2. System Configuration (Medium priority)
3. Default Configuration (Lowest priority)

Reference Documentation

For detailed overridable configuration items, please refer to the project configuration page

Custom Request Headers

Functionality

• Add custom HTTP request headers
• Remove existing request header fields
• Modify existing request header values

Configuration Examples

Authorization: Bearer custom-tokenUser-Agent: GPT-Load/1.0

Parameter Override

Advanced JSON format request parameter override functionality for forcibly overriding specific parameters in user requests. Once configured, it will automatically merge into all requests.

JSON Format

{
  "generationConfig": {
    "thinkingConfig": {
      "includeThoughts": true
    }
  },
  "tools": [
    {
      "google_search": {}
    }
  ]
}

Use Cases

• Set default parameter values
• Limit parameter ranges
• Force security parameters

Configuration Best Practices

Configuration Management

• Validate in test environment before configuration changes
• Backup current settings before important configuration changes
• Use test functionality to validate configuration effectiveness

Security Recommendations

• Regular API key rotation to ensure security
• Restrict management interface access permissions
• Monitor abnormal access and error logs