Skip to main content
The configuration endpoints allow you to read and modify the server configuration dynamically without restarting.

Get Configuration

endpoint
/v0/management/config
Returns the complete in-memory configuration as JSON.

Request

Response

string
Server bind address (empty for all interfaces)
number
Server port number
boolean
Debug logging enabled
string[]
List of API keys for authentication
object
Management API configuration
boolean
Allow non-localhost management access
string
Hashed management key

Get Raw Configuration

endpoint
/v0/management/config.yaml
Returns the raw YAML configuration file with all comments and formatting preserved.

Request

Response

Update Configuration

endpoint
/v0/management/config.yaml
Replaces the entire configuration file with new YAML content. The config is validated before writing.

Request

Request Body

Raw YAML configuration content.

Response

boolean
Success indicator
string[]
List of changed fields

Error Responses

Get Latest Version

endpoint
/v0/management/latest-version
Checks GitHub for the latest release version.

Request

Response

string
Latest version tag from GitHub releases

Update Individual Fields

Many configuration fields have dedicated GET/PUT/PATCH endpoints for granular updates.

Debug Mode

Usage Statistics

Logging to File

Proxy URL

Request Retry

Routing Strategy

Manage API Keys

List API Keys

Replace All Keys

Or with wrapper object:

Update Specific Key

Delete API Key

Manage Provider Keys

Gemini API Keys

Claude API Keys

Codex API Keys

OpenAI Compatibility

Vertex API Keys

Configuration Persistence

All configuration updates are:
  1. Validated before applying
  2. Written to the config file with comments preserved
  3. Immediately active (no restart required)
  4. Synchronized to disk with fsync for durability
Important: Configuration changes are persisted immediately. Make sure to backup your config file before making bulk changes.

Next Steps