Advanced SDK
The SDK is still supported, but it is now a tertiary implementation option after Server API and Script Tag. Use it when your team wants a thin TypeScript or React wrapper over the same API-first contracts described in the rest of this documentation.
Start with Server API or Script Tag. Use the SDK only when framework ergonomics, migration constraints, or package-level control justify the extra layer. Teams moving existing package integrations can follow the SDK-first migration guide.
sdk.ts
typescript
import { CslClient } from "@csl/wrapper-sdk";
const client = new CslClient({
baseUrl: "https://api.wavebird.ai",
getApiKey: () => process.env.WAVEBIRD_SECRET_KEY ?? "",
});
const job = await client.createJob({
client_id: process.env.WAVEBIRD_CLIENT_ID,
job_type: "chat",
slots_requested: 1,
});Use only when needed
When the SDK still makes sense
Typed client ergonomics
Helpful when your team wants a typed client wrapper around jobs, decisions, and beacons.
React rendering helpers
Useful if you specifically want component-level rendering helpers on top of the public API flow.
Compatibility path
Useful when you are migrating an existing SDK-based integration but want the docs and contracts to stay API-first.
Install command: npm install @csl/wrapper-sdk
Need rollout review?
Start in the dashboard, choose Script Tag or Server API, and use contact only when you need rollout review, enterprise coordination, or non-standard integration help. Billing beacon rules live in the API concepts guide.