SoulFire LogoSoulFire

Update server config entry

Updates a single configuration entry identified by namespace and key. This is a granular update operation for modifying individual settings. This is the preferred method for real-time UI interactions where users modify settings one at a time. It avoids overwriting unrelated settings and is more efficient than replacing the entire configuration. If the namespace doesn't exist, it will be created. If the key doesn't exist within the namespace, it will be added. Existing values are overwritten. The change is persisted to the database, and runtime hooks are triggered to apply the new value immediately where applicable.

PUT
/v1/server/config/namespaces/:namespace/entries/:key

Updates a single configuration entry identified by namespace and key. This is a granular update operation for modifying individual settings.

This is the preferred method for real-time UI interactions where users modify settings one at a time. It avoids overwriting unrelated settings and is more efficient than replacing the entire configuration.

If the namespace doesn't exist, it will be created. If the key doesn't exist within the namespace, it will be added. Existing values are overwritten.

The change is persisted to the database, and runtime hooks are triggered to apply the new value immediately where applicable.

Authorization

AuthorizationBearer <token>

Preferred API authentication. Use a JWT with the api audience.

In: header

Path Parameters

namespace*string

The namespace of the setting to update. Namespaces group related settings together (e.g., "dev" for developer settings). Must match an existing namespace or a new namespace will be created.

key*string

The key identifying the specific setting within the namespace. Combined with namespace, this uniquely identifies the setting. Example: namespace="dev", key="soulfire-debug" for the SoulFire debug setting.

Request Body

application/json

TypeScript Definitions

Use the request body type in TypeScript.

Response Body

application/json

application/json

application/json

application/json

curl -X PUT "http://127.0.0.1:38765/v1/server/config/namespaces/:namespace/entries/:key" \  -H "Content-Type: application/json" \  -d '{    "value": {}  }'
{}
{
  "code": 0,
  "grpc-code": "string",
  "message": "string",
  "stack-trace": "string",
  "details": [
    {}
  ]
}
{
  "code": 0,
  "grpc-code": "string",
  "message": "string",
  "stack-trace": "string",
  "details": [
    {}
  ]
}
{
  "code": 0,
  "grpc-code": "string",
  "message": "string",
  "stack-trace": "string",
  "details": [
    {}
  ]
}

How is this page?

Update server config PATCH

Replaces the entire server configuration with the provided values. This is a bulk update operation primarily used for profile import functionality. Use this method when you need to apply a complete configuration snapshot, such as when importing settings from a saved profile or restoring a backup. For individual setting changes during normal operation, prefer UpdateServerConfigEntry. The new configuration is persisted to the database, and runtime hooks are triggered to apply changes immediately (e.g., log level adjustments).

List users GET

Lists all users in the system.