typescript-configuration-resiliencelisted

# Configuration & resilience for an APIMatic TypeScript SDK All configuration is passed at construction time in the single `Configuration` object (see **typescript-client-initialization**). Transport tuning is **nested under `httpClientOptions`** — it is not top level. ```typescript import { Client, Environment } from 'paypal-server-sdklib'; const client = new Client({ environment: Environment.{Name}, timeout: 30_000, // ms, per attempt httpClientOptions: { timeout: 30_000, // overrides the top-level timeout when present retryConfig: { /* see below */ }, proxySettings: { /* ... */ }, httpAgent: undefined, // custom Node http agent (keep-alive, TLS) httpsAgent: undefined, }, }); ``` ## Base URL / environment There is **no free-form `baseUrl` option**. The base URL is derived from the selected `Environment` member (plus any server parameters such as `port`) by a private resolver in `src/client.ts`. Read the `Environment` enum in **`src/configuration.ts`** for the real member names before naming one — they vary per API, and a name like `Production` may not exist at all. > **To reach a host no `Environment` member covers** — a gateway, a sandbox proxy, a recorded mock, a > base URL from an environment variable — route below the SDK first, with a proxy or a DNS entry, which > leaves nothing for you to maintain when the runtime moves. > > Where neither can get you there, rewrite `request.url` in an intercepto