Interface PartnerRawClientOptions

Allow direct custom authorize realms for tests or private proxies. Leave disabled unless the configured host is trusted with the Master Application Key.

Validated Partner endpoint host suffixes restored from cached authorization. Facades normally manage this after authorization; direct raw clients can pass suffixes derived from trusted Partner authorization when rehydrating an auth cache. 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.

Partner endpoint calls validate URLs against suffixes recorded by authorizePartner(). A rehydrated client that skips authorization must use authorizedPartnerEndpointSuffixes or a UrlGuardedTransport 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.