API

go~mus REST API. Use-case-driven, with code and concrete examples.

This section is for everyone connecting go~mus with their own systems - websites, apps, backends, reseller platforms. We recommend starting with the Quickstart, followed by Concepts and Authentication. End-to-end use cases live under Scenarios.

Concepts

The go~mus API vocabulary explained in one go - instance, tenancy, master data vs live data, tokens, quotas, reservations, orders.

Read more →

Authentication

How authentication works on the go~mus API - bearer tokens, context awareness, foreign_id pattern, best practices.

Read more →

Tickets

Admission tickets - day tickets, time-slot tickets, combo tickets. How to list, check availability, reserve, and add to an order.

Read more →

Annual Tickets

Annual passes - personalization flow after purchase, token-based access, customer create and personalization update.

Read more →

Events

Events with concrete dates. How to build a calendar, apply filters, and turn a date into a booking.

Read more →

Tours

Guided tours - list, check availability, compute prices, and trigger via request or direct booking.

Read more →

Reservations

Temporary holds for tickets - lifetime, refresh mechanics, what happens on expiry. Why reservations exist only for tickets.

Read more →

Orders

Orders post-create - list, find (also by barcode), finalize in two phases, cancel. The lifecycle resellers and backoffice tools need.

Read more →

Customers

Customer data in go~mus - with foreign_id as the bridge to your CRM. Create, find, update without your system and ours drifting apart.

Read more →

Requests

Inquiries endpoint for group bookings - turn a school-class or group form on your website into a go~mus request.

Read more →

Coupons

Value vouchers - list, detail, shipping-cost link. A product type alongside tickets, events and tours.

Read more →

Museums

Houses on a go~mus instance - list, fetch detail, query opening hours. Reference data for filters and displays.

Read more →

Lookups

Lookup tables for constants - countries, states, dispatch modes, salutations, titles. Cache and refresh once per day.

Read more →

Errors

HTTP status codes, body format and retry strategy - what the go~mus API returns on errors and how to respond to each cleanly.

Read more →

Multi-locale

Multilingual content in one roundtrip - how to fetch DE and EN at the same time, what permission is needed, and how fallbacks work.

Read more →

Best practices

Caching, error handling, pagination, rate limits, logging - what distinguishes a production-ready integration from one you rebuild three times.

Read more →