Manages the relationship between EventGroups and Events.
You must have the registration
or scheduling
ConventionPrivilege to access this.
Event Group Events are accessed via /api/eventgroupevent
.
See "Object Properties" in Introduction for basic shared properties.
Complete details in EventGroupEventProperties.
See "Related Objects" in Introduction for how to use them.
The Convention this event group event belongs to.
The Event this event group event belongs to.
The EventGroup this event group event belongs to.
See "Includes" in Introduction for how to use them.
Returns whether the associated Event has enough seats for all BadgeTypes unreserved_quantity
associated via the Event's EventGroups.
1
means true,
0
means false.
For Events not in an EventGroup this will likely still return 1
(true).
Returns three flag values (1
means true,
0
means false):
Whether the Event is in more than one EventGroup.
Whether the Event is in more than one EventGroup that has its tickets_autoincluded
set to true.
Whether any EventGroup the Event is in has its tickets_autoincluded
set to true.
The services used to fetch and manipulate event group events.
This section describes basic searchability of Event Group Events, which is now available across several main endpoints.
To request Event Group Events,
a user must make a request via an endpoint for a parent object.
The parent objects for which this consolidated search behavior is valid are: Convention,
Event,
and EventGroup.
Departures/differences from basic behavior will be discussed in the documentation for the specific parent=>eventgroupevent relationship.
(The old endpoint GET /api/eventgroupevent
,
which allowed searching across conventions and users,
has been made admin-only.)
Returns:
{ "paging" : {...}, "items" : [ { "id" : "xxx", "event_id" : "xxx", "eventgroup_id" : "xxx", ... }, ... ] }
Pass a string query
to search for a partial match in specifically allowed text fields.
(can be searched only by specifying field with query_field=event.name
; see options below)
(can be searched only by specifying field with query_field=eventgroup.name
; see options below)
Event Group Event query
searches must include the query_field
parameter, set to one of the fields above.
POST /api/eventgroupevent
Returns the same as a normal read.
GET /api/eventgroupevent/xxx
Returns:
{ "id" : "xxx", "event_id" : "xxx", ... }
PUT /api/eventgroupevent/xxx
Returns the same as a normal read.
DELETE /api/eventgroupevent/xxx
Returns:
{ "success" : 1 }
Hey! The above document had some coding errors, which are explained below:
You forgot a '=back' before '=head3'