LDWS Advanced Endpoints

get /v1/advanced/property lock/ returns the presentation settings docid\ a6ali6u szxhuansk6t3 setting and if the registry has been set to override the property lock value request example get /api/v1/advanced/property lock/ http/1 1 host {{playerip}} authorization {{digestauth}} response body the server will return a success or error message a successful response will include settingshandlerenabled bool bool whether the applying settings in the properties panel docid\ pz4pkahlr3dsspr w1sx9 is enabled forceregistrysettings bool bool whether registry settings should take priority registryenablesettings bool bool the registry value for enable settings handler bsnce bool bool whether bsn cloud is enabled response example { "data" { "result" { "settingshandlerenabled" true, "forceregistrysettings" false, "registryenablesettings" true, "bsnce" true } } } put /v1/advanced/property lock/ lets users override the current presentation settings docid\ a6ali6u szxhuansk6t3 setting request body forceregistrysettings bool bool whether registry settings should take priority registryenablesettings bool bool registry value for enable settings handler request example put /api/v1/advanced/property lock/ http/1 1 host {{playerip}} authorization {{digestauth}} this is an example of the request body { "forceregistrysettings" true, "registryenablesettings" true } response body the server will return a success or error message a successful response will almost always cause a reboot which will be indicated in the response result object object the response object success bool bool whether or not the operation was successful reboot bool bool whether or not the player is rebooting response example { "data" { "result" { "success" true, "reboot" true } } } get /v1/system/supervisor/logging/ returns the current logging level on the player the default value is info request example get /api/v1/system/supervisor/logging/ http/1 1 host {{playerip}} authorization {{digestauth}} response body status is the http response code level is the logging level on the player the higher the number, the more detail is offered name is the name of the logging level (trace, info, error, or warn) response example { "data" { "result" { "status" 200, "level" "2", "name" "info" } } } put /v1/system/supervisor/logging/ sets the logging level on the player request body level int int the integer values correspond to the logging levels 3 trace 2 info 1 warn 0 error request example put /api/v1/system/supervisor/logging/ http/1 1 host {{playerip}} authorization {{digestauth}} this is the example request body { "level" 1 } response example { "data" { "result" { "status" 200 } } }