Skip to main content
The user settings endpoints store and retrieve an opaque settings blob keyed by Steam ID. The blob content is defined by the client (in-game Lua) and is treated as a raw string by the server. Both endpoints require the Auth-Key header. See Server API Overview for authentication details.

POST /saveOptions

Saves or updates a player’s settings. If a record for the given steamID already exists, the content field is overwritten. Otherwise a new record is created.

Request

string
required
Shared secret configured in appsettings.json as LodAuthKey.
string
required
JSON-encoded user settings object.

Example request

Response

The response body is empty on success.

POST /loadOptions

Retrieves the settings blob for a given Steam ID.

Request

string
required
Shared secret configured in appsettings.json as LodAuthKey.
string
required
JSON object with a single field.

Example request

Response

string
JSON-serialised content string that was previously saved by /saveOptions. The value is double-encoded — it is a JSON string whose value is itself a JSON object.
The 404 Not Found response is expected for first-time players who have not yet saved any settings. The client should treat a 404 as “use defaults”.

Data Model

The server maps the request to UserSettingsSave: