An exhibition in go~mus is a special exhibition - the curated show with a runtime to which tickets, events and tours can be attached. On most resource listings, exhibition_id appears as a filter; this resource provides the values and the detail data for public display.
Full endpoint and schema reference: Swagger.
Endpoints at a glance
| Endpoint | What |
|---|---|
GET /api/v4/exhibitions | List all special exhibitions |
GET /api/v4/exhibitions/:id | Detail with time frames and content |
Anatomy of an exhibition object
id- stable, use it inby_exhibition_ids[]filtersmuseum_id- which house the exhibition belongs toforeign_id- optional, your external id (e.g. CMS article slug)title,sub_title,description- translatable via?locale=defeatured- boolean, highlight flagpicture- URL of the main imagecontent- long-text HTML for detail pagestime_frames- array of{ from, to }pairs with the runtime of the exhibition. An exhibition can have multiple disjoint frames (pause, extension)
Full field list: Swagger.
Common tasks
List special exhibitions
curl "https://demo.gomus.de/api/v4/exhibitions?by_museum_ids[]=20&by_featured=true&locale=de"
Filters:
by_museum_ids[]- exhibitions of one house onlyby_featured=true- highlights only
Detail
curl "https://demo.gomus.de/api/v4/exhibitions/2057?locale=de"
Returns description, content and time_frames - enough for a complete detail page with runtime display.
Relationships
Exhibition
├── Museum ............. which house
├── Tickets ............ via exhibition_ids
├── Events ............. via exhibition_id
└── Tours .............. via exhibition_id
Pitfalls
exhibition_id = -1as a filter is a special form. Inby_exhibition_ids[],-1means "results without an exhibition link" - useful for collection tickets or collection events not tied to a running special exhibition.time_framescan have multiple entries. An exhibition with a pause and an extension has two frames. To show "currently running", check all frames, not just the first.foreign_idis also a URL lookup.GET /api/v4/exhibitions/:idtries the numeric id first, then falls back toforeign_id. If your CMS ids happen to look like numeric go~mus ids (12345), confusion is possible - prefixed foreign ids (HKW-2026,LWL-WI23) are more robust.