Cvent
Version
This integration utilizes the Cvent REST API.
Base URL
The base URL used for all Cvent API endpoints:https://api-platform.cvent.com/ea/
The hostname of the endpoint depends on the region that your Cvent account is hosted in. The base URL for the North America region is shown above.
Authentication & Authorization
The DataGrail Cvent integration connects using OAuth 2.0 with the following credentials: Client ID and Client Secret.
Cvent connects via OAuth 2.0 with Client Credentials Grant Flow. Client ID and Client Secret credentials can be obtained through Cvent Support.
An access token obtained with a Client Credentials grant has a fixed lifetime. DataGrail updates the access token after it expires to keep the connection alive.
Publicly exposing your API credentials can allow unauthorized access to the Cvent API endpoints and your data by a third party. DataGrail stores your API credentials encrypted and protected.
Scopes
Cvent API requires specific user scopes that need to be approved in order to grant DataGrail read access on certain objects necessary to complete privacy requests:
The Cvent integration requires specific scopes that must be granted in order to function for a given capability.
| Scope | Access |
|---|---|
event/attendees:read | ✅ |
event/contacts:read | ✅ |
event/attendee-activities:read | ✅ |
appointments/appointment-attendees:read | ✅ |
appointments/appointments:read | ✅ |
event/events:read | ✅ |
event/attendee-links:read | ✅ |
exhibitor/leads:read | ✅ |
event/speakers:read | ✅ |
exhibitor/exhibitors:read | ✅ |
Endpoints Utilized
DataGrail uses the following endpoints to authorize and test the connection:
Limits
Limits in Cvent are calculated using the leaky
bucket algorithm. All requests that are made after rate limits have been
exceeded are throttled and an HTTP 429 Too Many Requests error is returned.
Requests succeed again after enough requests have emptied out of the bucket.
- DataGrail supports requests throttling to stay within 70-80% of specified service rate limits.
- DataGrail processes API responses with HTTP 429 status to interrupt requests, waiting and retrying (using an exponential backoff strategy).
Capabilities
Access
DataGrail's Cvent integration provides Synchronous Access capabilities for the following supported identifier category: Email.Data Interactions
For Access requests, DataGrail will take the following actions:
- Search for Contacts whose email matches the Data Subject email.
- For all collected contacts, DataGrail will:
- Fetch AppointmentAttendees by contact ID
- Fetch Attendees by contact ID
- For all collected attendees, DataGrail will:
- Fetch Attendee Activities by attendee ID
- Fetch Appointments by attendee ID
- Fetch Attendee Links by attendee ID
- Search for Events whose stakeholder email matches the Data Subject email.
- For all collected events, fetch Exhibitors associated with the event.
- Search for Leads whose email matches the Data Subject email.
- Search for Speakers whose email matches the Data Subject email.
- For all objects found, DataGrail will return all available fields.
Endpoints Utilized
Disclaimer: The information contained in this message does not constitute as legal advice. We would advise seeking professional counsel before acting on or interpreting any material.