Appearance
Get a single event based on filters (storefront callers see active events only)
GET
/rest/v1/event/event/item
Storefront callers — guest (no token) and customer — match only against active events: filter[active] is server-forced to 1 for them, so a supplied value is ignored rather than combined. This is the route a storefront uses to resolve an event by slug, so it — not the id-addressed show() — sets what an inactive event looks like to a visitor. Backend callers may filter freely.
Parameters
Query Parameters
filter[id]
Filter by event IDs
Type
string
filter[active]
Filter by active status. Backend callers only — for storefront (guest/customer) callers this value is server-forced to 1 and any supplied value is ignored.
Type
string
filter[datetimeStartGte]
INCLUSIVE lower bound on the event start (events.datetime_start >= value). Same semantics as on GET /rest/event/event, including the NULL exclusion.
Type
string
Format
"date-time"filter[datetimeStartLt]
EXCLUSIVE upper bound on the event start (events.datetime_start < value). Same semantics as on GET /rest/event/event.
Type
string
Format
"date-time"filter[datetimeEndGte]
INCLUSIVE lower bound on the event end (events.datetime_end >= value). Same semantics as on GET /rest/event/event.
Type
string
Format
"date-time"filter[datetimeEndLt]
EXCLUSIVE upper bound on the event end (events.datetime_end < value). Same semantics as on GET /rest/event/event.
Type
string
Format
"date-time"filter[slug.el]
Filter by event slug (Greek)
Type
string
filter[slug.en]
Filter by event slug (English)
Type
string
with
With relations
Type
string
Responses
Successful operation
application/json
JSON
"string"