Authentication

API Keys

All API requests require authentication via an API key. Create and manage API keys from your dashboard. Keys are prefixed with origin_sk_ for easy identification.

Keep your API keys secret. Do not expose them in client-side code, public repositories, or browser network requests. Use server-side proxy routes for browser-based applications.

{
  "key": "origin_sk_live_abc123...",
  "id": "key_01",
  "name": "production",
  "created_at": "2026-02-01T00:00:00Z"
}

{
  "keys": [
    {
      "id": "key_01",
      "name": "production",
      "masked_key": "origin_sk_...xyz",
      "created_at": "2026-02-01T00:00:00Z",
      "last_used": "2026-02-07T12:00:00Z"
    }
  ]
}

Bearer Token Format

Pass your API key in the Authorization header using the Bearer scheme. Every authenticated endpoint requires this header.

curl -H "Authorization: Bearer origin_sk_your_key" \
  https://originneural.ai/api/voices

Magic Link Auth (Session)

The Origin Neural dashboard uses magic link authentication. Users enter their email, receive a one-time link, and are authenticated via httpOnly session cookies. This flow is for the web app — use API keys for programmatic access.

{
  "message": "Magic link sent to your email."
}

{
  "user": {
    "id": "user_01",
    "email": "user@example.com",
    "plan": "pro"
  }
}

{
  "user": {
    "id": "user_01",
    "email": "user@example.com",
    "plan": "pro"
  }
}