LoginViaEmail
Requests a new Login Link for a User Account, so the User can (re)login using a link. The user will need to login after this.
RPC Configuration
Rpc Name:
Plain: LoginViaEmail
Sha1: 99c003671a97663498cb5c947497881b61c49e03
RPCs can be called by their plain name or their SHA1 representation.
Rpc Parameters:
"email" : string
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.
false
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:
false
Sample Request
->
{
"email": "no-reply@contagt.com"
}
<-
{
"account_id": 1,
"token": "ea75c32046a8be46a47474931df9ffe4"
}