LoadPOIDetails

RPC Configuration

Rpc Name:

Plain: LoadPOIDetails
Sha1: edbda0e437c99d3f8404dc79bdba42e405cb658e

Rpc Call

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

Rpc Parameters:

"tag" : string,
"currenttag" : string 

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:

tag

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

->

{
    "tag": "njMqjt4a",
    "currenttag": "njMqjt4a"
}

<-

{
    "displayname": "Haupteingang ABC",
    "description": "",
    "icon": "http:\/\/172.18.1.12\/img\/content\/buildings\/131.0.png",
    "position": [
        49.4987241878,
        8.46852481333
    ],
    "time": 0,
    "distance": 0,
    "floor": 0,
    "hasFlavor": false,
    "categories": [
        "#exit"
    ],
    "panoramaUri": null,
    "roomContent": [],
    "room_id": null,
    "region": null
}