Webex API: Documented Data Not Being Returned

state1 · ‎05-21-2018

We are implementing the webex api in order to pull registration and attendance data from https://events-cisco.webex.com into our Quick Base Webinar Management System. However, not all the data specified in the documentation is being returned. Please see below from my Quick Base developer:

So we have run into a roadblock.

Prior, Jeffrey was using the returned registration data to fill in data for the attendance report that was missing from the returned attendance data.

However, now that we know not all events have registration, he can only use the call for attendee history. Unfortunately, it is only returning a limited amount of data:

<history:sessionKey>101316464</history:sessionKey>

<history:attendeeName>1111 1111</history:attendeeName>

<history:attendeeEmail>asdf@asdf.asdf</history:attendeeEmail>

<history:startTime>03/09/2004 07:34:45</history:startTime>

<history:endTime>03/09/2004 07:35:21</history:endTime>

<history:duration>1</history:duration>

<history:registered>N</history:registered>

<history:invited>N</history:invited>

<history:ipAddress>172.16.244.122</history:ipAddress>

<history:participantType>ATTENDEE</history:participantType>

<history:voipDuration>0</history:voipDuration>

<history:clientAgent>Windows,IE</history:clientAgent>

<history:confID>4686965</history:confID>

But, the documentation says that the following should be in the schema, but is not being returned:

And if you look at the information it has available, it still does not contain all of the fields we have mapped for the semi-automated import that your team is trying to replace:

https://cin2.quickbase.com/db/bjmvcqy65?a=q&qid=-1000008

Examples: Attendance Duration, Attention to Attendace Ratio, Join Time, Leave time

Of note, Join Time and Leave Time do show up in the schema for a meeting API call, which does not work for events.

So, we need you to reach out to someone to find out why that data is not being returned. We are hoping it will not come back that it is not available through the API and that your desktop user interface is doing some concatenation of data that the API can not do.

Thanks,

Jeff Cravener

Client Solutions Specialist

Trinity Integrated Solutions, Inc.