Skip to main content

cvent Registration

cvent Registration Integration Guide

Overview

This guide explains how to connect Bridged with cvent Registration to read event registration data including attendee profiles, registration details, ticket/admission item assignments, and session enrollments. The integration supports reading this data for activation, qualification, and nurture playbooks where attendee registration context is needed.

cvent Registration is Cvent's dedicated registration module for event sign-ups, ticketing, and attendee data collection. It provides REST APIs and webhooks for programmatic access to registration data .

Primary Use Case: Read Registration Data

For Bridged's identity and registration integrations, the primary use case is reading registration-related data, including:

Data Type

Use in Bridged

Attendee/Contact profiles

Personalize outreach and qualification conversations

Registration details

Confirm registration status, ticket types, answers to registration questions

Admission items (tickets)

Understand which ticket types attendees have purchased

Session enrollments

Track which sessions attendees have registered for

Guest registrations

Identify primary registrants and their guests

Prerequisites

Before starting, ensure you have:

  • A Cvent account with REST API access enabled

  • A Cvent user with Admin permissions to create API workspaces and webhooks

  • Access to the Cvent Developer Portal (developer-portal.cvent.com)

  • Your Event ID (the event you want to read registration data from)

Note: REST API access must be enabled for your account. If you don't see API options, contact Cvent Support.

Connection Methods

Method

Best for

Setup complexity

Data Access

REST API (OAuth 2.0 Client Credentials - Preferred)

Automated batch data pulls

Medium

Full read access to contacts, attendees, admission items

Webhooks (Token/OAuth)

Real-time registration event notifications

Medium

New registrations, cancellations, modifications

Manual Export (CSV)

One-time or backup data pulls

Low

Attendee lists, registration reports

Recommendation: Use REST API for bulk/scheduled data pulls and webhooks for real-time registration triggers.

Step 1: Create an API Workspace in Cvent

  1. Log in to your Cvent account

  2. Click the App Switcher (blue button in top right) → Admin

  3. Navigate to Integrations → REST API

  4. Click Create Workspace

  5. Enter a workspace name (e.g., Bridged Registration Integration)

  6. Under Scopes, select Custom and add the following read scopes:

Scope

Purpose

event/contacts:read

Read contact/attendee profiles

event/attendees:read

Read attendee registration records

event/admission-items:read

Read ticket/admission item details

event/sessions:read

Read session enrollment data

event/custom-fields:read

Read custom registration question answers

  1. Click Save

Step 2: Create an OAuth Application

  1. Navigate to the Cvent Developer Portal

  2. Click Create Application

  3. Fill in application details:

    • Application Name: Bridged Registration Integration

    • Application Type: Machine to Machine (for server-to-server)

  4. Under Scopes, select the same read scopes from Step 1

  5. Click Save

  6. Copy and save your Client ID and Client Secret

Step 3: Determine Your Cvent Region

Region

API Base URL

OAuth Token URL

North America

https://api-platform.cvent.com

https://api-platform.cvent.com/oauth/token

Europe

https://api-platform-eur.cvent.com

https://api-platform-eur.cvent.com/oauth/token

Sandbox

https://api-platform-sandbox.cvent.com

https://api-platform-sandbox.cvent.com/oauth/token

Step 4: Configure Bridged to Connect to cvent Registration

  1. Log in to your Bridged dashboard

  2. Navigate to the Integrations section. If you do not see this section, contact support@bridged.media

  3. Click cvent Registration → Connect Account

  4. Select OAuth 2.0 Client Credentials as your authentication method

  5. Enter the following credentials:

Field

Description

Region

Your Cvent account region (North America, Europe, or Sandbox)

Client ID

From your OAuth application

Client Secret

From your OAuth application

Event ID

Your target event identifier

  1. Click Connect

API Request Example

To verify your connection works:

bash

curl -X GET "https://api-platform.cvent.com/events/{EVENT_ID}" \
  -H "Authorization: Bearer {ACCESS_TOKEN}"

Step 5: Configure Webhooks for Real-time Registration Sync (Optional)

Webhooks allow Bridged to receive real-time notifications when registrations occur .

Step 5.1: Set Up Webhook Configuration in Cvent Admin

You must have full access to the "Account Integrations" administrative right .

  1. Log in to Cvent → click Admin

  2. Navigate to Integrations → Push API Integrations

  3. Click Create Integration

  4. Enter:

    • Name: Bridged Registration Webhook

    • Type: Webhooks

    • Default Endpoint: https://gateway.bridged.media/webhooks/cvent-registration

  5. Select Authentication Method :

    • Token: Enter a static authentication token (<150 characters)

    • OAuth: Provide Authorization Endpoint, Client ID, Client Secret, and Scopes

    • Salesforce OAuth: Select existing connection

    ⚠️ For OAuth, token expiry can cause auth failures; ensure your OAuth client supports token refresh .

  6. Click Save

Step 5.2: Configure Integration Points

  1. Click Edit on your webhook configuration

  2. Under Synced Objects, select the objects you want to sync

  3. Navigate to the Integration Points tab

  4. Click Add Integration Point and select relevant triggers :

