Overview

The NU Signal Partners API lets approved B2B partners discover, license, play, measure, and settle video and interactive IP through one server-side integration.

Use the catalog to inspect rights-cleared inventory, create agreements, authorize short-lived playback or Runtime sessions, send canonical events, and reconcile Production settlement statements.

Base URL and environments

Sandbox and Production share the same host. The API key determines the isolated environment and data context. See Sandbox guide.

Conventions

• Versioning — The API version is fixed in the path (/v1).
• Authentication — Send a bearer API key on every protected request. See Authentication. Public onboarding and POST /v1/api-keys/bootstrap do not use a bearer key.
• JSON — Request and response bodies use application/json.
• Timestamps — Use RFC 3339 / ISO 8601 UTC timestamps (for example, 2026-06-24T00:00:00Z).
• Territory and language codes — Use ISO 3166-1 alpha-2 territory codes and ISO 639-1 language codes.
• Money — Amounts are decimal numbers paired with an ISO 4217 currency code.

Response envelopes

Successful responses place the result in data; list endpoints may also include pagination.

{
  "data": { "...": "..." },
  "pagination": { "page": 1, "limit": 20, "total": 42, "has_next": true, "next_cursor": "eyJpZCI6..." }
}

Errors use one stable envelope and machine-readable code. See Error codes.

{
  "error": {
    "code": "validation_failed",
    "message": "Request validation failed.",
    "request_id": "req_01HQ...",
    "details": [
      {
        "field": "territories",
        "issue": "zod_invalid_format",
        "message": "The value has an invalid format."
      }
    ]
  }
}

Core capabilities

For a complete first integration, continue with Quickstart.