Runtime endpoints
The local ODevice runtime exposes an HTTP and WebSocket surface for the generated clients. Endpoints are implementation details of the self-hosted runtime; use the Python SDK for normal application development.
Common paths
| Path | Purpose |
|---|---|
GET /manifest | Current application schema and device model |
GET /state | Current runtime state snapshot |
POST /auth/login | Authenticate a runtime user |
PUT /config/page | Persist a per-user page layout overlay |
DELETE /config/page/:id | Reset a page layout to its developer default |
| WebSocket runtime connection | Realtime state and command traffic |
Page layout overlays
The backend developer schema is never mutated when a user edits a dashboard. The runtime stores a separate per-user overlay and resolves it against the current developer-defined page.
See Pages & sections for the stable-ID and overlay model.
Treat endpoints as versioned runtime behavior
Do not hard-code browser clients against internal runtime paths unless you own the deployment and validation process. The Python SDK and generated client remain the supported integration boundary.