Skip to main content
The endpoints in this section are generated directly from Spillway’s OpenAPI spec (pnpm build:openapi in the monorepo), which is itself generated from the request/response zod schemas the server validates every call against — the spec can’t drift from what the server actually does.

​
Base URLs

​
Authentication

Spillway has three credential types, scoped to different planes: A virtual key never authenticates the control plane, and a session token or admin key never authenticates the data plane — the two credential families don’t cross over.
Admin-key authentication is not yet enabled. Admin keys can be minted, revealed once, listed, and revoked via /api/admin-keys, but no request path verifies them yet — a minted key currently grants no access. Use a session token (dashboard login) for control-plane calls until admin-key verification ships.

​
The two planes, at a glance

  • Data plane (/v1/*) — POST /v1/chat/completions, POST /v1/messages, GET /v1/models. The gateway itself.
  • Control plane (/api/*) — everything else: orgs, teams, members, provider keys, virtual keys, admin keys, budgets, guardrail policies, routing rules, aliases, approvals, approval policies, delegations, automation rules, alerts, decision logs, requests, and reports.

​
Errors

See Errors for response shapes and the full stable error-code taxonomy.

​
Regenerating this reference

Run from the monorepo root, then copy the resulting apps/docs/reference/openapi.json over docs-mintlify/api-reference/openapi.json — the docs site keeps its own copy so this directory can be published independently of the app build.