LoadVisitorCounts

RPC Configuration

Rpc Name:

Plain: LoadVisitorCounts
Sha1: 59676959e6da7fb6969a932cf99d75c910fcc791

Rpc Call

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

Rpc Parameters:

"buildingId" : int,
"roomIds" : array,
"oldValues" : ?array = [],
"longPoll" : bool = 1 

Parameter Description

Uses Long-Polling for Repeating Values. Client should send the correct last Value, so the response will be delayed until update. Send null to get a direct response.

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.

true

Requires contextParamName:

buildingId

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

->

{
    "buildingId": 131,
    "roomIds": [
        9090
    ],
    "oldValues": {
        "9090": 0
    },
    "longPoll": false
}

<-

[]