LoadBuildingSavepoint

Class Description

Loads all accessible guide savepoints. This method will only offer savepoints that were taken with the same api structure version, so internal api structure upgrades will make old savepoints unavailable. Savepoint migration is currently not supported, note that savepoints are not meant to be backups.

RPC Configuration

Rpc Name:

Plain: LoadBuildingSavepoint
Sha1: cda61b2b80a65fdb5320e5017dba8cf2ef8c3294

Rpc Call

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

Rpc Parameters:

"building_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.

ENHANCED_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": 131
}

<-

[
    {
        "saveToken": "vQGPwB16yo69NFvjNBupfEhLH350AO6Q",
        "timestamp": "2025-01-21 09:13:47+0000",
        "size": 4538516
    }
]