Interface BackupRawClientOptions

Validated Computer Backup endpoint host suffixes restored from cached Partner authorization. Facades normally manage this after authorization; direct raw clients can pass trusted suffixes derived from derivePartnerAllowedSuffixes(). Do not derive this cache with JSON.stringify(authorizePartner()), which intentionally stores a redacted token placeholder instead of a usable Partner token. Rehydrating that placeholder fails fast.

The HTTP transport used to send requests.

Computer Backup endpoint calls validate URLs against suffixes recorded by Partner authorization. A rehydrated client that skips authorization must use authorizedBackupEndpointSuffixes or a transport with a locked urlGuard. Because Partner authorize responses redact authorizationToken under JSON.stringify, durable caches should persist partnerAuthorizeResponseForPersistence(auth) only to encrypted or otherwise credential-grade storage, or use another secure token-preserving representation.