Sandbox guide

Build and test the complete integration without an executed license or real charges. Base URL: https://signal-partners.newunivers.ai/v1; keys use the nsp_test_ prefix.

What Sandbox provides

• A dummy catalog of isSandbox titles and episodes, browsable through the same Catalog API as Production.
• Playback without a license agreement: Sandbox POST /playback/tokens returns a hosted webview_url and equivalent signed manifest without an ACTIVE agreement. A partner-visible rights package is still required, and country, when present, is checked against its territories. Send non-PII preferences to test personalization. See Playback API.
• A test webview: open https://signal-partners.newunivers.ai/w/test?subtitle=ko&audio=ko&lang=ko&autoplay=1 in a WebView or iframe to validate playback end to end. It immediately plays the 9:16 Episode 009 Confession preview without a token or media setup.
• The event validation contract matches Production. Financial settlement APIs require a Production key, so Sandbox validates only ingestion results.

Isolation

Sandbox and Production share a base URL but use separate keys and data contexts. Each key has one environment encoded in its prefix; titles.isSandbox plus the environment stored on sessions and logs confines every request to that catalog. nsp_test_ selects Sandbox and nsp_live_ selects Production.

Get Sandbox data

1. Create a nsp_test_ key with the required scopes (API keys).
2. List Sandbox titles with GET /catalog/titles, then inspect IDs through /titles/{id}/episodes.
3. Issue a token, play HLS, and send events as shown in Quickstart.

Limits and differences

Validate settlement response shapes against the docs and OpenAPI examples; retrieve real statements only with Production keys. When ready to launch, follow the Production checklist.