How it works
An update has two halves, and they are separate problems.
- Finding. The app asks a feed or API for the newest version, compares it with its own, and decides whether to prompt.
- Installing. The app downloads the file, checks that it is genuine, replaces itself and restarts.
Frameworks cover the second half. Sparkle, the open-source updater for macOS apps, reads a feed called an appcast and requires the update archive to carry a cryptographic signature. Electron ships a built-in autoUpdater module based on the Squirrel framework. You choose one per platform and keep one rule: the update must be verified before it replaces the app.
Example: one check against Clavem
Clavem’s side is the finding half. This request uses the license key in a header, so it stays out of URLs and logs. The product id and the response values are sample values from the Clavem docs:
curl "https://clavem.io/v1/releases/75/latest?platform=macos" \
-H "X-License-Key: YOUR-LICENSE-KEY"
{
"version": "3.2.1",
"notes": "Fixes a crash when importing large files.",
"published_at": "2026-11-19T08:30:00.000Z",
"files": [
{
"id": 12,
"filename": "Inkwell-3.2.1.dmg",
"size": 50540748,
"platform": "macos",
"url": "https://clavem.io/d/12?exp=1795050000&sig=..."
}
]
}
Without a key, or with an expired or disabled one, the answer shrinks to the version and published_at. A product with no published release answers 404 with not_found; the real endpoint returns that for the public demo product today.
Three rules for the app:
- Request the download link when the customer clicks, not when the check runs. Links last one hour, and an update prompt can sit longer.
- Treat
latestas the most recently published release, not the highest version number. Your app decides what is newer; see semantic versioning. - Update checks are rate limited to 120 requests a minute per IP address, counted separately from license validation.
Auto-update versus update notification
A notification only tells the user a version exists and links to a download page. An auto-update also fetches and installs. The notification is enough for a plugin or a small tool, and installing in place is worth the extra work for an app people launch every day, where users rarely visit a website.
How Clavem handles it
Clavem delivers the files and answers the update check; it does not install anything. You upload a release in the dashboard (each file up to 5 GiB, with an optional platform label such as macos), publish it, and your app calls the endpoint above. Downloads support byte ranges, so an interrupted download resumes. Because the license key gates the download links, an update can be a paid benefit: a customer whose license has lapsed still sees that a version exists. For a full client, see check for updates in a desktop app and Releases and downloads.
Questions
Does Clavem install updates in the app?
No. Clavem stores your release files and tells your app which release is newest. Installing is done by your app or an update framework you add.
Can an expired license still see that an update exists?
Yes. Without a valid key the releases endpoint returns just the version and publish date, so your app can say a version exists and invite the customer to renew. Release notes and download links need a license that is neither expired nor disabled.