Server API

Server API is the recommended default backend path. Use it when your backend already owns session state, orchestration, rendering decisions, or rollout policy. This is the reference surface the advanced SDK also adapts to.

create-job.sh

bash

RECOMMENDED

curl -X POST https://api.wavebird.ai/v1/jobs \
  -H "Authorization: Bearer sk_live_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "client_id": "wbproj_your_client_id",
    "session_id": "sess_demo_123",
    "job_type": "chat",
    "slots_requested": 1
  }'

get-decision.sh

bash

DECISION

curl -X GET https://api.wavebird.ai/v1/decisions/slot_123 \
  -H "Authorization: Bearer sk_live_your_key"

Backend control

Why use the server path

Own the lifecycle

Create jobs, poll decisions, and send beacons from your backend without browser activation concerns.

Keep secrets server-side

The secret-key path is simpler when your app already has a backend and does not need direct browser-side monetization control.

Pair with your renderer

Use your own renderer, or create the job on the server and still render through the browser path later if that fits your app better.

Patterns overview

Script Tag

Need rollout review?

Contact the team

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.