canonical: https://jentic.com/apis/cvent.com/cvent

# Cvent REST APIs

Jentic publishes the only available OpenAPI specification for Cvent REST APIs, keeping it validated and agent-ready. Cvent is an enterprise event-management platform covering in-person, virtual, and hybrid events, exhibitors, attendee journeys, surveys, travel, and webcasts. The REST API exposes 427 endpoints across attendees, sessions, registrations, exhibitors, badges, surveys, housing, travel, payments, and webhooks. It supports OAuth2 client-credentials and authorization-code flows and is hosted in both North American and European data centres.

## For AI agents

Manage Cvent events end to end - registrations, attendees, sessions, exhibitors, surveys, badges, and webhooks - via 427 REST endpoints behind OAuth2.

## Scope

Does not handle ticket discovery on third-party marketplaces, generic CRM contact storage, or payment processing networks - use for managing your own events on the Cvent platform only.

## Capabilities

- Register and update attendees against an event via the /attendees endpoints
- Manage event sessions, speakers, and seating using /sessions and related resources
- Schedule appointments and check availability through /appointment-events and /appointment-availability-times
- Run surveys and collect responses via the /surveys endpoint group
- Coordinate exhibitor profiles, content, and team rosters under /exhibitor* endpoints
- Subscribe to event lifecycle webhooks via /hooks and trigger badge prints via /badge-print-job

## Use cases

### Event registration automation

Automate attendee registration from a marketing form or CRM into a Cvent event. Code creates or updates the attendee record via /attendees, attaches custom field values, and confirms registration status. Cvent handles confirmations, badges, and downstream housing or travel coordination.

Example prompt: Create an attendee with email jane@example.com on event 12345 and confirm the registration status field is 'Registered'.

### On-site session and appointment management

Run an on-site portal that lets attendees browse sessions, book 1:1 appointments with exhibitors, and check capacity in real time. The /appointment-events and /sessions endpoints expose availability, allow bookings, and surface speakers, so a custom mobile app or kiosk can drive the floor experience.

Example prompt: List available 1:1 appointment slots on event 7890 between 14:00 and 16:00 and book the first slot for attendee 56789.

### Post-event survey and reporting

Send a survey after the event and pipe responses into a BI tool. The /surveys endpoints expose responses, and /attendee-insights surfaces engagement signals so revenue and marketing operations can score sessions and update lead records in the CRM.

Example prompt: Pull all completed responses for survey 42 on event 12345 and write them to the analytics warehouse.

### Exhibitor and lead capture coordination

Coordinate exhibitor onboarding, booth content, and lead retrieval across a multi-day event. The /exhibitor, /exhibitor-content, and /leads endpoints let an exhibitor portal manage profiles, accept lead scans, and sync the captured leads back into Salesforce or HubSpot.

Example prompt: List leads captured by exhibitor 123 on event 7890 in the last 24 hours and push them into the CRM.

### AI agent event assistant via Jentic

Expose Cvent operations to an autonomous agent so it can answer attendee questions, register guests, or pull session schedules during an event. The agent searches Jentic for 'register an attendee for an event', loads the schema, and executes - the OAuth tokens stay in your Jentic One instance.

Example prompt: Through Jentic, register attendee Jane Doe (jane@example.com) on event 12345 and reply with the confirmation number.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /attendees | List event attendees |
| POST | /account-user-groups | Create an account user group |
| GET | /sessions | List sessions for an event |
| POST | /appointment-events/{id}/appointments | Create an appointment within an event |
| GET | /exhibitors | List exhibitors attached to an event |
| GET | /surveys | List event surveys |
| POST | /hooks | Subscribe to a webhook event |

## Key resources

- **Attendees** — Register, update, and segment event attendees
- **Sessions** — Manage agenda items, speakers, and seating
- **Appointments** — Schedule and track 1:1 meetings during events
- **Exhibitor** — Manage exhibitor profiles, content, and teams
- **Surveys** — Build surveys and collect attendee responses
- **Hooks** — Subscribe to event lifecycle webhooks
- **Travel & Housing** — Coordinate hotel blocks, room assignments, and travel itineraries
- **Webcasts** — Manage virtual session streams and recordings

## Why Jentic

- **Setup:** Wiring the Cvent REST APIs by hand means running the OAuth2 client-credentials exchange, refreshing bearer tokens, choosing between the US and EUR api-platform hosts, and mapping hundreds of endpoints yourself. Through Jentic you install once, import the Cvent REST APIs from the API Directory, store the client credentials once, and your agent calls it.
- **Permission scoping:** Cvent drives most operations from the request body and OAuth scopes rather than a single resource id in the URL path, so scope the agent to the operations it needs, such as listing attendees or reading sessions. If you grant only those reads, creating user groups or registering webhooks is not included unless you add them.
- **Credential handling:** Your Cvent OAuth2 client credentials are stored once, encrypted, by your own Jentic One instance, which mints short-lived tokens at execution time. The client secret never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'register an attendee for an event' or 'list event sessions', and Jentic returns the matching Cvent operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Swoogo** — Mid-market event management platform with strong API coverage
- **Meetup** — Community-events platform with a public-facing audience model
- **Ticketmaster Discovery API** — Public events and venue discovery feed

## FAQ

### Why is there no official OpenAPI spec for Cvent?

Cvent does not publish a single OpenAPI specification covering its full REST surface. Jentic generates and maintains this spec so that AI agents and developers can call Cvent via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Cvent REST API use?

OAuth2 with both client-credentials and authorization-code flows. You exchange your application's client ID and secret at the OAuth2 token endpoint to receive a bearer token valid for one hour, which is then sent in the Authorization header on subsequent calls.

### Can I register an attendee for an event through the API?

Yes. The /attendees endpoint group lets you create, update, and look up attendee records on a specific event, including custom field values and registration status.

### Does Cvent support webhooks for event lifecycle changes?

Yes. The /hooks endpoints let you subscribe to event lifecycle notifications - registrations, session updates, and other state changes - so downstream systems can react without polling.

### What are the rate limits for the Cvent REST API?

Cvent enforces tiered limits: Free at 1,000 calls/day and 2 calls/sec, Standard at 15,000 calls/day and 10 calls/sec, Premium at 500,000 calls/day and 25 calls/sec. Daily quotas reset at midnight GMT and 429 responses indicate you have hit a limit.

### How do I register an attendee through Jentic?

Run pip install jentic, search for 'register an attendee for an event', load the /attendees POST schema, and execute with the event ID and attendee fields. Jentic handles the OAuth2 token exchange so your code never sees the client secret.

### Can I limit what my agent is allowed to do with the Cvent REST APIs?

Yes. Because you run Jentic One yourself, your own rules decide which Cvent operations and OAuth credentials the agent may use, so you can scope it to just the calls it needs, such as listing attendees via /attendees or reading sessions via /sessions. Cvent drives most operations from the request body and OAuth scopes rather than a resource id in the URL path, so granting only those reads means write actions like creating account user groups or registering webhooks via /hooks stay out of reach unless you explicitly add them. This keeps the agent confined to a narrow set of Cvent endpoints under your control.