Testing

Use a Server Test Key (sk_test_*) for integration checks. Test traffic is non-billable, including validation and guardrail diagnostics.

Use a Server Production Dry-run Key (sk_dry_...). Dry-run is selected by credential class and remains non-billable. No payout setup is required.

Before sending billable traffic, complete payout setup and activate live delivery for your project in Dashboard. Billable impressions require verified delivery records.

Server Test, Production Dry-run, and Live keys are backend-only secrets. Copy the full value when it is created or rotated; Dashboard stores only a masked preview and cannot reveal the original secret later.

Browser publishable keys are limited to their configured origins and project. They do not replace a server key and must never grant access to billing, payout, or private account operations.

The server key and browser publishable key must belong to the same Test project. Use its Project ID as client_id or WAVEBIRD_CLIENT_ID. In Dashboard API Keys, create or rotate a Server Test Key and copy the full value immediately; masked previews are for identification and cannot authenticate requests.

Key classes and rotation

A filled response should render the selected format. No-fill should leave no empty ad container and must not interrupt the AI task. Use the controlled no-fill request below to test this branch.

Test prompt, slot_hint, request-level consent, and advanced overrides separately. Validation errors include request_id and field paths such as slot_hint.max_width.

Check rendered and completion beacons for the formats you actually ship. Billing evidence depends on that path, not just on placement creation.

Call /v1/placements?wait_ms=1500&test_outcome=no_fill with the same valid body you use for a normal Test request. The response is successful and processed, but returns decision.fill: false, placement: null, and test_controlled_no_fill as its no-fill reason.

The control is accepted only with a Server Test Key and remains non-billable. Production, production dry-run, and browser keys cannot use it. Remove the query parameter for ordinary fill testing.

Intentionally missing asset_token, missing slot_id, invalid event, or stale occurred_at requests should return actionable 400 validation errors in sandbox tests.

A stale timestamp can return BEACON_TOO_LATE. Generate a fresh timestamp for every direct server beacon with new Date().toISOString().

Invalid consent purposes should return field-level validation errors. These are expected negative tests when deliberately triggered and should not be treated as production integration failures.

Default integrations should rely on hosted renderer beacons sent to /public/wrapper/v1/beacons. Direct server /v1/beacons is an advanced QA or custom-rendering path.

Direct server beacons require the sensitive asset_token from placement.asset_token or decision.asset_token. Redact it from logs, screenshots, reports, and client-visible debug output.

Production dry-run is a public pre-live validation mode selected by credential class, not by a request-body flag. Create a Server Production Dry-run Key in Dashboard API Keys, or request one from your wavebird contact. Set its sk_dry_... value as WAVEBIRD_SECRET_KEY for normal server-side /v1/placements calls. Do not send undocumented production_dry_run, production_billing_dry_run, billing_suppressed, or production_live_approved fields in request bodies; those names are response, log, or dashboard diagnostics only.

If live delivery is not activated for your project, use a Server Test Key to validate the integration. Use a Production Dry-run Key when it is available in Dashboard; it verifies the delivery path without billing.

A dry-run placement with no active SSP readiness should fail closed with 409 ssp_not_ready. The expected response/log fields include mode=production-dry-run, production_dry_run=true, production_billing_dry_run=true, billing_suppressed=true, production_live_approved=false, live_billing=false, and billable=false.

Qualifying hosted renderer proof in dry-run should report mode=production-dry-run, PRODUCTION_DRY_RUN_NON_BILLABLE, production_dry_run=true, production_live_approved=false, billing_suppressed=true, dry_run_billable_suppressed=true, and proof_would_be_eligible=true.

Use test or dry-run credentials for these checks. Do not click real ads for testing. A successful dry-run verifies delivery, not live billing. The mode is production-dry-run, not production-live-approved.