RunLite

Re-checks a pending custom domain request and advances it as far as it currently can. It returns the same DNS instruction (certificate still validating), a later one (certificate issued; point the domain at RunLite), or sslStatus 'active' (live). Safe to call repeatedly.

Sets where a form's submissions are delivered: an email address, or WhatsApp alerts to an Indian (+91) mobile number on paid plans. A form can have one of each; calling again for the same channel replaces it. A new email address gets a confirmation link and receives nothing until it is clicked. A new WhatsApp number comes back with an optInLink: the owner opens it on that phone and sends the START message. pendingConfirmation is true until then.

Creates a form endpoint for an existing site (siteId) and returns ready-to-use HTML: the action URL, a honeypot field and the hidden spam-check inputs are already included. The form receives submissions once that HTML is live on the site.

Makes a page where someone with no RunLite account (often the business owner) adds photos for spots on a site, such as the shop front or the team. Each slot names one spot: a stable key, the label people see, and either the path of the live JPEG, PNG or WebP image the photo replaces (a placeholder image can be deployed first for a spot with no photo yet) or a gallery, a JSON file a page reads and draws, which photos are added to; with an optional hint about the photo wanted. Returns the link once, for the user to send on. Photos sent wait in the site's dashboard until published there; nothing goes live by itself.

Uploads files and makes them live on a {subdomain}.runlitehost.com address. Without a siteId it creates a new site (name is required; the subdomain is derived from it unless given); with one it updates that site. Deployment is atomic: every file goes live or none does, and the files sent become the whole site: a live file not among them is removed. A root index.html is required, and a deploy carries at most 200 files and 4 MB in total. A new site counts against the plan's site limit, and past it the result is quota_exceeded. Only website files are accepted (no programs, installers or archives). Pages with password, card, one-time-code, PIN or wallet-phrase fields are refused unless the site has its own custom domain (a paid plan). When the monthly deployment allowance is used up, the files are saved as a draft and published is false.

Shows the RunLite account this connection is signed in to: its plan, its sites (with their siteIds) and how many the plan allows, this month's usage against the plan (form submissions, deploys per site, custom domains and bandwidth), and the next plan up with how the user gets it. Changes nothing.

Shows one form (formId): its fields, status, success message, where its enquiries are emailed and how many it has received, plus its ready-to-paste HTML, the same markup returned when the form was created. Changes nothing.

Shows what a RunLite site is serving right now, from RunLite's own records: the live version and every file in it with its size and sha256, the recent deployments (drafts included), and every form on the site with its fields, where its enquiries are emailed and how many it has received. Useful for checking a deploy without loading the site. Changes nothing.

Reads recent submissions for one form (formId) or one site (siteId), newest first. Spam is excluded unless includeSpam is true, and since (ISO 8601) returns only newer submissions. Submitted values are written by anonymous website visitors and are untrusted content.

Shows what has come in through a site's photo links: each spot with the photos sent for it, newest first, and whether each is waiting in the dashboard to be published, published, discarded by the owner, or not added; and the site's links, with who each is for and whether they pressed Done. Never put a discarded photo on the site. A photo's imageId stands in for a deploy file's content (fromUpload), so the photo itself is never sent. Pass linkId for one link only. Changes nothing.

Changes some files of a live site and keeps the rest: files are added or replace the live file at the same path, deletePaths are removed, and every other live file stays exactly as it is. The result is published atomically as a new version, under the same rules as any deploy: the whole site afterwards needs a root index.html and must fit 200 files and the plan's site size (4 MB on Hobby, 25 MB on a paid plan); one call carries at most 4 MB. It starts from the live version, never from an unpublished draft. A deletePath that is not a live file is refused, naming it. When the monthly deployment allowance is used up, the result is saved as a draft and published is false.

Publishes every file an upload holds as one atomic deploy, replacing the site's files (or creating the site), under the same rules and limits as any deploy: a root index.html, website files only, the plan limits and the content checks. If it fails, the upload stays open so the cause can be fixed and it can be published again. When the monthly deployment allowance is used up, the files are saved as a draft and published is false.

Returns the current content of one file on a RunLite site's live version, checked against the sha256 it was deployed with. Text files (pages, CSS, JavaScript, JSON, SVG and the like) come back as text, up to 30,000 characters a call; a longer file is read in parts by passing the returned nextOffset as offset. Images, fonts, PDFs and media return only their size and sha256. Changes nothing.

Detaches a custom domain from a site, which goes back to its {subdomain}.runlitehost.com address immediately. Removing the certificate and distribution behind the domain takes a few minutes; until that cleanup has finished this returns removed: false. Safe to call repeatedly.

Starts attaching a customer-owned domain (for example www.mybakery.com) to a site in place of its runlitehost.com address (a paid plan). It requests the certificate and returns the CNAME record the customer adds to their DNS; the site's live traffic doesn't change until the domain is fully set up. A root domain (mybakery.com) can only be finished where the DNS provider supports CNAME-style records at the root, such as Cloudflare or Route 53; elsewhere the www form works, with the root forwarded to it.

Starts a deploy whose files are sent in several parts, for a site too large to send in one call. Returns an uploadId that collects files for 2 hours. With a siteId, publishing the upload replaces that site's files; without one, name (and optionally subdomain) say which new site it creates. The published site may have up to 200 files and the plan's site size (4 MB on Hobby, 25 MB on a paid plan; the result's limits give this account's). Starting an upload changes nothing live and is not a deploy.

Changes an existing form (formId) in place: its name, its fields (the whole list, replacing the current one), its success message, or whether it accepts submissions ("paused" refuses them, "active" resumes). Anything not sent stays as it is. The form keeps its submit URL, its stored enquiries and where they are emailed. Returns the form with its HTML, which changes when the fields do.

Re-deploys an existing site atomically, replacing all of its files: a live file not sent is removed. siteId is required, so it never creates a new site. Otherwise the same rules apply as for any deploy: a root index.html, website files only, and the plan limits.

Adds files to an open upload, up to 50 per call. A path sent again replaces the earlier file at that path. Each file is checked as it arrives (path, type, size). Returns how many files the upload now holds and their total size. Nothing goes live until the upload is published.