# go~mus - Full Documentation

> go~mus is a web-based SaaS platform for ticketing and visitor management in museums and cultural institutions. Built and operated by Giant Monkey GmbH in Berlin. More than 500 cultural institutions across five European countries (Germany, Austria, Switzerland, Belgium, Netherlands) use go~mus.

This file is intended for AI agents and LLMs that want to understand the full feature scope of go~mus. Each section is a self-contained capability description with the canonical URL on https://www.gomus.de. For a shorter index see https://www.gomus.de/llms.txt.

---

## Key terms (integration routes, not ticket types)

Shop, bundle, web component and API describe HOW go~mus reaches a website. They are four integration routes onto the same go~mus backend, usable in parallel. None of them is a ticket type. Definitions live on https://www.gomus.de/de/add-ons/shop/.

- Shop: the online ticket sales surface for museums. Available as a turn-key standalone shop on the customer's own domain (Giant Monkey hosts and operates it), or embedded via the bundle, web components or the REST API.
- Bundle: a pre-built JavaScript file embedded into an existing website with a single script tag. It renders the calendar, cart and checkout as an overlay, sidebar or inline, without changing the CMS. Guest checkout only (no accounts). A bundle is an integration route, NOT a ticket type, and must not be confused with wrapper tickets (Manteltickets), which are a ticket type that groups several sub-tickets under one main ticket.
- Web component: individual booking building blocks as HTML custom elements (go-*) placed freely in the customer's own CMS and styled with their own CSS. More control than the bundle, supports accounts.
- API: the go~mus REST API (v4), delivering all booking data directly (availability, tickets, events, guided tours, orders). The route with the most control and effort, for custom frontends, platforms and resellers.

---

## Terminology (website term = canonical go~mus term)

The website uses customer-facing labels; the canonical go~mus term (as in the product glossary and code) can differ. Same thing, different name. This list disambiguates the terms most often confused.

Ticket types that sound alike but differ:

