Venue

Six reads describe a venue completely. They are cheap, cacheable on your side, and change only when the operator edits something in the console. All of them take the venue's slug in the path, need a key (Keys and headers), and answer 404 with a problem body when no venue has that slug. Each read has its own page below, with its response fields, a JSON example and request samples in three languages.

Endpoints

Caching

None of these responses carries a cache header, because the operator can change them at any moment. A sensible integration caches them for minutes, not days, and refetches on a 404 or a schema it does not recognise. The widget itself reads the venue profile and floor plan once per page load and never caches across loads.

Next steps

• Availability — turn a resource type and a date into bookable slots.
• .NET SDK — the same six reads as typed methods.