UpdateFeedSource
Updates the feedSource
RPC Configuration
Rpc Name:
Plain: UpdateFeedSource
Sha1: 5b7b263deaa6681d4c4a4a201bda28dbfc42d398
RPCs can be called by their plain name or their SHA1 representation.
Rpc Parameters:
"building_id" : int,
"source_id" : int,
"param" : string,
"trusted" : int,
"valid_for_days" : int,
"account_id" : int
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.
true
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:
SUBBUILDING_ONLY
Cache Configuration
All writing RPCs are not Cacheable, also Caching will be disabled by the paramters nocache
and readonly
.
Cache enabled:
false
Sample Request
->
{
"building_id": 1,
"source_id": 1,
"param": "",
"trusted": 1,
"valid_for_days": 30,
"account_id": 1
}
<-
true