Skip to main content
← Changelog

Faster, More Reliable Cached API Responses

Event API responses are now cached and compressed, refreshing automatically on publish for faster, more reliable visitor-facing pages.

Busy on-sale moments used to strain visitor-facing pages. Pages backed by your public event data now load faster and hold up under heavy traffic. Responses from the public event and event-instance APIs are served from a pre-built cache rather than being computed on every request, so even popular shows and busy on-sale moments stay quick and dependable.

Built ahead of time, served compressed

The cache is prepared in advance, including the listing pages visitors page through, so requests are answered from ready-made results instead of live lookups. Responses are also compressed, which keeps payloads small and pages snappy for visitors on any connection.

Refreshes automatically on publish

When you publish a change, the cache refreshes on its own, so what visitors see stays accurate without any manual steps. Saving a draft or unpublishing will not trigger a refresh, so routine editing does not churn the cache or briefly affect live pages.

Updates applied cleanly

New results are staged in full and only swapped in once they are complete. Visitors never see a half-updated page, and outdated entries are cleared as part of each refresh, so the cache stays consistent with your published content.

Feature API