Developer FAQ
The answers below stay close to the released SDK surface and the documented evidence behind it.
What is live today-
wavebird is released, tested, and pre-pilot validated. Dashboard signup, key management, and the self-serve sandbox are live as well; broader market connectivity continues to expand partner by partner after real configuration and evidence.
Which integration path should I start with-
If you are still choosing an integration model, start with the API docs first. If you are intentionally using the SDK, start with SDK Server Integration plus the SDK integration flow.
Does the SDK run in Node or in the browser-
Both. Use wavebird in Node/server code with a dashboard secret key, and wavebird/browser in browser code with a dashboard publishable key. Browser usage is publishable-key based and requires activation plus allowed-origin checks before runtime calls. React Native and Electron are not part of the current official support or example surface.
What data do I pass into `createJob()`-
The minimum field is job_type. slots_requested defaults to 1. Add context, prompt, consent, brand_safety, slot_config, routing hints, or callback settings only when your integration needs them.
Do I need callback verification logic myself today-
If you use the callback path, verification is handled in integration code today. A dedicated public SDK helper is not documented.
Are proxy-compatible routes part of `WavebirdClient`-
No. Proxy compatibility is a direct HTTP integration pattern for OpenAI-compatible and Anthropic-compatible request shapes. It is not part of the WavebirdClient method family.
How do errors surface-
Public methods stay fail-silent. Use options.onError to observe structured WavebirdSdkError values and inspect machine-readable WavebirdSdkErrorCode values.
Need help diagnosing no-fill?
Start with the troubleshooting decision tree for key, request, widget, and no-fill checks.
Open troubleshooting →Testing and sandbox
Use sk_test_... keys to validate the full integration path with mock creatives and no billing.
Choose hosted defaults or package control
These pages document the package layer for teams that choose wavebird to control ad requests, decisions, rendering helpers, consent, and beacons directly. Use the API docs for hosted defaults, and use contact only when you want rollout review, enterprise coordination, or help with non-standard integration constraints. Beacon billing rules live in SDK Concepts.