WebEx Connector - Technical Overview
To confirm that your WebEx plan includes API access get in touch with your WebEx sales representative
The WebEx connector requires a user with administrator privileges. Along with this user the integration requires 3 additional pieces of information from WebEx in order to connect.
- Site Brand Name
- Site ID
- Partner ID
You can learn more about how to gather this information and install your WebEx connector in the Bedrock Portal here.
Each object below may have a certain set of sub-objects. Not all sub-objects are supported by Bedrock Data so it's important to discuss any specific data points related to these objects that are important to your integration needs with our sales team.
|Object||Permissions||Custom Field Support||Dedupe Key|
|Attendee||Read / Create||No|
|History||Read||No|| Attendee Email
API Version and Limits
The Bedrock WebEx connector is currently using the WebEx XML API.
Every Connector has a set of considerations and limitations that can impact how data will flow from one system to another. These may not be the only limitations depending on your integration needs. Make sure to discuss your key integration goals with your Bedrock Data sales representative to ensure we can meet your needs.
- At this time the only events Bedrock Data supports are in the Event Center. We are unable to read events in the Training or Meeting Center.
- Bedrock Data does not support any WebEx - ADFS integration. The user used to authenticate must be created in WebEx and not in Active Directory.
- A Session Key is required in order to create a new Attendee in WebEx. This is often the case when you are using a payment system where someone can pay to get access to a scheduled Webinar. We recommend setting up a custom field for Session ID in this system and mapping this to the Session ID field in Webex and when someone is paying they must enter this ID into the form when purchasing.