EntityType
The five entity types — EVENEMENT, LOCATIE, EVENTGROUP, ROUTE, VENUE — and when to use each
Every TRCItem has an entitytype field that determines what kind of object it represents. The API has five entity types:
| Value | Meaning | Example |
|---|---|---|
EVENEMENT | An event — something that happens at a time and place | Concert, exhibition, market |
LOCATIE | A location — a geographical point of interest | Museum, park, monument |
EVENTGROUP | A group of related events | A festival containing multiple sub-events |
ROUTE | A geographical path with waypoints | Walking trail, cycling route |
VENUE | A business-oriented location | Restaurant, hotel, conference center |
EVENEMENT
Events are the most common and feature-rich entity type. They carry priceElements, promotions, performers, and support child/parent links for event series.
Events are accessed via GET /events and are expected to have a Calendar that describes when they take place.
LOCATIE
Locations are geographical points of interest. They describe where something is, not when it happens. A location might have a Calendar (e.g., opening hours for a museum), but it is not required.
Locations are accessed via GET /locations.
VENUE
Venues are physical locations suitable for hosting larger B2B events — congress centres, conference hotels, business event spaces. They are not a generic "businesses" bucket: they specifically describe places where multi-room corporate events, congresses, and similar gatherings are held.
Because venues serve B2B event planners, they carry properties planners care about: total capacity, minimum / maximum group size, number of meeting rooms, total square metres, and similar quantitative attributes.
Venues also support rooms: individual meeting spaces within the venue, each with its own surface area and capacity in different setups (theater / U-shape / cabaret / reception / seated dinner). Rooms are modelled as subItemGroups inside trcitemRelation — see the Location vs Venue page for the full structure.
Venues are accessed via GET /venues and always have entitytype: "VENUE". See Location vs Venue for guidance on which to use.
EVENTGROUP
Event groups are containers for related events. A festival might be an EVENTGROUP with child links to its individual EVENEMENT entries. The group itself can carry its own Calendar, location, and metadata.
ROUTE
Routes are geographical paths. They carry a routeInfo object with the route type (walking, cycling, driving), distance, duration, difficulty, surface type, waypoint coordinates, and points of interest along the path.
Routes are accessed via GET /routes.
See the API Reference for the full entitytype enum definition.