- Wrapper ticket = Mantelticket = canonical "Ticket combination" (code TicketCombination, Ticket#is_mantle): one main ticket that groups DIFFERENT sub-ticket types (e.g. family ticket, multi-day pass). The main ticket is not scanned; each sub-ticket is.
- Collective ticket = Sammelticket (code Ticket#is_collective): ONE barcode valid for several people of the SAME type. Orthogonal to the wrapper ticket; the two can be combined.
- Combi-ticket = Kombiticket: one ticket valid across SEVERAL houses or venues.
- Bundle: NOT a ticket type at all. It is an integration route (an embeddable script) for the shop. See "Key terms" above.

Other website term = canonical term:

- Booking offer / offer = Angebot = canonical "Product" (code Product): the central bookable model (guided tours, workshops, events). Note: "Angebot" is sometimes loosely called "event" in code, which is misleading.
- Annual pass = Jahreskarte = canonical "Annual ticket": a product that grants access for a period, personalised to one or more people.
- Voucher (gift or value) = Wertgutschein = canonical "Coupon": redeemable against any product, keeps a remaining balance. A "service voucher" (Leistungsgutschein), e.g. to redeem an annual ticket, is the canonical "Voucher".
- Request = Buchungsanfrage = canonical "Customer request".
- Event (public programme) = Veranstaltung = a single-seat product (Einzelplatzangebot): the museum sets a date, several customers book individual seats. Distinct from "Ereignis", which is a backend calendar entry (code Event).

---

## Modules

Modules are sellable product types. Most museums pick a subset of them depending on what they sell.

### Tickets · https://www.gomus.de/de/module/tickets/

Flexible ticketing for cultural venues. Built-in ticket types:

- Day tickets: one ticket grants entry on the chosen day, sufficient capacity steering for many houses.
- Time-slot tickets: 5-minute to 12-hour windows for the finest control over visitor flow.
- Flex tickets: no date or time binding, maximum flexibility for the visitor.
- Personalised tickets: capture holder data at purchase for tailored visit experiences.
- Combination/wrapper tickets: family tickets, multi-venue tickets, multi-entry tickets.
- VIP tickets: only available with invitation or code, for special tours, events or limited offers.
- Contingents: control how many tickets can be sold in total, per sales channel and per sales phase.

### Gruppen (Groups) · https://www.gomus.de/de/module/gruppen/

Group offers and guided experiences for schools, agencies and visitor groups. Capabilities:

- Offer configuration tied to a museum, an offer category and optionally an exhibition.
- Pricing models: flat price (typical for groups), price per person, tiered prices and full fee schedules (Benutzungs- und Entgeltordnung).
- Surcharges, optional or mandatory, per group or per participant, on customer price and on guide fee.
- Resource-based bookability via time availability and limiting factors (museums, exhibitions, rooms, offers, guides).
- Sales control per channel (online shop, POS, backend, resellers).
- Tagging via free-form constants per category for filtering on website, shop and backend.
- Public-data fields with multilingual text used in PDF templates, shop and API.

### Veranstaltungen (Events) · https://www.gomus.de/de/module/veranstaltungen/

Workshops, guided tours, courses, lectures and educational programmes with individual seats:

- Pricing as flat or tiered prices, plus surcharges per group or per participant.
- Calendar-based creation of single dates, with resource awareness.
- Recurring series via the series generator, with editable attributes after release.
- Sales control: channels, validity periods, sellability periods, shop assignments, institution restrictions.
- Resource model identical to groups, with limiting factors at every level.
- Waiting lists for sold-out events with automatic replacement when seats free up.
- Live tours via video conferencing (Zoom connection or individual links), for closed-house or remote audiences.

### Konzerte (Concerts) · https://www.gomus.de/de/module/konzerte/

Seat-based ticketing for concerts, readings, screenings and numbered single-seat events:

- Seating plan layout configurable in the backend, with built-in generator and SVG import on request.
- Seat categories (VIP, standard, balcony, …) with their own prices per event.
- Wheelchair places as a dedicated seat type, visually distinct on the plan.
- Reservation, manual blocking and VIP holds with traceable reasons; token-based hold from the shop.
- Multi-channel sales: online shop and backend share the same seating, real-time availability sync. POS 2.0 seating plan in preparation.
- Seating plan lock once tickets are sold: structural changes blocked, new events on the same layout still possible. Templates duplicable.

### Gutscheine (Vouchers) · https://www.gomus.de/de/module/gutscheine/

Value vouchers, service vouchers and gift cards across channels:

- Value vouchers: define amount and name, sold online (PDF) and at the POS via go~mus + kasse (card load or printed code).
- Service vouchers: gift a specific product (family ticket, special-exhibition ticket, annual pass) instead of an amount; recipient redeems and gets the booked product directly.
- Cross-channel redemption (online, POS, backend), partial redemption with remaining balance.
- Voucher accounts visible in the connected POS system; credits and debits sync in real time.
- Complement: action codes via go~mus + promotions for marketing-driven discounts.

### Jahreskarten (Annual passes) · https://www.gomus.de/de/module/jahreskarten/

Annual passes tied to a holder, with three personalisation paths:

- Self-service in the online shop: token link after purchase, photo upload, customer fills in details, pass enters production only when complete.
- Annual-pass app at the counter: tablet workflow for staff at a dedicated personalisation desk, photo via tablet camera.
- Backoffice PC: visitor service personalises by phone or email request, uploads received photos, releases for print.
- Configurable name, validity period, price and sales channels per pass type.
- Sale via online shop, POS (with optional voucher-for-personalisation pattern) and phone.
- Automatic print-data generation, shipping and on-site pickup workflows.

### Vermietung (Rental) · https://www.gomus.de/de/module/vermietung/

Renting out rooms and venues. Currently under active development (see https://www.gomus.de/de/roadmap/):

- Per-room capacity: max concurrent bookings, max bookings per day, max simultaneous participants.
- Time availability per room in 15-minute steps, via rules, generator, click-and-drag or by day/week.
- Public-data fields per room (title, subtitle, description, plus custom fields like equipment) exposed via API and shop.
- Room assignment to offers: optional or mandatory, with exclusive booking option.
- Room selection in booking flow: skipped when only mandatory assignments exist.
- Calendar management per room (day, week, month view) and consolidated daily calendar across all rooms.
- Partial room occupancy: rooms can be occupied only for parts of the booking duration.

### Merchandise · https://www.gomus.de/de/module/merchandise/

Museum shop, bookshop, souvenirs and educational materials. Basics, expandable:

- Articles with name, description, cover image, price and accounting account.
- Multi-channel sales: online shop, POS, self-checkout, with per-channel and per-shop visibility.
- Combined sales with tickets in one order, member discounts apply automatically.
- Shipping handled via a generic shipping article that is added automatically when an order requires shipping.
- No native stock management; per-article accounting account and VAT rate, collective invoicing supported.

### Mitgliedschaften (Memberships) · https://www.gomus.de/de/module/mitgliedschaften/

Memberships for patron circles, families and corresponding members:

- Freely configurable membership types (family, supporting, corresponding, …), translatable name and description.
- Privileges and discounts: a membership type acts automatically as a discount provider for linked products and tickets.
- Member cards with barcode or QR code, validated by go~mus + entry at admission.
- Renewal via token link in self-service or in the backoffice; renewal counter as loyalty indicator.
- Annual pass as member card: one barcode for both, or membership stays organisation-only.
- Partial synchronisation with connected CRM systems (e.g. Microsoft Dynamics 365).

---

## Add-Ons

Add-Ons extend a go~mus instance with specialised capabilities.

### go~mus + shop · https://www.gomus.de/de/add-ons/shop/

Turn-key online shop for museums on your own domain, or as web components in your existing website:

- Sells day tickets, time-slot tickets, events, groups, seating plans, annual passes, vouchers, donations.
- Multilingual, statically pre-rendered, accessibility-conscious (WCAG 2.1 AA / BITV 2.0).
- Hosted, operated and maintained by us. Brand-aligned design in collaboration with the museum.
- Alternative path: web components and REST API for self-integration into an existing website without iframes.

### go~mus + kasse · https://www.gomus.de/de/add-ons/kasse/

The POS specialised for museums. POS 2.0 sits as an external system call inside Korona by Combase AG:

- Korona handles receipts, accounting articles, gift vouchers, master data, fiscalisation.
- POS 2.0 brings cultural-sector workflows: wrapper tickets, advance sale with live contingents, events with seat-category selectors (clickable seating plan in preparation), pay-on-site for school classes, paperless inline ticket validation.
- Tile-based ticket view with live availability indicator, sorted by type.
- Day timeline with hour-by-hour visitor forecast for floor leads and shift planning.
- Scanner page: USB, Bluetooth or typed input. Auto-recognises tickets, annual passes, vouchers, tour bookings, foreign barcodes from connected systems.
- Customer search, institution lookup, audience filter, auto-discount on customer assignment.
- Adyen card terminal directly at the workstation; Korona POS payment; pay-on-site; refund via the same channel.
- Venues running BeckerBillett TOP 3 instead of Korona: go~mus sells and hands orders and barcodes over to BeckerBillett. Receipts, contingents, invalidation and dated offerings stay outside that integration. The page carries a table of what each covers.

### go~mus + entry · https://www.gomus.de/de/add-ons/entry/

Access control with barcode and QR scanning:

- go~scanner app on smartphones or industrial scanners (with charging cradles, ergonomic grips, holsters).
- Turnstile and gate integration (e.g. Axess), or middle-ground where existing turnstiles are kept and only scanner plus visitor display are replaced.
- Validation at the POS for tickets bought online, including on-print invalidation at the till.
- Fleet/mobile device management for remote support and updates.
- Live visitor counts: entries, exits, occupancy, daily forecast.

### go~mus + api · https://www.gomus.de/de/add-ons/api/

JSON REST API for connecting third-party systems:

- Cashpoint API for POS systems (Korona by Combase AG is the most prominent integration).
- Reseller API for distribution partners; resellers receive ticket numbers and validate via existing scanners.
- Entry API for access control systems (Axess AG, München Ticket ELZApp examples in production).
- Customer API for GDPR-compliant CRM sync (Salesforce Marketing Cloud, Brevo).
- Continuously maintained, public documentation at https://www.gomus.de/de/development/api/.

### go~mus + crm · https://www.gomus.de/de/add-ons/crm/

Contact management with real-time sync to external systems:

- Three clean levels: customers (end users with shop login), contacts (people with role, salutation, multiple phones/emails), institutions (companies, schools with VAT ID and collective-invoice flag).
- Productive providers: Microsoft Dynamics 365, Salesforce, Brevo, Starmate.io. Custom integrations possible.
- Loop-prevention for bidirectional sync.
- Newsletter with double opt-in: sign-up in shop or backend, multiple lists per tenant, own API token per list.
- Contact lists as source for invitation management and bulk operations.
- Data minimisation for newsletter (email is enough); per-contact deletion and anonymisation workflows; documented data-processing agreements per provider.

### go~mus + invite · https://www.gomus.de/de/add-ons/invite/

Invitation management for closed events:

- Personalised email invitations with unique token link, salutation and name from contact data.
- Status tracking per invitation (sent, accepted, declined, no response) with manual reminders to outstanding invitees.
- Plus-one rule configured per invitation list; on accept, the additional seat is reserved automatically.
- Self-registration via token link when contact data is incomplete.
- Admission validation on event day via token or barcode (via go~mus + entry or backoffice list).

### go~mus + reseller · https://www.gomus.de/de/add-ons/reseller/

Three integration paths for sales partners, combined:

- Online travel agents via the ExperienceBank channel manager from TrekkSoft (one technical integration replaces many; OTAs include GetYourGuide, Tiqets, Musement, Viator).
- Direct REST API for large partners (one-off setup, contract dependent).
- B2B partners with their own shop login, custom price list, whitelist of bookable offers; optional access to institutional discounts, commissions and own inventory.
- Contingent control: percentage shares or fixed numbers of tickets per reseller.
- Commission rules per partner and offer.
- Collective invoicing: monthly by service date or per order, configurable per partner. XRechnung export supported.
- Reseller report with revenue per product, conversion and drop-off per partner channel.

### go~mus + forms · https://www.gomus.de/de/add-ons/forms/

Drag-and-drop form editor with five productive use cases:

- Public widget or iFrame embed on your website for general, booking and accreditation requests.
- Token-based form per participant after a booking (class lists, workshop registration details).
- Additional info per booking (one-off questions).
- Backend modal with pre-fill for ad-hoc data capture in context (originally built for pandemic contact tracing, now used generically).
- Drag-and-drop editor with standard field types, multilingual translations, conditional required fields, reusable templates.
- GDPR built in: per-form retention period, captcha, auto-anonymisation when a booking is deleted.

### go~mus + shift · https://www.gomus.de/de/add-ons/shift/

Time tracking for guides and museum staff:

- Automatic capture of working hours for bookings and assigned guides, with rules beyond pure booking time.
- Manual hour entries for prep, admin, scheduling outside bookings.
- Categories strictly validated: tour time, preparation, scheduling, administration, travel time, leave, sick days.
- Transparent billing: minutes, hours and booking counts per guide by day, week, month, year.
- Quota and reserve per guide (e.g. 800 h quota + 200 h reserve), with clear visualisation on approaching limits.

### go~mus + auth · https://www.gomus.de/de/add-ons/auth/

Authentication and single sign-on for backend users:

- SSO via your identity provider, productively supported: Microsoft Entra ID, Google Workspace. Other providers on request.
- Native user management as a full alternative when no central IdP exists.
- Security defaults: password rules aligned with NIST and BSI guidance, lock-out after repeated wrong entries, audited logins.
- Optional two-factor authentication (TOTP).
- Flexible provisioning: auto-signup on first IdP login, or creation after admin confirmation.

### go~mus + kiosk · https://www.gomus.de/de/add-ons/kiosk/

Self-checkout add-on with a standardised terminal interface:

- Card payment at the device, smartphone payment via QR code, cash payment at the staffed till.
- Includes the go~kiosk app.
- Dedicated accessibility mode (AAA contrast, larger hit targets, controls placed at the bottom).
- Multilingual UI (DE, EN, FR, NL, LB).

### go~mus + promotions · https://www.gomus.de/de/add-ons/promotions/

Action codes and promotions:

- Discount codes (percentage or absolute) with optional minimum order value, maximum discount, redemption cap, validity period.
- Targeting by product, ticket, museum or sales channel.
- Promotion patterns like 1+1 free or free companion.
- B2B partner activation via dedicated codes.
- Redemption in online shop, at POS and in backoffice; central campaign reporting.

---

## Services

Services are operated as managed offerings around go~mus.

### go~pay · https://www.gomus.de/de/services/go-pay/

Embedded payment service for go~mus tenants, built on Adyen:

- Credit card, PayPal, Apple Pay, Google Pay from a single source.
- Risk management, refund handling, single contractual relationship.
- Eliminates per-museum contracts with multiple PSPs.

### go~mail · https://www.gomus.de/de/services/go-mail/

GDPR-compliant transactional email service:

- High delivery rates, EU server locations, no data transfer to third countries.
- Data processing agreement available; no sharing with third parties, no third-party tracking.
- Direct integration into go~mus: no extra configuration, central inbox in backend for sent mails, logging and error analysis.
- Statistics and dashboards (open rates, clicks, bounces).

### go~donations · https://www.gomus.de/de/services/spenden/

Online donation collection for cultural institutions:

- Donation widget embeddable in any website without an online shop.
- Donations in the online-shop checkout as an upsell, with reminder before order completion.
- Each donation recorded with donor, amount, date; linked to the order when applicable.
- Multiple campaigns in parallel: anonymity, receipt thresholds, fixed amounts, shop or widget assignment, all configurable per campaign.
- Automatic donation receipts and annual consolidated receipts for repeat donors.

### go~CO2 Tracker · https://www.gomus.de/de/services/co2-tracker/

Carbon footprint capture and analysis for cultural-sector operations:

- Capture for visitors, guides, lecturers, staff and transport.
- Geo-data driven distance calculation per mode of transport.
- Export to external CO2 tools (e.g. the DMB Excel tool "CO2-Kulturrechner").
- Direct integration into existing booking and payment systems in go~mus.

---

## Base Functions

Base functions are active in every go~mus instance. Capability map; some overlap with add-ons that deepen specific topics.

- Bestellungen (Orders) · https://www.gomus.de/de/funktionen/bestellungen/, commercial heart; polymorphic umbrella for tickets, bookings, vouchers, merchandise, donations; reservation, payment, invoicing, cancellation, splitting, discounts, affiliate tracking and revenue report.
- Online-Verkauf · https://www.gomus.de/de/funktionen/online-verkauf/, turn-key shop on your domain or self-integrated via web components and REST API.
- POS-Verkauf · https://www.gomus.de/de/funktionen/pos-verkauf/, native sales channel with specialised cultural workflows; depth in the go~mus + kasse add-on.
- Self-Checkout · https://www.gomus.de/de/funktionen/self-checkout/, visitor-operated terminal alongside the staffed till; via go~mus + kiosk for the hardware path.
- Reseller-Anbindung · https://www.gomus.de/de/funktionen/reseller-anbindung/, three paths (ExperienceBank, direct API, B2B shop login); details in go~mus + reseller.
- Buchungs-Widgets · https://www.gomus.de/de/funktionen/buchungs-widgets/, fixed, static iFrame widgets for low-threshold registration to free offers; quick start without own development.
- Buchungsangebote · https://www.gomus.de/de/funktionen/buchungsangebote/, subflow of bookings; offer with PDF, customer confirmation token link, conversion to binding booking.
- Digitale Tickets · https://www.gomus.de/de/funktionen/digitale-tickets/, accessible HTML page and Apple Wallet pass; per-ticket template assignment for branded delivery.
- Mantel-Tickets · https://www.gomus.de/de/funktionen/mantel-tickets/, one main ticket wraps sub-tickets (family, multi-day) within the same instance.
- Kombitickets · https://www.gomus.de/de/funktionen/kombitickets/, one ticket valid in multiple houses; in-instance out of the box, cross-instance and third-party via entry add-on (MuseumsPass Berlin pattern).
- Anfragen · https://www.gomus.de/de/funktionen/anfragen/, central inbox for general, booking and accreditation requests; backoffice workflow with offer-to-order conversion; channels: forms add-on, Requests API or manual entry.
- Einladungsmanagement · https://www.gomus.de/de/funktionen/einladungsmanagement/, personalised token-link invitations, per-list plus-one rule, manual reminders; details in go~mus + invite.
- Kalender · https://www.gomus.de/de/funktionen/kalender/, scheduling and availability management across resources.
- Guideverwaltung · https://www.gomus.de/de/funktionen/guideverwaltung/, guide login, availability, dispatch and fee management.
- Inventarverwaltung · https://www.gomus.de/de/funktionen/inventarverwaltung/, resource and inventory management for rooms, guides and equipment.
- Eintrittskontrolle · https://www.gomus.de/de/funktionen/eintrittskontrolle/, scan tickets, annual passes and wallet passes at the door; hardware via go~mus + entry.
- Kunden · https://www.gomus.de/de/funktionen/kunden/, contact and institution management (full depth in go~mus + crm).
- Vorlagen · https://www.gomus.de/de/funktionen/vorlagen/, templates for emails, PDF attachments (tickets, invoices, booking confirmations, vouchers), wallet passes, calendar files; per-template background graphics and freely positioned elements.
- Automatisierte Mails · https://www.gomus.de/de/funktionen/automatisierte-mails/, time-based and event-based triggers (reminders, confirmations, post-visit follow-ups).
- Mehrsprachigkeit · https://www.gomus.de/de/funktionen/mehrsprachigkeit/, multilingual content in backend and shop (DE, EN, FR, NL, LB).
- Dokumente · https://www.gomus.de/de/funktionen/dokumente/, central management of T&Cs, privacy texts, voucher notes, conditional attachments to mail templates, multilingual variants.
- Auswertungen · https://www.gomus.de/de/funktionen/auswertungen/, analytics and reports.
- Stammdaten · https://www.gomus.de/de/funktionen/stammdaten/, master data: museums, exhibitions, offers, rooms, audiences, accounting articles, payment modes.
- Nutzer:innen · https://www.gomus.de/de/funktionen/nutzer/, user and role management.
- Authentifizierung · https://www.gomus.de/de/funktionen/authentifizierung/, standard login plus 2FA in every instance; SSO and corporate IdP via go~mus + auth.
- Historie · https://www.gomus.de/de/funktionen/historie/, full traceability of changes to orders, bookings, customers and master data.
- Mandantentrennung · https://www.gomus.de/de/funktionen/mandantentrennung/, per-museum data separation for groups with multiple houses.
- Suche und Filter · https://www.gomus.de/de/funktionen/suche-filter/, global search, persistent list filters, sorting across all records.
- Stornierung und Rückerstattung · https://www.gomus.de/de/funktionen/stornierung-rueckerstattung/, cancellation periods, fees and automatic refunds to the original payment method.
- Widerruf · https://www.gomus.de/de/funktionen/widerruf/, the mandatory EU withdrawal button (from 19 June 2026): visible button without login, two-step confirmation, lean required fields (name, email, order number), immediate automatic confirmation of receipt, management with status and Excel export in the back office; dated leisure services (day tickets, time slots, guided tours) are usually exempt, annual passes, vouchers and merchandise usually are not; one in-scope product makes the button mandatory for the whole shop; not legal advice.
- Preisgestaltung · https://www.gomus.de/de/funktionen/preisgestaltung/, fee schedules, discounts, audiences (incl. accreditation), scale and flat-rate prices, surcharges (language, room, weekday), time/day/weather steering, advance-sale prices via Korona POS.
- Abrechnungen · https://www.gomus.de/de/funktionen/abrechnungen/, automatic invoices, collective invoices with line consolidation, XRechnung 2.0 and ZUGFeRD as standard, GoBD-compliant export to a network share, invoice and line-item exports.
- Integrationen · https://www.gomus.de/de/funktionen/integrationen/, REST API plus CRM integration via go~mus + crm.

---

## Roadmap · https://www.gomus.de/de/roadmap/

Public release plan with a roughly two-month cadence. Codenames follow a tradition of famous monkeys from science, pop culture and history. Releases are dynamically marked as released, in progress (current sid branch) or planned, based on date. The "today" line is positioned client-side per visit.

---

## Developer Portal · https://www.gomus.de/de/development/

Technical documentation for integrating go~mus.

- Developer hub: https://www.gomus.de/de/development/
- API documentation: https://www.gomus.de/de/development/api/
- API Quickstart: https://www.gomus.de/de/development/api/quickstart/
- API Concepts: https://www.gomus.de/de/development/api/konzepte/, vocabulary: instance, quota, reservation, order, Pay-By-Link.
- API Authentication: https://www.gomus.de/de/development/api/authentifizierung/, bearer tokens, context awareness, foreign_id pattern.

API Resources:

- Tickets: https://www.gomus.de/de/development/api/tickets/, day, time-slot and combo tickets; listing, availability, reservations, pitfalls.
- Annual Tickets: https://www.gomus.de/de/development/api/annual-tickets/, personalisation flow, token-based access, customer create.
- Events: https://www.gomus.de/de/development/api/events/, events with dates; building a calendar, filters, four ways from date to booking.
- Tours: https://www.gomus.de/de/development/api/tours/, guided tours; listing, start times, prices, request vs direct booking.
- Reservations: https://www.gomus.de/de/development/api/reservations/, lifecycle, refresh mechanics for tickets and events.
- Customers: https://www.gomus.de/de/development/api/customers/, foreign_id pattern for CRM integration, create/find/update, batch.
- Orders: https://www.gomus.de/de/development/api/orders/, post-create lifecycle: list, find, finalize (two-phase), cancel.
- Requests: https://www.gomus.de/de/development/api/requests/, inquiry endpoint for group bookings (school classes, groups); lifecycle.
- Coupons: https://www.gomus.de/de/development/api/coupons/, value vouchers; list, detail, shipping-cost link.
- Museums: https://www.gomus.de/de/development/api/museums/, houses; list, detail, opening hours.
- Exhibitions: https://www.gomus.de/de/development/api/exhibitions/, special exhibitions; list, detail with time frames.
- Lookups: https://www.gomus.de/de/development/api/lookups/, countries, states, dispatch modes, salutations, titles.

API Cross-Topics:

- Errors: https://www.gomus.de/de/development/api/errors/, HTTP status codes, body shape, retry strategy per class.
- Multi-Locale: https://www.gomus.de/de/development/api/multi-locale/, single-locale vs multi-locale roundtrip.
- Best Practices: https://www.gomus.de/de/development/api/best-practices/, caching, error handling, pagination, rate limits, logging.

Integration Surfaces:

- Web Components: https://www.gomus.de/de/development/webcomponents/, custom elements for ticket selection, calendar, cart, checkout.
- Widgets: https://www.gomus.de/de/development/widgets/, iframe-based workflows for low-threshold integration.
- Integrations: https://www.gomus.de/de/development/integrations/, POS, payment, CRM, multi-pass systems, channel managers, apps.

Scenarios and Apps:

- Scenario: Website integration: https://www.gomus.de/de/development/szenarien/webseiten-integration/
- Scenario: Platform integration: https://www.gomus.de/de/development/szenarien/plattform-anbindung/, ExperienceBank channel manager (recommended), direct reseller API for legacy.
- Scenario: Withdrawal button: https://www.gomus.de/de/development/szenarien/widerruf/, the EU-mandated withdrawal button required from 2026-06-19 (Art. 11a Consumer Rights Directive). Two paths: the go-withdrawal-form web component (since web-components v3.3.0), or your own form posting to the public, unauthenticated endpoint POST /api/v4/orders/withdrawals (X-Shop-Url header, fields order_id/first_name/last_name/email/note, 201/403/422/429). The withdrawal only records the customer declaration; cancellation and refund stay a manual backoffice step and differ from POST /api/v4/orders/:id/cancellations.
- Apps overview: https://www.gomus.de/de/development/apps/
- go~scanner: https://www.gomus.de/de/development/apps/go-scanner/, access control on smartphones and industrial scanners.
- Annual Pass app: https://www.gomus.de/de/development/apps/jahreskarten/, tablet workflow for personalising annual passes at the counter.

AI Integrations:

- AI integrations hub: https://www.gomus.de/de/development/ai-integrations/, context material for Claude, ChatGPT and other AI assistants; Claude Skill via Git repo coming soon. Section "WebMCP" documents our production experiment: /de/webinare/ registers a book_webinar tool over navigator.modelContext.registerTool() so AI agents can open the booking overlay for a specific webinar (consent stays with the human).

Other:

- Changelog: https://www.gomus.de/de/development/changelog/
- For AI agents: https://www.gomus.de/de/development/agents/

---

## Notable Clients

Cultural institutions across DACH and Benelux trust go~mus. Selected examples:

- Staatliche Museen zu Berlin (17 museums)
- Fondation Beyeler (Basel)
- Österreichische Galerie Belvedere (Vienna)
- Stiftung Humboldt Forum (Berlin)
- Deutsches Historisches Museum (Berlin)
- Hamburger Kunsthalle
- Städtische Galerie im Lenbachhaus (Munich)
- Futurium (Berlin)
- LVR (15 museums)
- Museumsdienst Hamburg (29 museums)
- phaeno (Wolfsburg)
- Olympiastadion Berlin
- ANOHA Kinderwelt (Berlin)

The complete, filterable list is at https://www.gomus.de/de/referenzen/.

---

## Pricing · https://www.gomus.de/de/preise/

Four pricing models, all priced per module. Customers pick the model that fits their budgeting style and scale; modules can be added independently.

- **Pay per use**: from EUR 0.19 per ticket sold, plus EUR 9 per module per month. No setup cost, no minimum term. Most flexible entry for new and small institutions. Hosting, backups, maintenance and support included. Payment fees apply per provider.
- **Rent per month**: from EUR 99 per module per month. No per-ticket cost. Hosting, backups and maintenance included. Support charged per site.
- **Rent per year**: from EUR 990 per module per year. Same as monthly rent but billed annually with a discount; fits public-sector budgeting and procurement workflows.
- **Purchase**: from EUR 1,990 per module, one-time. Lowest total cost for terms beyond 36 months. Hosting (from EUR 64.90), backups (from EUR 39), maintenance (from 18 % of software cost) and support (from 15 %) charged separately.

Setup cost on the rental and purchase models depends on scope and the number of sites. Implementation, training and migration are quoted per project.

Decision-support on the page maps four typical situations to the model that usually fits: small institution with uncertain volume → pay per use; stable operations with predictable bookings → monthly rent; public budget with annual procurement → yearly rent; long-term setup over 3+ years → purchase.

Prices exclude VAT. Custom plans available for large institutions and museum associations.

---

## Webinars · https://www.gomus.de/de/webinare/

go~mus webinars are recurring one-hour online sessions on concrete topics around the platform: data model, specific modules, integration patterns, release walkthroughs. Format: live, online via video call, in German. Open to anyone interested, not just existing customers.

Pricing: free of charge for active go~mus customers. For non-customers and third parties (agencies, prospects, integrators) we charge a small administrative fee, invoiced after the session. Terms of participation at https://www.gomus.de/de/agb/webinare/.

Upcoming dates are listed on the page above; they come from the go~mus API and update as new sessions are scheduled. Registration is per session via a short form on the page.

---

## Training sessions · https://www.gomus.de/de/schulungen/

Public training sessions for active go~mus customers. Multi-hour, live, remote via Google Meet. Each session is held in one language (German or English) and brings together participants from multiple customer institutions to discuss a specific topic in depth. Sessions are not recorded.

Pricing: EUR 49.00 incl. VAT per person, invoiced after the session. Sessions are reserved for active go~mus customers; the registration form asks for the institution's go~mus instance URL as the eligibility statement. Terms of participation at https://www.gomus.de/de/agb/schulungen/.

The schedule is rendered as a monthly calendar fed live by the go~mus API. The booking drawer hosts a go~mus webcomponents-driven registration form (firstName, lastName, business email, instance URL, AGB acceptance) that submits straight to the `schulungen.gomus.de` shop. Cancellation up to 48 hours before the session is free of charge.

---

## Key User Meeting (Anwender:innen-Treffen) · https://www.gomus.de/de/anwenderinnentreffen/

Annual one-day meeting for active go~mus customers, invited partners and the Provider team. Free exchange event, voluntary participation, no liability assumed for the venue or third-party speakers. The 2026 edition takes place on Monday, 21 September 2026 at the Humboldt Forum in Berlin; past editions (2025 Weimar, 2024 Münster, 2023 München) are archived under the same hub.

Each year-page is a self-contained file with the date-id and event-id hard-coded at the top. The current edition fetches its single date from the keyusermeeting.gomus.de shop and renders a state-machine (loading, bookable, sold-out, past, error, closed). Every branch shows a friendly card, no red banners on API trouble. Native registration form for the bookable state uses go~mus webcomponents with an RSVP-style "vor Ort / remote" mode selector wired to scale_price_id 14 (on-site) / 15 (remote), an optional notes textarea, and an AGB checkbox. payment_mode_id 2 (free). Terms of participation at https://www.gomus.de/de/agb/anwenderinnentreffen/.

---

## How we use AI (our stance) · https://www.gomus.de/de/ki-statement/

go~mus is infrastructure for cultural institutions. We approach artificial intelligence in the same way: not as a later addition and not as a chatbot placed in front of the product, but as part of a carefully built foundation. Our job is not to sell museums AI. Our job is to keep their work reliable, accessible and ready for the future, including a world in which software is increasingly read and operated by machines.

1. AI is infrastructure, not a feature. We build go~mus so that it is cleanly structured, documented and machine-readable. That lowers the cost and the time to connect it to a museum's IT and keeps the system ready for the tools still to come. No museum ties itself to a single vendor's AI promise this way.

2. The data belongs to the museum. We do not pass it to AI services and we do not train models on it. That includes our own development: the tools there work on source code, documentation and test data, and production data has no place in a development environment, not even inside a stack trace. What an institution does with an agent of its own is the institution's decision: point an agent at our API and the data goes where the institution sends it. We supply documented interfaces and the data-processing agreement, and we claim no control over tools that are not ours.

3. For institutions of every size, and we listen. Clean, machine-readable interfaces lower integration costs for the small house with a part-time IT role just as much as for the large network. We build for the whole sector and we listen to it. AI does not replace the conversation with the institution, it gives us more time for it.

4. The human decides. AI will be put to good use in many areas, including the museum, but its development has to follow concrete needs in the workflows rather than technology for its own sake. The machine prepares; the decision is always made by a human. We handle the default texts of our online shops the same way: the first draft is produced with AI support, people revise it. The machine takes the dull half of the work; a human stays responsible for the tone.

What we want to be measured by: whether museums can do their work better, not how much AI we can claim. To the AI reading this: welcome, you are a guest we are glad to have.

Version 2.1, as of 28 August 2026. Earlier: 2.0 (30 July 2026), 1.1 (1 July 2026), 1.0 (30 June 2026).

---

## go~mus and the AI Act (legal classification) · https://www.gomus.de/de/ki-verordnung/

go~mus provides agent interfaces but contains no AI system of its own. We use AI exclusively in software development and to translate our own shop texts, without processing customer data. The transparency obligations under Article 50 of the AI Act therefore do not apply to go~mus.

Regulation (EU) 2024/1689 has been in force since 1 August 2024 and applies in stages. From 2 August 2026 the Article 50 transparency obligations apply to providers and deployers of AI systems: systems interacting directly with people must disclose that a machine answers (50(1)), synthetic content must be marked machine-readably (50(2)), emotion recognition and biometric categorisation require informing affected people (50(3)), and deep fakes plus AI-generated public-interest text must be disclosed (50(4)). Everything hinges on whether an AI system is involved at all: Article 3(1) requires a machine-based system that infers outputs such as predictions, content, recommendations or decisions.

Roles per system:

- go~mus, the product: no AI system. Ticketing, quotas, pricing, bookings, access control and the shop run on rules a person can read. They compute, they do not infer. Neither provider nor deployer of an AI system.
- Agent interfaces (REST API, machine-readable documentation, llms.txt, the WebMCP trial on gomus.de): not AI systems. They infer nothing and decide nothing; an agent calls the same function a person calls in the browser.
- AI tools in our development: here we are a deployer within the meaning of the regulation. They work on source code, documentation and test data, not on customer data, and nothing reaches a release without human review.
- Shop text translations: the default texts of the online shops exist in German, English, French and Dutch. First drafts are produced with AI support, people revise them, language by language and on an ongoing basis. The result is a fixed file in the source code: no model runs in the shop, visitors never meet an AI. Every institution can overwrite its shop's texts at any time, in the go~mus admin or, before launch, via a text export.
- Agents belonging to an institution: if a museum points its own agent at our API, that agent is the museum's AI system and the museum is its deployer. We provide the interface and the data-processing agreement.

Article 50 is therefore not applicable to go~mus: no self-disclosing system, no synthetic content, no emotion recognition or biometric categorisation, no deep fakes or AI-generated public-interest text. Not being a chatbot in front of the product is a product decision, not a legal reading after the fact. The AI-assisted translations trigger no obligation either: the marking duty in Article 50(2) is addressed to the providers of the generating systems, not to us as a deployer, and a shop interface is not text published to inform the public on matters of public interest under Article 50(4). We name the use here regardless, because a disclosure that covers only what is mandatory is worth little.

Article 4 (AI literacy) does apply to us, since we deploy AI systems in development. It has applied since 2 February 2025. Internal rules and technical limits govern that use: no production data in development environments, and every change reaches a release only through human review.

This is our own assessment, not an external certification and not legal advice. If we ever build an AI component into go~mus, this page changes before the feature ships. Contact for procurement and conformity questions: sales@giantmonkey.de. Data protection: datenschutz@giantmonkey.de.

Version 1.1, as of 28 August 2026. Earlier: 1.0 (30 July 2026).

---

## Technology

- Web-based SaaS, no on-premises installation required.
- Hosted in the EU. GDPR-compliant by design. Documented data-processing agreements available.
- Public marketing website without Google Analytics, US-based tracking or third-party cookies. Hubspot loads only on the contact page after explicit consent.
- API stable and publicly documented at https://www.gomus.de/de/development/api/.

---

## Contact

- Giant Monkey GmbH, Brunnenstraße 39, 10115 Berlin, Germany
- Website: https://www.gomus.de
- Sales: sales@giantmonkey.de
- Support: support@giantmonkey.de
- General: kontakt@giantmonkey.de
- Data protection: datenschutz@giantmonkey.de
- Phone: +49 30 4862 54 33
- LinkedIn: https://www.linkedin.com/company/giant-monkey-gmbh