hai-api-client

To manage HTTP API tokens and automatically refresh them, you can use a unified TypeScript HTTP client that handles Bearer token storage, attachment, and automatic refresh retries during contract-driven API calls.

A type-safe HTTP client for Web and mobile apps uses a singleton object initialized via api.init, combining Zod-based runtime validation with EndpointDef contracts to enforce consistent API usage across platforms.

To handle streaming responses in a type-safe API client, you need a client that supports SSE and ReadableStream protocols alongside strong runtime validation, ensuring data structure integrity during continuous data fetching.

Yes, this unified API client supports Zod-based runtime validation for contract-driven calls, allowing you to define typed EndpointDef contracts that validate request and response data structures automatically.

To initialize a singleton HTTP client at app startup, configure it with baseUrl and authentication settings using the api.init method, then execute authenticated requests through api.call with your defined EndpointDef.

Contract-driven API calls solve the problem of inconsistent API usage by enforcing type-safe EndpointDef structures and Zod validation, providing stronger runtime safety and unified access than standard fetch requests.