Museums

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

A museum resource in go~mus represents a house or a location. An instance hosts either a single museum or several houses of an association. On almost every resource listing, museum_id shows up as a filter - the museums resource provides the values plus detail data and opening hours for public display.

Full endpoint and schema reference: Swagger.

Endpoints at a glance

EndpointWhat
GET /api/v4/museumsList all houses on this instance
GET /api/v4/museums/:idDetail with description and content
GET /api/v4/museums/:id/opening_hoursOpening hours for a concrete date
GET /api/v4/museums/:id/schedulesDay plan including scheduled tours/events (if the schedules feature is active)

Anatomy of a museum object

  • id - stable, use it in by_museum_ids[] filters everywhere
  • title, sub_title, description - translatable via ?locale=de
  • picture - URL of the main image (hero, list view)
  • content - long-text HTML for detail pages
  • created_at, updated_at

Full field list: Swagger.

Common tasks

List houses

curl "https://demo.gomus.de/api/v4/museums?locale=de"

Sorted by shop_order (the order configured by the house), not alphabetically. Useful for frontends that want display order tied to the instance's configuration.

Museum detail

curl "https://demo.gomus.de/api/v4/museums/20?locale=de"

Returns description plus content for a full "about the house" page.

Query opening hours

curl "https://demo.gomus.de/api/v4/museums/20/opening_hours?date=2026-05-15"

Parameters:

  • date - ISO date (default: today)
  • quota_ids[] - optional: compute over specific quotas only (e.g. specific entrance zones)

The response contains the effective opening-hour slots for that day - taking special closures, holidays and quota configurations into account.

Relationships

Museum
 ├── Tickets ........... via museum_ids
 ├── Tours ............. via museum_id
 ├── Events ............ via museum_id
 ├── Exhibitions ....... via museum_id
 ├── Quotas ............ linked through tickets/events
 └── Schedule (optional) day plan if the feature is active

Pitfalls

  • Sort follows shop_order, not title. For alphabetical order, sort client-side - the server respects the configured order from the go~mus back office.
  • opening_hours is date-dependent. Special days (closure, extended hours) only show up for the queried date. Do not cache today's value and reuse it for tomorrow.
  • Schedules endpoint needs a feature flag. If the instance has no schedules feature, the endpoint returns an error. Clarify with the operator whether the feature is on.