Clavem

Appcast

An appcast is an RSS feed with extra fields that an update framework such as Sparkle reads to learn which versions of an app exist, where to download them and how to verify them.

How it works

Sparkle’s documentation describes an appcast as an RSS feed with some extra information for Sparkle’s purposes. The app’s Info.plist holds a SUFeedURL key with the feed’s address. At each check, Sparkle downloads the feed, compares each item’s version with the app’s own CFBundleVersion, and offers the newest one. The documentation says that bundle version must be incrementing and properly formatted.

Each <item> is one release. As of November 2026, Sparkle’s template for an item looks like this:

<item>
  <title>Version 2.0 (2 bugs fixed; 3 new features)</title>
  <link>https://myproductwebsite.com</link>
  <sparkle:version>2.0</sparkle:version>
  <sparkle:releaseNotesLink>https://example.com/release_notes/app_2.0.html</sparkle:releaseNotesLink>
  <pubDate>Mon, 05 Oct 2015 19:20:11 +0000</pubDate>
  <enclosure url="https://example.com/downloads/app.zip"
             sparkle:edSignature="7cLALFUH..."
             length="1623481"
             type="application/octet-stream" />
</item>

The enclosure is the file. Its sparkle:edSignature is an EdDSA signature of the archive, which Sparkle checks before installing; the documentation says updates must be cryptographically signed to defeat tampering. Sparkle’s generate_appcast tool can build the feed and the signatures for you.

Example: what a stable URL means

The enclosure url is baked into the feed, so it must keep working for as long as the item stays in the feed. Compare two hosts:

Where the file lives Enclosure URL Works months later
A static file host https://downloads.example.com/App-3.2.1.zip Yes
A link that expires after an hour https://clavem.io/d/12?exp=...&sig=... No

A feed that holds an expired link produces a failed download for every user who checks after the hour.

Appcast versus an update API

An appcast is a static document many users read; the framework decides everything from it. An update API such as Clavem’s releases endpoint is a live question asked per user, so the answer can depend on who asks. The appcast is simpler to host and cache. The API can say “your license has lapsed” and withhold the file.

How Clavem handles it

Clavem does not generate appcasts and does not serve Sparkle feeds. The releases endpoint returns JSON with a version, notes and, for a valid license key, signed download links that last one hour. That has a consequence if you use Sparkle:

  • Option one: serve the appcast from your own backend, generated per request, so it can ask the releases endpoint for a fresh link each time. The license key has to reach your backend for that.
  • Option two: skip the appcast and have your app call GET /v1/releases/:productId/latest with the key in X-License-Key, then hand the returned link to your installer code at click time.

Sparkle’s signature check still applies to the archive you upload. Create it with Sparkle’s tool before uploading, and keep the length and sparkle:edSignature values that go with that exact file. See Releases and downloads and auto-update.

Questions

Where does an app find its appcast?

In Sparkle, you set a SUFeedURL key in the app's Info.plist to the URL where the appcast is hosted, for example https://yourcompany.example.com/appcast.xml.

Does Clavem generate an appcast?

No. Clavem's releases endpoint returns JSON, not an appcast. If you use Sparkle, you host an appcast yourself or have your app call the endpoint directly.

Sources

  1. Sparkle, Publishing an update (checked November 2026)
  2. Sparkle, Delta Updates (checked November 2026)