# SDK installation

Install wavebird when your integration needs package-level control over jobs, decisions, rendering helpers, consent, or beacons.

Install the Wavebird SDK package.

## Install

The SDK is the package path for teams that want direct control in app code. Hosted API and Script Tag paths remain available when you want Wavebird to own more of the rendering flow.

```bash
npm install wavebird
```

## Create an account

Create a wavebird account at https://dashboard.wavebird.ai/wavebird-start, complete onboarding, and create a project before you run SDK calls. The dashboard is where you copy sandbox secret keys, publishable keys, live keys, and configure browser allowed origins.

## Runtime

The Node/server client is intended for backend use with secret keys. Start with a sandbox `sk_test_...` key in `WAVEBIRD_SECRET_KEY`; switch to a live `sk_live_...` key only after production readiness is approved in the dashboard. Browser package integrations use publishable keys plus activation and allowed-origin checks. The package requires Node.js 20 or newer for server usage.

## Browser keys

Use `NEXT_PUBLIC_WAVEBIRD_PUBLISHABLE_KEY` only with a publishable key. Publishable keys are browser-safe, but they work only from origins configured in the dashboard. Never put a server secret key in browser code.

## Versioning

Pin the package version in production and review the migration guide before changing SDK-first integrations. npm README changes are delivered with package releases, so verify the published package page after each version bump.