llms.txt
+13 −1
https://api.activationking.com/llms.txt
− - `get_session`: One session with its result media.+ - `get_session`: One session with its result media. Also works while the session is still running: status is in_progress and media holds what is ready so far (follow a booth session via its sessionId from get_remote_booth).+ - `get_white_label`: Your white label branding: app name, on/off switches, microsite colors and texts, with descriptions. App fields are per app; microsite fields are shared.+ - `update_white_label` (writes): Change some white label fields. Colors: hex string #RRGGBB (solid) or {color1, color2, color3, fillType, gradientType, lineerGradientAngle}; null clears a text or color. Needs a plan with white label. Logos and the custom domain are changed in the app.+ - `list_remote_booths`: Your booths open for remote control (one per booth and event): online now, whether operator control is on, the current screen and sessionId (the running booth session, if any). Only the account that runs the booth can control it.+ - `get_remote_booth`: A booth's current screen: actions (guest = on-screen buttons, operator = pause/resume/run...), choices, form fields (with allowed options), whether it waits for media, its stateVersion and sessionId (the running booth session, set once the booth has synced it; follow it with get_session). screenIsLive=false means the booth is offline and this is its last reported screen. Call this before send_remote_command.+ - `send_remote_command` (writes): Run an action on the booth's current screen as the operator and get the screen after it settles. actionId: an action id from the screen; for a choice use actionId 'choice' with choiceId; for a form use actionId 'submitFields' with fields. Pass stateVersion (from get_remote_booth) so the command is not sent if the screen changed. Errors before sending: action_not_available (lists the actions on this screen), invalid_choice, invalid_fields (which field and why). B+ - `upload_remote_media` (writes): Send a photo or video to the booth while its screen has a mediaRequest (e.g. after the start_upload action); the booth uses it like a capture. The reply has mediaId (the stored file: the same file content uploaded again on this account returns the same id; cloudId is the same value under its old name), sessionId (the booth session it went to, when known) and the screen after it. Give an https url or base64 data, and the file extension (.jpg, .png, .heic, .webp, + - `GET /v1/whitelabel`: Your white label branding (one app's view)+ - `PATCH /v1/whitelabel`: Change some white label fields+ - `GET /v1/remote/booths`: Your booths that are open for remote control+ - `GET /v1/remote/booths/{boothId}`: A booth and its current screen+ - `POST /v1/remote/booths/{boothId}/commands`: Run an action on the booth's current screen+ - `POST /v1/remote/booths/{boothId}/media`: Send a photo or video to the booth while it waits for media