Overview
Travel and hotels can be important aspects of an event.
Prerequisites
To use Cvent’s REST API, your developer needs access to a workspace with the needed permissions. Account users can find more details about creating workspaces in Inviting Your Developers.
Objects
To work with the Event Hotel and Air API, you’ll need to understand the objects involved.
- Air Requests: Collected from invitees during event registration, air requests indicate the registrants’ desired air travel plans but don’t represent booked flights.
- Air Actuals: Represent the registrant’s booked flight information. Air actuals can be supplied by the event planner or provided by a registrant.
- Hotel Request: Represents hotel requests collected from invitees during event registration. They indicate the registrants desired hotel accommodations but don’t necessarily correlate to bookings.
Retrieving Hotel & Air Details
Event Travel endpoints retrieve travel data from a specific event. To do this:
- Retrieve the ID of the event of interest with the List Events API.
- Use the event ID to retrieve hotel and air details using the Event Travel endpoints.
Retrieve Expanded Responses
Event planners can request travel details from attendees, like travel questions. These details are only available via the Event Travel APIs if your requests include the required scopes. If your scopes are limited to travel, you’ll only receive the core information of the Event Travel endpoints. By providing more scopes, the caller can receive an expanded response that includes the extra data. The data available for expanded responses are documented on the Event Travel APIs.
Example
To retrieve travel questions, your request needs to contain the scopes needed
for List Event Questions, which
is event/events:read.