AddFeedSource

Class Description

Adds a new feedsource

RPC Configuration

Rpc Name:

Plain: AddFeedSource
Sha1: 2f97cc00601a2dbccd30b42caf94fddeefd52123

Rpc Call

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

Rpc Parameters:

"building_id" : int,
"mode" : string,
"limit" : int,
"trusted" : int,
"validForDays" : int,
"param" : string,
"account_id" : int 

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:

building_id

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.

true

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:

SUBBUILDING_ONLY

Cache Configuration

Response Cache

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,
    "mode": "twitter",
    "limit": 10,
    "trusted": 0,
    "validForDays": 999,
    "param": "contagt",
    "account_id": 1
}

<-

false