Good for backward compatibility with any devices, as all API functions can be
called using GET and POST. When POST is used, the parameters can be passed to
functions either as multipart/form-data or as JSON.

API key can be sent in request parameters, session (if enabled and user is
logged in) or in HTTP X-Auth-Key header.

Standard responses in status/body:

200 OK{ “result”: “OK” } API call completed successfully.

Standard error responses in status:

400 Bad Request Invalid request params

403 Forbidden the API key has no access to this function or resource

404 Not Found method or resource/object doesn’t exist

405 Method Not Allowed API function/method not found or HTTP method is
not either GET or POST

All modified items, their status, and configuration will be written to the disk. If exec_before_save command is defined in the controller’s configuration file, it’s called before saving and exec_after_save after (e.g. to switch the partition to write mode and back to read-only).

Enables and disables debugging mode while the controller is running. After the controller is restarted, this parameter is lost and controller switches back to the mode specified in the configuration file.

Obtains authentication token which can be used in API calls instead of API key.

If both k and u args are absent, but API method is called with HTTP request, which contain HTTP header for basic authorization, the function will try to parse it and log in user with credentials provided.