# HTTP API: Runtime

> Driving a running page.

Glider documentation · Automation & API · Web page: https://cgglider.com/docs/http-api/runtime/

Sections of this page: [Pages](https://cgglider.com/docs/http-api.md) · [Runtime](https://cgglider.com/docs/http-api/runtime.md) · [Files, fonts & secrets](https://cgglider.com/docs/http-api/files.md) · [Checks](https://cgglider.com/docs/http-api/checks.md) · [Streaming](https://cgglider.com/docs/http-api/streams.md)

| Endpoint | Does |
| --- | --- |
| GET /api/pages/{id}/runtime | Runtime status. |
| POST /api/pages/{id}/runtime | {action: "start" \| "stop"}, optionally for one entryId. |
| GET /api/pages/{id}/runtime/stores | Current values. ?scope=data\|memory\|both and ?path= narrow it. |
| POST /api/pages/{id}/runtime/event | Emit a page event. |
| POST /api/pages/{id}/units/command | The typed unit command gate. |
| POST /api/pages/{id}/runtime/units/{unitId}/probe | Call a poller once, server-side. |

> **stores reads the live session:** Stores are persisted on a debounce, so a value a unit just wrote exists only in the running session. The endpoint reads that session when there is one and falls back to the saved page otherwise — the response says which, in source.