Boundary

A TypeScript SDK that normalizes third-party API interactions through a unified request pipeline, enforcing consistent error handling, rate limiting, and response shapes across providers.

Problem Statement

Applications integrating multiple third-party APIs face inconsistent response formats, error structures, rate limit behaviors, and pagination strategies. This fragmentation requires provider-specific error handling, retry logic, and data transformation code that is difficult to maintain and test.

Boundary provides a single abstraction layer that normalizes these differences, allowing applications to interact with any provider through a consistent interface while maintaining type safety and resilience patterns.

Non-Goals

- UI components or dashboards
- API mocking or stubbing frameworks
- Request recording or replay functionality
- GraphQL support (v1)
- Webhook handling (v1)
- Multi-region routing
- Built-in caching (applications can layer caching on top)

Installation

``bash
npm install boundary-sdk
`

Requirements

- Node.js ≥18.0.0 (required for fetch, Headers, AbortController, crypto.randomUUID)

Usage

IMPORTANT: Boundary requires async initialization. Always use Boundary.create():

`typescript
import { Boundary } from "boundary-sdk";

// ✅ CORRECT: Async initialization
const boundary = await Boundary.create({
github: {
auth: { token: process.env.GITHUB_TOKEN },
},
localUnsafe: true, // Required for local development without StateStorage
});

const { data, meta } = await boundary.github.get("/users/octocat");
console.log(meta.rateLimit.remaining);
`

❌ NEVER use new Boundary() - the constructor is private and will fail.

$3

For distributed deployments (serverless, multiple instances), you must provide a StateStorage implementation:

`typescript
import { Boundary } from "boundary-sdk";
import { RedisStateStorage } from "./your-redis-storage.js";

const boundary = await Boundary.create({
mode: "distributed",
stateStorage: new RedisStateStorage(redisClient), // Required in distributed mode
github: {
auth: { token: process.env.GITHUB_TOKEN },
},
});
`

Without stateStorage in distributed mode, startup will fail. This is intentional - in-memory state cannot be shared across instances.

$3

For local development, explicitly opt-in to unsafe in-memory state:

`typescript
const boundary = await Boundary.create({
mode: "local", // or omit mode
localUnsafe: true, // Explicitly acknowledge unsafe state
github: {
auth: { token: process.env.GITHUB_TOKEN },
},
});
`

Warning: localUnsafe: true means circuit breaker and rate limiter state will be lost on process restart. This is acceptable for development but must not be used in production.

Safety Guarantees

Boundary enforces safety by default:

1. Fail-Fast Initialization: SDK cannot be used before initialization completes. All methods throw if called before Boundary.create() resolves.

2. Fail-Closed State Management: Distributed mode requires StateStorage. In-memory state is opt-in only via localUnsafe: true.

3. Guaranteed Secret Redaction: All observability paths (logs, errors, metrics) automatically redact sensitive fields: authorization, cookie, token, apiKey, api_key, body.

4. No Silent Degradation: Runtime failures are explicit. Invalid configurations fail at startup. Adapter validation failures stop initialization.

Public API

$3

- static create(config: BoundaryConfig, adapters?: Map): Promise - Use this to create instances
- getCircuitStatus(provider: string): CircuitBreakerStatus | null
- registerProvider(name: string, adapter: ProviderAdapter, config: ProviderConfig): Promise

$3

Each configured provider exposes a client with:

- get(endpoint: string, options?: RequestOptions): Promise>
- post(endpoint: string, options?: RequestOptions): Promise>
- put(endpoint: string, options?: RequestOptions): Promise>
- patch(endpoint: string, options?: RequestOptions): Promise>
- delete(endpoint: string, options?: RequestOptions): Promise>
- paginate(endpoint: string, options?: RequestOptions): AsyncGenerator>`

Project Status

v2.0.0 - Production-ready safety contract established. Core functionality is stable. Provider coverage is expanding. API stability guaranteed for 2.x releases.

License

MIT. See LICENSE.md for details.