Auth-Key header. See Server API Overview for authentication details.
POST /saveOptions
Saves or updates a player’s settings. If a record for the givensteamID already exists, the content field is overwritten. Otherwise a new record is created.
Request
Shared secret configured in
appsettings.json as LodAuthKey.JSON-encoded user settings object.
Example request
Response
| Status | Meaning |
|---|---|
200 OK | Settings saved successfully. |
401 Unauthorized | Missing or invalid Auth-Key header. |
POST /loadOptions
Retrieves the settings blob for a given Steam ID.Request
Shared secret configured in
appsettings.json as LodAuthKey.JSON object with a single field.
Example request
Response
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.| Status | Meaning |
|---|---|
200 OK | Settings found; body contains the serialised content. |
401 Unauthorized | Missing or invalid Auth-Key header. |
404 Not Found | No settings record exists for the given Steam ID. |
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 toUserSettingsSave:
| Field | Type | JSON Key | Description |
|---|---|---|---|
SteamId | string | steamID | Primary key in the database. |
SettingsContent | string | content | Raw settings payload stored verbatim. |

