Catalog releases

Every published catalog snapshot has an immutable ID so decisions can be audited and replayed.

Release ID

The x-allm-catalog-release header is returned on API responses. A release ID identifies the full catalog snapshot, not only the records in the response.

HTTP/2 200
x-allm-catalog-release: cat_2026_07_14_8fa9b2d7c13e
x-request-id: 92e5ca2e-640c-4d36-92ea-f43f97282940
etag: "61f167a9f65ca56b277d5020"

Why pin a release

• Reproduce a price quote after public rates change.
• Explain why a deployment passed a compatibility policy.
• Review catalog drift before a rollout changes providers.
• Associate production decisions with their evidence snapshot.

Detect drift

Compare the release used by your lockfile with the latest response header. A different ID means the catalog changed somewhere; compare the locked resources before updating.

Cache safely

Use ETag for HTTP cache validation and the catalog release for business-level reproducibility. They solve different problems: an ETag fingerprints one response body, while a release identifies the entire snapshot.