HTTP API

Everything the editor can do, Glider can do over HTTP.

Machine-wide endpoints.

EndpointDoes
GET /api/recordingThe recording's status and the saved settings.
PUT /api/recordingSave the settings. 409 while a recording runs.
POST /api/recording{action: "start", pageId} or {action: "stop"}; {action: "capabilities"} lists the formats and encoders this machine's ffmpeg has.
POST /api/stingers/importUpload stinger clips or a Glider stinger package as multipart files.
POST /api/stingers/export{action: "render"} renders a stinger from a scene workflow; {action: "package"} builds a Glider package; with no action it returns the clip as a MOV, WebM or MP4 file in the export settings sent.
GET /api/stingers/assets/{id}A stinger's clip; /recipe its source scene.
GET /api/system/healthAnswers while the server is responsive. The desktop app uses it to tell a frozen server from a busy one.
GET/PUT/POST /api/system/httpsSettings › System › Secure connection: read, change, or {action: "renew"} the certificate. Changes need the access token when one is set.
GET /api/system/https/endpointWhether https is serving, and on which port.
GET /api/system/https/caThe local authority's certificate for another computer to install (DER; ?format=pem for text). Served on plain http too.
POST/DELETE /api/system/https/trustTrust the local authority on this computer, or remove it. Answered only for a window on this computer.