Skip to content

Shell

Note

Since the device can not run on a dedicated domain, the HTTPS encryption is done by a certificate signed by the RACOM certificate authority.

Public Methods

Public method can be called as simply as:

curl \
    --insecure \
    --output - \
    --request POST \
    --header "content-type: application/json" \
    --data '{"method":"device_info_get_public"}' \
    https://10.9.8.7/cgi-bin/rpc.cgi

Private Methods

In order to call the private methods, we need to obtain the user token first:

curl \
    --insecure \
    --output - \
    --request POST \
    --header "content-type: application/json" \
    --data '{"username":"admin","password":"admin"}' \
    https://10.9.8.7/cgi-bin/login.cgi

This will return a JSON map like:

{
    "token": "<auth_token_string>",
    "role":{
        "name":"admin",
        "permission":10
    }
}

We then use the value of the attribute token as the value of the apikey header in subsequent calls to methods requiring authentication:

curl \
    --insecure \
    --output - \
    --request POST \
    --header "content-type: application/json" \
    --header "apikey: <auth_token_string>" \
    --data '{"method":"time_set","params":{"tstamp":1617692029}}' \
    https://10.9.8.7/cgi-bin/rpc.cgi