Skip to content

UpdateConfig

Description: Updates the editable part of the server common configuration.

Access Control

SESSION_ADMIN

Request Parameters

Name Type Required Description
name string Yes Server name
owner string Yes Owner name
timeofdemo int Yes Demo duration
timezone int Yes Timezone value
antiflood int Yes Anti-flood mode
floodcontrol int Yes Flood-control value
rollovers_mode int Yes Rollover mode
path_database string Yes Database path
path_history string Yes History path
path_log string Yes Log path
account_url string Yes Account URL
port int No Optional common port
timeout int No Optional timeout
typeofdemo int No Demo type
feeder_timeout int No Feeder timeout
daylightcorrection int No Daylight correction
keepticks int No Keep-ticks flag/value
monthly_state_mode int No Monthly statement mode
statement_mode int No Statement mode
statement_weekend int No Weekend statement flag
time_backup string No Backup schedule
fingerprint_mode int No Registration attribution mode, 0–2; see Fingerprint mode. Omitted — the current value is kept

Request Example

{
  "name": "TradeServer",
  "owner": "Broker Ltd.",
  "timeofdemo": 604800,
  "timezone": 2,
  "antiflood": 1,
  "floodcontrol": 50,
  "rollovers_mode": 1,
  "path_database": "/opt/server/db",
  "path_history": "/opt/server/history",
  "path_log": "/opt/server/logs",
  "account_url": "https://account.broker.com",
  "time_backup": "03:00",
  "fingerprint_mode": 1
}

Fingerprint mode

fingerprint_mode controls whether CustomerRegistration uses marketing touches remembered from earlier visits: the browser fingerprint (brand, IP and stable request headers, hashed on the server) and the one-hour IP fallback.

Value Mode Behaviour
0 None Stored touches are not used. A registration is attributed only by the explicit attribution object (or installation_id) in the request itself.
1 Once Default. A stored touch survives page reloads but attributes one registration only: after the customer is attached, the touch and every earlier touch with the same fingerprint are expired. A new click on a marketing link creates a new touch.
2 Always A stored touch attributes every registration from the device until it expires after 30 days.

The explicit attribution object, installation_id, CustomerRegistrationByAffiliate and the mobile app endpoints do not depend on the mode. Expired touches stay in the visit statistics. Installations created before this setting existed are migrated to 1.

Response Parameters

Name Type Description
data string Returns "OK" on success

Response Example

{
  "data": "OK"
}

Validation Error Example

{
  "error": "INVALID_DATA",
  "message": "path_log is required"
}
{
  "error": "INVALID_DATA",
  "message": "Field 'fingerprint_mode' is greater than max"
}

Backend Error Example

{
  "error": "CONFIG_UPDATE_ERROR",
  "message": "..."
}