Skip to main content
Skip table of contents

Installation and Configuration

For a quick installation checklist, check out our CVENT Onboarding Checklist.


This guide will assist you with getting started configuring your Cvent integration. The goal is to make sure you understand and have taken all the steps necessary for the integration to work autonomously afterward. We recommend you try one step at a time although some steps can be worked on in parallel (i.e. one step may not need to wait for a previous step to be completed).

Attendee Workflow

A common case scenario:

  1. An attendee visits the association's website

    1. And browses the meeting web page displaying the upcoming event

      It is recommended to secure the meeting web page in permitting access to authenticated users only.

  2. The attendee clicks on a link from the content page

    1. The link is provided and rendered by our Single Sign On widget

      1. It can be a RiSE iPart

      2. Or it can be a Web User Control (in case of a Public View website)

    2. This link is configured to reference a Cvent event code

      1. A Cvent event code will be made available on the CSI Cloud Cvent Event Configuration section

  3. The link sends the attendee context information to our CSI Cloud Cvent middleware application

    1. The middleware performs a number of validations

      1. Ensure member is authenticated and authorized for the event selected

        1. This is performed by running an IQA associated with the event

      2. Identify registrant in Cvent using their Standard Service API

        1. This creates or updates attendee information in Cvent based on IQA result returned

    2. And upon success the attendee is redirected to the Cvent registration website

  4. Attendee completes their registration

    1. Once the event is done Cvent will trigger their webhooks

      1. CSI Cloud Cvent middleware provides an endpoint to receive Cvent information

      2. This allows creation and update of the iMIS Activity records

1. Steps to Perform At Cvent

Login to the Cvent application website

You can log in to the Cvent app here.

Cvent would have provided you with an account name and credentials.

Create a New Event

Skip this step if you have an existing event to use.

You may need Cvent to assist you with setting up your meetings and events. 

Add a Webhooks Integration Endpoint for Your Account

You only need to set this up once. It is account wide. Go to Admin > Integrations > Push API Integrations

Then click on Create Integration to add a new Webhooks integration. Give it a meaningful Name and select Webhooks as the Type.

The Default Endpoint value should be:

To find out the Authentication Token you need to login to the CSI Cloud Cvent middleware application.

Check the Synced Objects

And enable the integration for:

  • All new events

  • All new sessions

Check the Integration Points

And add these integration points for our purposes:

  • Invitee/Guest Registered for Event

  • Invitee/Guest Event Registration Cancelled

  • Invitee/Guest Event RegistrationModified

  • InviteeSubstitutedInAnEvent (if you plan on substituting registrants)

Enable the Webhooks Integration for Each Event

After creating the global Webhooks Integration endpoint you need to enable it for each event. Go to Events > [your event] > Event Details > General > Push API Integrations

Click on Add Webhooks to enable the newly created Webhooks Integration endpoint

Check the Basic Settings and make sure to Activate webhooks for this event

Whitelist the Cvent App IP Addresses

In the remote event that your webhooks may not be working, Cvent may have to Whitelist the following IP addresses in your Cvent account settings in order for the CSI Cvent app to successfully communicate with the Cvent APIs:

IP Address


CSI Cloud API Router

CSI Office (for troubleshooting and debugging)

Cvent App - Outbound IP

See more from Full List below

Cvent App - Inbound IP

Load Balancer for Data Processor

Full List Of Cvent App - Outbound IP:,,,,,,,,,,

How to Enable Custom IDs for Each Event

  1. In an event, navigate to Registration > Registration Process > Open Site Designer.

  2. Click on the Registration Page dropdown in the top left > Click the gear icon next to your Registration Path(s).

  3. Scroll to the "External Data Source" section and select "Cvent" in the dropdown.

Find Your SOAP API Credentials

You may need to call Cvent to provide you with your SOAP API Credentials. This will allow us to access your Cvent information using the SOAP endpoint (North America Only):

If you are not in North America, please find your API url here: SOAP API Archives - Cvent | Developer Hub   Send CSI a help ticket @ so that they can change this in the configuration.

To review your SOAP API Usage and configuration, go to Admin > Integrations > SOAP API Usage

Ensure our CSI Clout Router server IP addresses are whitelisted to the SOAP API. Click on the dropdown next to the API username to validate the Allowed IP Addresses.

Confirm Your Standard Service Support

You may need to call Cvent to confirm they have enabled this feature for you. It is also known as HTTP POST Process for Events which allows us to provide you with a Single Sign On experience.

Typically a form is submitted via HTTP Post on your behalf at this URL: This is used by our registration iPart (and custom Web User Control) to authenticate members for the Cvent meeting.

2. Steps to Perform on the CSI Cloud Dashboard

Log In to the Cloud Dashboard

Navigate to

  • Username: The username in your iMIS environment (Typically the manager account or admin)

  • Password: The password for this account.

  • CSI Cloud ID: This is the Alias for your iMIS instance. This would be given to you by CSI. Learn more.

Create the Connection to Cvent

Once logged in to the CSI Cloud Dashboard, you will notice a menu to your left under the "Connectors" category (if it is hidden, click on the CSI icon in the upper left corner). This menu can be pinned or unpinned for your preference. If you are licensed for Cvent, then it will be listed under “Apps” in this menu.

When you click on Cvent, you will be presented with a sub-menu (Account, Events, Registration iPart).

Set Up Your Cvent Account

After navigating to the Cvent Account information you will see the following data points:

  • Cvent Account Name: This is supplied to you by Cvent.

  • API Username: This is supplied to you by Cvent (or created by you through their site)

  • SOAP API URL: This is Cvent’s API URL. Supplied to you by Cvent. This should remain fairly static.

  • Registration URL: This is Cvent’s Registration URL. Again, this should be static.

  • Webhooks Authentication Token: This will be created for you automatically. This allows Cvent to authenticate with your iMIS data.

  • Last Updated On: The date/time account information was last updated.

Map a Cvent Meeting

Events is the page where you would be able to add OR edit new events for your organization provided they are setup in Cvent. After navigating to the Events page, you should see the Add New button to be able to add your event. After clicking on this, you will encounter the following data points:

Cvent Event Code: This will be the event code created by Cvent for this specific meeting. Based on your account setup, you should be able to use the SELECT button to select the event from Cvent that you want to setup. You will also be able to type in this textbox to manually enter your Cvent Event Code.

iMIS Meeting Code: This is the meeting code from your iMIS meeting that has been setup that you want to link with Cvent. You will be able to use the SELECT button for this as well to select your iMIS meeting. You will also be able to type in this textbox to manually enter your iMIS Meeting Code. NOTE: You do not NEED to setup a Meeting in iMIS for this integration to work. But you need to enter a distinct meeting code.

Registrants IQA Path: This allows you to specify the iMIS IQA for the list of registrants allowed to register for this meeting. You must have an IQA that matches the result set for Cvent Standard Service. You can download a sample IQA below in "TIP". A SELECT button is also active for this data point and is recommended. After hitting the “Select” button, a dialog page displays with your IQA’s from the root.

 To learn more about importing a sample Cvent IQA into your iMIS environment, go here.

Once you have navigated to the IQA you would like, you can Run the IQA to see the results, then Select the IQA to be used in your Event Setup.

Allow Anonymous Registration: This will allow the user to register for the event from within the Cvent application without regard for who they are or whether they are allowed to register or not. When you have successfully created an Event integration configuration, your page should look similar to this as an example:

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.