Skip to main content

Overview

The Narrative Sports API uses API key authentication. All API requests (except health checks) require a valid API key passed as a Bearer token in the Authorization header. API keys are prefixed with sk-nr- and can be created and managed via the API Dashboard.

Making Authenticated Requests

Include your API key in the Authorization header:

Header Format

API Key Format

API keys follow this format:
For example: sk-nr-a1b2c3d4e5f6... When listed in the dashboard, keys are displayed with a truncated prefix (e.g., sk-nr-a1b2****) for security.

Authenticated Endpoints

The following endpoints require API key authentication:

Task Management

Highlights

Highlight Packages

Recaps

Upload

Example Request

Error Responses

401 Unauthorized

Missing API key:
Invalid API key:
Expired API key:

API Key Security

Keep your API key secure. Never expose it in client-side code or public repositories. The full key is only shown once at creation time and cannot be retrieved later.
Best practices:
  • Store API keys in environment variables
  • Use server-side requests only
  • Rotate keys periodically
  • Use separate keys for development and production
  • Set an expiration date on keys when possible

Public Endpoints

The following endpoints do not require authentication: