Docs / Referenz / Reference / API Reference
API Reference — LLMinONE Docs
What this reference covers
LLMinONE speaks a compact JSON API. Everything the web app does — build, edit, save, share, analytics — goes through the endpoints below. Always call them with a trailing slash (/api/chat/); otherwise the server redirects and a POST loses its body.
Authentication
Two ways: a bearer token from login or signup (Authorization: Bearer <token>) for members, or a device id (deviceId in the body) for anonymous visitors. Anonymous visitors have a daily build quota; members use the full engine without that cap. Admin endpoints additionally require the admin role.
Core endpoints
| Method & path | Purpose | Key fields |
|---|---|---|
POST /api/chat/ | Build, edit or chat | messages[], lang, style, refine, projectId, fileId, saveFile, deviceId |
POST /api/projects/ | Read and write projects (actions: create, get, save, list, chat, publish, unpublish) | action, projectId, deviceId |
GET /api/pulse/ | Live platform metrics | Response: buildsToday, liveNow, engine; with an admin token also errRollup and earlyWarning |
GET /api/config/ | Available models, personas and feature flags | Response: connected, providers[], personas[], settings |
POST /api/auth/ | Sign up, verify the email code, log in, log out | action, email, password, code |
POST /api/track/ | Count a page view or event (analytics) | page |
GET /api/share/ · /s/<token> | View a published app | token |
/api/appstore/ · /api/appdata/ | App-store entries and app data (rows/bytes within quota) | action, appId, rows |
Admin endpoints
The admin panel and the in-app dashboard use POST /api/admin/ with an action: get (settings), set (save knobs), analytics/insights (traffic, countries, browsers, top prompts), system (users, projects, vault, cache, router health, per-route error budget), calls (API calls and cost), auditReport and exportCsv. In addition, GET /admin/errrollup.php returns the error budget as JSON — only with a valid admin session.
Response shapes
Success returns {"ok":true, ...}. Errors come back as {"error":{"code":"...","message":"..."}} with a matching HTTP status: 400 for invalid requests, 401/403 for missing rights, 429 when the daily quota is used up, 502 when the model does not answer. While building, the server streams progress as server-sent events (phases send, reason, write, save), followed by the finished artifact.
Limits and behaviour
Anonymous visitors get a limited daily build quota; editing existing apps is unlocked for members. A running build must not be interrupted by a reload — the server keeps working and stores the result in the project. Repeating an identical wish is served from the cache and costs no tokens.