AddStatsFragment

RPC Configuration

Rpc Name:

Plain: AddStatsFragment
Sha1: 3215d222ca3db0c1cce28686e0b8204ca80043b7

Rpc Call

RPCs can be called by their plain name or their SHA1 representation.

Rpc Parameters:

"fragment" : object|array,
"UUID" : ?string = null 

Requires Login:

true

Requires Context:

Context

The context providing parameter can either be a contagt-id (8-Bytes, Alphaumeric) or an integer as a building id. The context parameter name should make the choice obviouse, the type has not to be defined manually.

false

Requires WriteAccess:

WriteAccess

Only accounts that have an explicit write access to the defined context can execute this RPC, no matter if the authentication level matches or not.

false

Requires AuthenticationLevel:

Context

Authentication levels allow the SuperUser to define a by-RPC granular access configuration. If RPCs are chained in a single unified call and lenient is enabled, all allowed RPCs will be executed, while execution will fail entirely with lenient set to false.

STANDARD_USER

Requires Subbuilding Merge Strategy:

REPLACE

Cache Configuration

Response Cache

All writing RPCs are not Cacheable, also Caching will be disabled by the paramters nocache and readonly.

Cache enabled:

true

Cache Time to Live:

60

Sample Request

->

{
    "fragment": [
        {
            "lat": 1234.45678,
            "lon": 1234.45678,
            "timestamp": 1588927104,
            "bid": 1,
            "floor": 1,
            "bearing": 359,
            "ble": 1,
            "inaccuracy": 2.34
        },
        {
            "lat": 1234.45678,
            "lon": 1234.45678,
            "timestamp": 1588927105,
            "bid": 1,
            "floor": 1,
            "bearing": 359,
            "ble": 1,
            "inaccuracy": 2.34
        }
    ]
}

<-

2