Incorrect specification in Event Attendance Report API

API and Webhooks Zoom Events
1

There are two items in the Event Attendance Report API that appear to be errors in the specification.

1,Although the web information for the EventAttendanceReportAPI specification states that it is session_attendance/live_stream_view, the actual response is session_attendance/live_streaming_view.

2,Regarding the Event Attendance Report API, the specification web information states:
connection_made is shown as being included in the array under session_attendance
But the actual response is s
connection_made is not under session_attendance
It seems that.

2

Hello @sone , thank you for posting here. We are working with our Zoom Events engineering team to check what the expected behavior should be. We will reply shortly, thank you for your patience.

3

@sone , this is an error with our documentation spec. The correct behavior is live_streaming_view . We will update the documentation shortly. Thank you for identifying!

4

@michael.zoom
Thank you for your confirmation.

Similarly, in the Event Attendance Report API,
connection_made
It is stated on the web that it is under session_attendance, but the actual behavior seems to be different.
Is this also an error on the website?

5

Hi @sone
Can you please share the response body you are getting so I can take a look at this ? make sure to delete any personal information from the response

6

@elisa.zoom
Thank you for your confirmation.

The person in charge is on vacation and cannot receive data via text.
I expressed the output result images I received in the past in text.

|-display name:
|-email:
|-first_name:
|-last_name:
|-event_attendance :
|-lobby_attendance :
|-lobby_chat_sent:
|-survey_taken
|-total_sessions_joined:
＞-session_attendance
|-role:
＞-tickets
|-profile_created:
|-connection_made:
|-personal_chats:
＞-attendance_type:

7

Hello @michael.zoom

I hear that the website will be revised soon, but how long will it take to be revised?

8

Hello @elisa.zoom

I have received the data, so I have attached a portion of it.

{“total_records”:14
attendees:[
{display_name":"
email:“”
first_name:“”
last_name:“”
event_attendance:“attended”
lobby_attendance:“attended”
lobby_chat_sent:1
survey_taken:0
total_sessions_joined:2
session_attendance:[
{“session_id”:“”
session_name:“”
session_attendance:“attended”
duration_spent_in_session:52
chat_messages_sent:“4”
material_download:false
recording_view:true
recording_view_duration:1
live_streaming_view:true
live_streaming_view_duration:1}
{“session_id”:“”
session_name:“”
session_attendance:“attended”
duration_spent_in_session:37
chat_messages_sent:“2”
material_download:false
recording_view:false
recording_view_duration:0
live_streaming_view:true
live_streaming_view_duration:1}
]
role:“Special role”
tickets:[
{“ticket_type_name”:“Moderator Ticket”
ticket_type_id:“”
ticket_id:“”
questions:}
]
profile_created:true
connection_made:0
personal_chats:0
attendance_type:[“hybrid”]
}

9

Thanks for sharing that with me @sone

10

Hi @elisa.zoom

Thank you for your response to this matter.

It looks like the documentation has been corrected.
Are you saying that there was also a flaw in the documentation regarding connection_made?

11

Hi @sone
Yes, there was an error in our documentation. I appreciate your help on this!