flingflyers

Publish an HTML document at a short public URL and return the link. Use this when the user wants to view a page you made in a real browser, send it to someone, or open it on another device — anywhere handing back raw markup is not good enough. The link works for anyone who has it, with no account and no sign-in, and expires on its own (7 days by default). It is public: anyone with the URL can read the page, so do not publish anything the user would not post openly, and confirm first unless they have asked you to share it. Plain (unencrypted) only. The document reaches the server as text, so this cannot produce an encrypted flyer — for that the user runs `npx flingflyers <file> -e --persist` on their own machine, where the key is generated locally and never sent. Say so rather than implying this is private. Single self-contained document: inline the CSS, JS and images, or use data URIs. External file references will not resolve.

{
  "type": "object",
  "properties": {
    "html": {
      "type": "string",
      "description": "The complete HTML document, including <!doctype html>. Must be self-contained."
    },
    "ttl_hours": {
      "type": "integer",
      "description": "How long the link should live, in hours. Default 168 (7 days), maximum 720 (30 days).",
      "minimum": 1,
      "maximum": 720
    }
  },
  "required": [
    "html"
  ],
  "additionalProperties": false
}

Replace the contents of a flyer you already published, keeping the same URL. Use this for every revision to a page that is already live — a fix, a new section, a chart the user asked you to add — so the link they may have already sent to someone keeps working and shows the new version. Prefer this over publishing again. A second publish_flyer call mints a different URL and leaves the old page live and out of date, which is almost never what the user meant by "update it". Needs the id and owner_token returned when it was published; there are no accounts, so that token is the only proof of ownership. Send the complete replacement document, not a patch or a fragment — the old contents are overwritten and cannot be recovered. The expiry is left alone unless you pass ttl_hours, so editing a page does not quietly extend how long its link stays alive.

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "The flyer id, e.g. x7Kp2mQ."
    },
    "owner_token": {
      "type": "string",
      "description": "The owner_token returned by publish_flyer."
    },
    "html": {
      "type": "string",
      "description": "The complete replacement HTML document, including <!doctype html>. Must be self-contained."
    },
    "ttl_hours": {
      "type": "integer",
      "description": "Optional. Reset the expiry to this many hours from now, maximum 720 (30 days). Omit to keep the flyer's existing expiry.",
      "minimum": 1,
      "maximum": 720
    }
  },
  "required": [
    "id",
    "owner_token",
    "html"
  ],
  "additionalProperties": false
}

Take down a flyer immediately: the link starts returning "gone" and the stored document is deleted. Needs the id and owner_token returned when it was published — there are no accounts, so that token is the only proof of ownership and it is not recoverable if lost.

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "The flyer id, e.g. x7Kp2mQ."
    },
    "owner_token": {
      "type": "string",
      "description": "The owner_token returned by publish_flyer."
    }
  },
  "required": [
    "id",
    "owner_token"
  ],
  "additionalProperties": false
}