Scenarios

Use-case stories for the most common tasks across all API resources - architecture sketch, flow, links to the resource pages.

Scenarios are top-level walkthroughs for the most common integration tasks: website connection (event calendar, direct booking, group requests, ticket shop) and reseller integration via the ExperienceBank channel manager. Each scenario covers an architecture-variant comparison, a flow sketch, scenario-specific pitfalls and links to the relevant API resources.

Website integration

Connect a museum website to go~mus - event calendar, direct registration, group requests, ticket shop. Architecture sketch, flow, links to the resources.

Read more →

Embed the bundle

Bring the go~mus booking bundle onto an existing website with a single script tag, as an overlay or inline. What you need, how it looks, and what your delivered docs cover.

Read more →

Platform integration

Connect go~mus to external platforms - reseller marketplaces via ExperienceBank, museum-operated booking portals and apps directly via the API.

Read more →

Withdrawal button

The mandatory withdrawal button from 19 June 2026, across all four routes: standalone shop (automatic), bundle, web components, API. Triggers, fields, error codes, and how it differs from cancellation.

Read more →

Shop web analytics (GTM)

Your own analytics and marketing tags in the go~mus shop, self-managed via Google Tag Manager. Three-layer setup, ecommerce events including the visit date, consent as a load gate, activation checklist.

Read more →