LoadCampaign
RPC Configuration
Rpc Name:
Plain: LoadCampaign
Sha1: bca30de7ca790eaec7b868a30db149316aaf0b5a
RPCs can be called by their plain name or their SHA1 representation.
Rpc Parameters:
"building_id" : int,
"campaign_id" : int = -1 
Building ID is transmitted for context control!
@param int building_id
@param int campaign_id
@return array|bool
Requires Login:
true
Requires 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:
building_id
Requires 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:
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
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
->
{
    "building_id": 131,
    "campaign_id": 15
}
<-
{
    "id": 15,
    "name": null,
    "enabled": null,
    "categories": [],
    "config": null,
    "content_type": null,
    "content": "",
    "handle": "campaign_0038e9bce4c22011ab348e0cf7a59613af43988f",
    "image": null,
    "audio_uri": null,
    "panorama_uri": false,
    "source_image_uri": false,
    "date_start": null,
    "date_end": null,
    "created_on": null,
    "constraints": [],
    "teaser": null,
    "campaign_type": [],
    "accessibleOnly": false,
    "withUnresolvableConstraints": true,
    "orientationPointConfig": false
}