Integration Point

When it triggers

Invitee/Guest Registered for Event

New registration completed

Invitee/Guest Event Registration Cancelled

Registration cancelled

Invitee/Guest Event Registration Modified

Registration details changed

Invitee/Guest Marked as Event Participant

Attendance confirmed

Step 5.3: Associate Webhook to Your Event

  1. Navigate to Events → select your event

  2. Click Integrations → Setup

  3. Under Webhooks, select your configuration and enable

  4. Click Save

Step 6: Reading Registration Data via REST API

Based on Cvent's Registration API documentation , the following endpoints are available:

List Contacts (Attendees)

Retrieves existing contacts in your address book:

bash

GET /contacts

Use this to inventory attendees before registration or sync existing profiles.

Get Contact by ID

bash

GET /contacts/{contactId}

Returns full contact profile including name, email, custom fields.

List Admission Items (Tickets)

Retrieves ticket types for an event:

bash

GET /admission-items?eventId={EVENT_ID}

Each registrant requires an admission item assignment . The response includes:

  • Admission item name and code

  • Total, remaining, and consumed capacity

  • Open/closed status

List Attendees (Registrations)

Retrieves all registrations for an event:

bash

GET /attendees?eventId={EVENT_ID}

Returns registration records including:

  • Contact ID (linked to attendee profile)

  • Admission item ID (ticket type)

  • Registration status (Accepted, Cancelled, etc.)

  • Answers to registration questions

  • Guest registration flags

List Sessions and Enrollments

For events with sessions:

bash

GET /sessions?eventId={EVENT_ID}
GET /sessions/{sessionId}/enrollment

Step 7: Registration Data Workflow

To fully understand attendee data, follow this workflow :

text

1. GET /events → Get Event ID
2. GET /admission-items → Get ticket type IDs
3. GET /contacts → Get or create contact IDs
4. GET /attendees → Get registration records linking contacts + admission items

Understanding Guest Registrations

Guests are individuals brought by a primary registrant (spouse, child). Key fields :

Field

Description

guest: true

Identifies a guest registration

primaryId

Attendee ID of the primary registrant

To retrieve guests for an event, filter attendees by guest: true.

Step 8: Configure Sync Settings

Setting

Options

Description

Data objects

Contacts, Attendees, Admission Items, Sessions

Which registration data to read

Sync frequency

Hourly, Daily, Weekly

How often to refresh data

Sync method

REST API, Webhooks, Both

Preferred data access method

Registration status filter

Accepted, Cancelled, All

Filter by registration status

Bulk sync limit: Each bulk operation is limited to 50 records per request. Use pagination with page and per_page parameters.

Common Use Cases

Playbook

How Registration Data Is Used

Activation

Read attendee list to trigger pre-event reminders, ticket confirmations, and logistics via WhatsApp

Qualification Agent

Read registration details (ticket type, answers to questions, session enrollments) for lead scoring

Nurture & Conversion

Read registration status for post-event follow-up; identify no-shows vs. attendees

Example Conversation Powered by cvent Registration Data

When an attendee asks "What sessions am I registered for?", Bridged:

  1. Reads attendee record to get contact ID

  2. Queries session enrollments for that attendee

  3. Returns personalized schedule information

When a lead asks "What's included in my VIP ticket?", Bridged:

  1. Reads attendee record to get admission item ID

  2. Retrieves admission item details

  3. Returns ticket inclusions conversationally

Rate Limiting & Performance

Consideration

Details

Rate limits

Vary by Cvent API plan

Webhook sync

May have up to 1-hour delay depending on configuration

REST API pagination

Use per_page (max 200) and page parameters

Bulk operations

Maximum 50 records per request

Security & Permissions

  • Cvent uses OAuth 2.0 Client Credentials for REST API authentication

  • Webhooks support Token, OAuth, or Salesforce OAuth authentication

  • OAuth tokens should support refresh to avoid auth failures

  • All API calls should be made over TLS 1.2+

  • Credentials are encrypted and never stored in plain text

Required Administrative Rights

Right

Required for

Account Integrations (full access)

Creating webhook configurations at account level

Event & Survey Integrations (full access)

Enabling webhooks for specific events

Troubleshooting

Issue

Likely cause

Solution

Connection fails (401)

Invalid Client ID/Secret

Verify credentials in Developer Portal

No data returned (403)

Missing API scopes

Add required read scopes to workspace and OAuth app

Webhook not received

Webhook not associated with event

Associate webhook configuration to specific event

Webhook auth fails

Token expired

OAuth tokens expire; ensure refresh token support

Duplicate contact records

Multiple emails for same person

Merge duplicate records in Cvent Address Book

Registration status not updating

Status not set to Accepted

When adding attendees, set status: "Accepted"

Guest registration fails

Primary attendee not registered

Register primary attendee first before adding guests

Support

For integration support, contact your Bridged account manager or email support@bridged.media.

For Cvent-specific questions:

  • Cvent Developer Portal: https://developers.cvent.com

  • REST API Documentation: Registration Guide section

  • Webhook Setup: Push API Integrations in Admin

  • API access requests: Contact Cvent Support