Retrieve Events

Only include events that have the given text in the event Name. For example: If you want to retrieve all the events that have the word “International” in the event Name field, pass in the value “International” for the filter_by_event_name_contains_text parameter. Note: this text search is not case-sensitive.

Only include events that have their start date greater than or equal to the value passed in for this filter parameter. Use this date format: YYYY-MM-DD

Only include events that have their start date smaller than or equal to the value passed in for this filter parameter. Use this date format: YYYY-MM-DD

Only include events that have their end date greater than or equal to the value passed in for this filter parameter. Use this date format: YYYY-MM-DD

Only include events that have their end date smaller than or equal to the value passed in for this filter parameter. Use this date format: YYYY-MM-DD

Only include events that have their participation_type_id equal to the value passed in for this filter parameter. To get a list of available event Participation Type Ids in your workspace, refer to this endpoint: /v1/references/event_participation_types

Only include events that have their format_id equal to the value passed in for this filter parameter. The following integer values are accepted (1 for In-Person, 2 for Virtual, 3 for Hybrid)

Only include events that have their star rating equal to the value passed in for this filter parameter. The following integer values are accepted: 0, 1, 2, 3

Only include events that have this tag. For example, you can use this filter to get all the events that have the tag “International”. Note: You can only pass in one tag to filter based on.

Only include events that have their integration_metadata_field_1 property equal to the value you pass in for this parameter. Note: An event's integration_metadata_field_1 property is an integration-specific text field only accessible via the ExhibitDay API. This field is typically used to store metadata or information about a particular event (e.g., the "external id" of the event from another system you're integrating with).

Only include events that have their integration_metadata_field_2 property equal to the value you pass in for this parameter. Note: An event's integration_metadata_field_2 property is an integration-specific text field only accessible via the ExhibitDay API. This field is typically used to store metadata or information about a particular event (e.g., the "external id" of the event from another system you're integrating with).

Only include events that have their integration_metadata_field_3 property equal to the value you pass in for this parameter. Note: An event's integration_metadata_field_3 property is an integration-specific text field only accessible via the ExhibitDay API. This field is typically used to store metadata or information about a particular event (e.g., the "external id" of the event from another system you're integrating with).

Only include events that have their integration_metadata_field_4 property equal to the value you pass in for this parameter. Note: An event's integration_metadata_field_4 property is an integration-specific text field only accessible via the ExhibitDay API. This field is typically used to store metadata or information about a particular event (e.g., the "external id" of the event from another system you're integrating with).

Only include events that have their integration_metadata_field_5 property equal to the value you pass in for this parameter. Note: An event's integration_metadata_field_5 property is an integration-specific text field only accessible via the ExhibitDay API. This field is typically used to store metadata or information about a particular event (e.g., the "external id" of the event from another system you're integrating with).

Include the tasks collection for each event in the result set. Note: hydrating the task collection for each event in the results will naturally yield a larger response size and response time. Set the value for this parameter to true only if you need to include the list of tasks for each event in the result set.

Include the list of available task sections for each event in the result set. Note: hydrating the event task section collection for each event in the results will naturally yield a larger response size and response time. Set the value for this parameter to true only if you need to include the list of task sections for each event in the result set.

Include the list of miscellaneous expenses & credits for each event in the result set. Note: hydrating the event miscellaneous expenses & credits collection for each event in the results will naturally yield a larger response size and response time. Set the value for this parameter to true only if you need to include the list of miscellaneous expenses and credits for each event in the result set.

Include the event custom fields (i.e. custom fields that have been added to your workspace) for each event in the result set. Note: hydrating the event custom field collection for each event in the results will naturally yield a larger response size and response time. Set the value for this parameter to true only if you need to include the custom field values for each event in the result set.

Only include the event that has this id. The result is still a list: it holds that one event, or no events if your workspace has no event with that id. To retrieve a single event object, use /v1/events/info instead. A value that isn't an event id number is rejected with an error.

Only include the events in one category: "all" (all events), "upcoming" (events that end today or later, including events that are in progress), "past" (events that ended before today), or a year such as "2026" (events that start in that year). "Today" is based on your workspace's time zone. When you pass in one of these values, the start date and end date filters are ignored. To get the list of categories for your workspace (with a category for every year that has events), use /v1/references/event_start_date_categories. Any other value is rejected with an error.

Another way to filter events by the value of a Custom Text field or a Custom Dropdown field: pass in the field's id as filter_by_custom_field_value_setting_id and the value to look for as filter_by_custom_field_value_setting_value. You can get the ids of the custom fields you can filter by from /v1/references/filterable_event_custom_fields. Only the events whose value for that field equals the value you pass in are included (the comparison is not case-sensitive and ignores leading and trailing spaces). An id that isn't a custom text field or custom dropdown field in your workspace is rejected with an error.

The value to look for in the custom field given in filter_by_custom_field_value_setting_id (see that parameter).

Sorts the events by when they were added or last updated. Accepted values: create_timestamp_asc, create_timestamp_desc, last_update_timestamp_asc, last_update_timestamp_desc. Without this parameter, events are sorted by start date (earliest first).

Return a shorter version of each event (id, exhibitday_url, name, start and end dates, participation type, format, star rating, created and last update timestamps, and the integration metadata fields). Use it for faster responses when you only need to identify events. Note: the hydrate parameters don't apply to these shorter events.

Only include events that were added or changed on or after this date and time, for example 2026-10-14T18:30:00 (a date alone, such as 2026-10-14, means midnight). Responses give event_last_update_timestamp in UTC (it ends in Z), and that value can be passed back unchanged; a value without an offset is read as US Eastern time, and any other offset (e.g., 2026-10-14T18:30:00-04:00) is converted. To sync changes, save the latest event_last_update_timestamp you receive and pass it in next time (events changed at exactly that time come back again, so skip ids you already have). Deleted events are not returned. Any other value is rejected with an error.

The most events to return (a whole number of 1 or more). Use it with $offset to read a long list in pages: total_records in the response counts every matching event and has_more is true while more pages follow (the X-Total-Count header carries the total too). Without $limit, every matching event is returned.

How many events to skip before the first one returned (a whole number; 0 by default). For the next page, add the number of events you received to $offset.

Pass in "array" to get the results as a plain JSON array (without records_found, total_records, has_more and list_type; the X-Total-Count header still gives the total), or "wrapped_in_array" to get the usual response inside a JSON array.

If the request has an error (e.g., an invalid filter value), return an empty list with HTTP status 200 instead of an error response.

The ETag of a response you already have: while the data is unchanged the API answers 304 Not Modified without a body.