Skip to main content
ApiGlow v0.1.0
EN
FEATURE 08 / 11

An API changelog, diffed in the reader's browser.

When a schema evolves, returning readers want one thing: what moved since they last looked. ApiGlow keeps a fingerprint of the operations each reader last saw — in their own browser — and diffs the loaded document against it. No changelog service, no account, nothing sent anywhere.

demo.apiglow.dev/#/overview · petstore.yaml
The schema-changes modal after an update: three operations added, two modified, compared with the schema seen on the reader's last visit. The schema-changes modal after an update: three operations added, two modified, compared with the schema seen on the reader's last visit.

REAL SCREENSHOT, SHOWN AT 1:1

What changed since your last visit.

On load, the document is compared against the reader’s stored snapshot. A modal lists the operations added, removed and changed since — with the schema versions and the date of that last visit. Opening it once marks the diff as seen; the next changelog starts from there.
The schema-changes dialog listing three added operations and two modified ones. The schema-changes dialog listing three added operations and two modified ones.
[01]WHAT MOVED SINCE THE LAST VISIT

Badges say where.

The modal says what changed; badges say where. Added and changed operations carry a mark in the navigation — on the operation and on its group — and in the doc content itself, each with a tooltip and an accessible name, never color alone. A reader scanning the nav sees the news without opening anything.

No service behind it.

The diff is computed client-side from operation fingerprints stored in the reader’s IndexedDB, per schema URL — compact snapshots, not copies of the schema, with an LRU cap so storage stays bounded. Each reader’s changelog is genuinely theirs: it compares against their last visit, not a publication date you maintain. Nothing to host, nothing to configure.

It pairs naturally with the audit — one grades the document, the other tracks its movement — and with overlays, whose fixes show up as changes like any other edit.

A reading aid, not a contract audit.

The diff compares bounded fingerprints: a change buried below the expansion depth budget is not flagged, a first visit has nothing to compare against, and an evicted snapshot simply costs one changelog. For contract-level guarantees, diff the schema files in CI; this feature is for readers, not pipelines.

See it in the live demo.

Open the live demo Read the OpenAPI & schema guide