project-nomad/admin/docs/api-reference.md

1.3 KiB

API Reference

N.O.M.A.D. exposes a REST API for all operations. All endpoints are under /api/ and return JSON.


Interactive reference

The full, always-current endpoint reference is generated directly from the application's routes and validators and served as an interactive Scalar UI:

  • /reference — browse every endpoint, request/response schema, and try calls live
  • /api/openapi.json — the raw OpenAPI 3.1 document (import into Postman, Insomnia, codegen, etc.)

Because it is derived from the same VineJS validators the API validates against, it never drifts from the implementation. Prefer it over any hand-written endpoint list.


Conventions

Base URL: http://<your-server>/api

Responses:

  • Success responses include { "success": true } and an HTTP 2xx status
  • Error responses return the appropriate HTTP status (400, 404, 409, 500) with an error message
  • Long-running operations (downloads, benchmarks, embeddings) return 201 or 202 with a job/benchmark ID for polling

Async pattern: Submit a job → receive an ID → poll a status endpoint until complete.

Streaming: The /api/ollama/chat endpoint supports Server-Sent Events (SSE) when stream: true is passed. Connect using EventSource or fetch with a streaming reader.