Products, releases and files
A release is one version of a product, with release notes and one or more files: a macOS disk image, a Windows installer, a plugin ZIP. The newest published release is the one customers get. Drafts are invisible to everyone but you.
Upload and publish a release
Open the product in the dashboard. Releases and files are on its page.
- Create the release. Give it a version of up to 64 characters: letters, digits, dots, dashes, plus signs and underscores, such as
3.2.1or4.0.0-beta.2. A product cannot have the same version twice. Release notes are optional plain text, up to 20,000 characters. - Upload files. Each file can be up to 5 GiB. The dashboard sends large files in parts of at most 10 MiB, up to three files at a time. You can have at most 5 unfinished uploads open at once; a sixth is refused with
429andtoo_many_uploadsuntil one finishes or is cancelled. Give a file a platform label if it belongs to one platform: 1 to 40 characters from lowercase letters, digits, dots, dashes and underscores, such asmacos,windowsorwordpress. Clavem does not fix the list of labels. Your app asks for whatever you chose. A file with no label is universal and is offered to every platform. - Publish. A release needs at least one finished upload to be published. Publishing sets its date. Publishing again changes nothing. You can unpublish at any time.
Latest means most recently published, not highest version number and not most recently created. If you publish a backport after a newer build, the backport becomes the latest. To pull a bad build, unpublish it and the previously published release is the latest again.
Storage
Each plan includes file storage for the finished uploads on your account. Downloads are not metered and there is no bandwidth fee.
| Plan | File storage |
|---|---|
| Free | 1 GB |
| Indie | 10 GB |
| Studio | 50 GB |
| Scale | 250 GB |
The size you declare when an upload starts is reserved against your storage until the upload completes or you cancel it, so several uploads in progress cannot together overshoot the limit. An upload that is not touched for 24 hours is treated as abandoned and its reservation is released. An upload that does not fit is refused before it starts, with a storage_limit error (402) that says how much is used or reserved and how much is needed. Delete files you no longer ship, or move to a larger plan. Going over the storage limit never stops existing downloads.
{
"error": {
"code": "too_many_uploads",
"message": "You already have 5 unfinished uploads. Finish or cancel one before starting another."
}
}How customers download
A buyer's order page lists the files of the latest published release, each with a fresh link. Links are signed, so they cannot be guessed, and they expire after one hour. Opening the order page again gives new ones. A link that is invalid or has expired answers 403 with the message that the buyer should open the order page again.
- Downloads support byte ranges, so an interrupted download resumes where it stopped, and download managers work.
- Files are served as attachments with the name you uploaded, and are never rendered in the browser.
- A download that resumes from the middle of a file is not counted again in your download statistics.
curl -L -C - -O "https://clavem.io/d/12?exp=1795050000&sig=…"Update checks from your app
GET /v1/releases/:productId/latest returns the newest published release of a product. It is public, so an app can call it at launch. Send the license key in the X-License-Key header, which keeps it out of URLs, server logs and referrers. The license_key query parameter still works but is legacy; prefer the header. Add platform to get only that platform's files, plus the universal ones. :productId is the product's id from its page in the dashboard, or pid in a token.
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=…"
}
]
}The release notes and the file list, with a signed download url on each file (valid for one hour), appear only when the key belongs to a license of this product that is neither expired nor disabled. Without a key, or with a key that does not qualify, the response holds just the version and published_at. A wrong key is not an error: your app can still say that an update exists and ask the customer to renew.
{
"version": "3.2.1",
"published_at": "2026-11-19T08:30:00.000Z"
}{
"error": {
"code": "not_found",
"message": "This product has no published release yet."
}
}Request the download link when the customer clicks, not when the check runs. Links last an hour, and an update prompt can sit for longer than that. The endpoint answers 429 past 120 requests a minute per IP address, a limit counted separately from validation.
const BASE = 'https://clavem.io';
const PRODUCT_ID = 75;
const APP_VERSION = '3.2.0';
/** Resolves to { version, notes, url } when a newer build exists and this license may download it, otherwise null. */
export async function checkForUpdate(licenseKey, platform) {
const query = new URLSearchParams({ platform });
const res = await fetch(BASE + '/v1/releases/' + PRODUCT_ID + '/latest?' + query, {
headers: { 'X-License-Key': licenseKey },
signal: AbortSignal.timeout(8000),
});
if (res.status === 404) return null; // nothing published yet
if (!res.ok) throw new Error('Update check failed: HTTP ' + res.status);
const latest = await res.json();
// The server returns the newest published release. Deciding what counts as newer is up to your app.
const newer = latest.version.localeCompare(APP_VERSION, undefined, { numeric: true }) > 0;
// Notes and files come back only for a license that is valid for this product. Without them you can still
// tell the customer that version X exists and send them to renew or to your site.
const file = latest.files?.find((f) => f.url);
return newer && file ? { version: latest.version, notes: latest.notes, url: file.url } : null;
}The comparison in the sample treats versions as dotted numbers. If you use pre-release tags, compare with a semantic version library instead.
Imported licenses
Licenses imported from Lemon Squeezy have no order, so they have no order page and no emailed download link. Their owners get downloads through your app's update check, which accepts the same key, or from your own website. Customers who buy after you connect Stripe get the full order page.