Registration_type key is missing in GET meeting/{id} for meeting type=8

API and Webhooks
1

Hi there!

I can set registration_type via API or Zoom dashboard when creating a new recurring meeting with fixed time (type=8).

I can PATCH it with new registration_type, or update in Zoom dashboard by editing a meeting.

Per API docs, this key is used for recurring meeting with fixed time only (type=8)

However, performing GET on meeting/{ID} returns ALL keys but the registration_type.
Same result in Postman/Zoom Api Tool/Curl

POST: Create new recurring meeting
    {
      "topic": "Api Create Test",
      "type": 8,
      "start_time": "2020-03-31T19:00:00Z",
      "duration": 60,
      "timezone": "America/New_York",
      "recurrence": {
        "type": 1,
        "repeat_interval": 1,
        "end_date_time": "2020-04-01T03:59:00Z"
      },
      "settings": {
        "host_video": false,
        "participant_video": false,
        "cn_meeting": false,
        "in_meeting": false,
        "join_before_host": false,
        "mute_upon_entry": false,
        "watermark": false,
        "use_pmi": false,
        "approval_type": 1,
        "registration_type": 2, <---- key is present and correctly set when meeting is created
        "audio": "both",
        "auto_recording": "none",
        "enforce_login": false,
        "enforce_login_domains": "",
        "alternative_hosts": "",
        "registrants_email_notification": "true"
      }
    }



GET meeting/{ID}
    {
      ...
      type: 8,
      status: 'waiting',
      ...
      occurrences: [
      	...
        {
          occurrence_id: '1585422000000',
          start_time: '2020-03-28T19:00:00Z',
          duration: 60,
          status: 'available'
        },
        {
          occurrence_id: '1585508400000',
          start_time: '2020-03-29T19:00:00Z',
          duration: 60,
          status: 'available'
        }
        ...
      ],
      settings: {
        host_video: false,
        participant_video: false,
        cn_meeting: false,
        in_meeting: false,
        join_before_host: false,
        mute_upon_entry: false,
        watermark: false,
        use_pmi: false,
        approval_type: 1,
        audio: 'both',
        auto_recording: 'none',
        enforce_login: false,
        enforce_login_domains: '',
        alternative_hosts: '',
        close_registration: true,
        registrants_confirmation_email: true,
        waiting_room: false,
        global_dial_in_countries: [ 'US' ],
        global_dial_in_numbers: [ ... ],
        contact_name: '***',
        contact_email: '****',
        registrants_email_notification: true,
        meeting_authentication: false
      },
      recurrence: {
        type: 1,
        repeat_interval: 1,
        end_date_time: '2020-04-01T03:59:00Z'
      }
    }

Image:

get-meeting-id-miss-key
get-meeting-id-miss-key384×905 120 KB

2

Hey @WMaster,

This does seem like a bug. Can you send me the created meeting id, and the name of your App?

Thanks,
Tommy

3

Hi Tommy:

Here’s one: 418064758
App Client ID: XM6_J4sASaK5w8ZteWG6SA

Thank you

4

Thanks @WMaster,

We are looking into the issue and get back to you. (ZOOM-147990)

-Tommy

5

Hi Tommy!

Any chance this fix will make it into next API update release and/or if there’s an ETA?

Without knowing the registration type we can’t offer users proper registration choices on any multi-occurrence meetings.

We figured out a way around this for now, and will be launching with that, but having that key will make things much smoother.

Thank you!

6

Hey @WMaster,

We are still looking into this. We are all super busy at the moment.

Glad you figured out a work around.

Thanks,
Tommy

7

Hi @tommy

Any news on this fix?

8

Hey @someone,

No updates yet. I will post back here once we start working on this! :slight_smile:

Thanks,
Tommy

9

Hey @someone, @WMaster,

Please check to see if the registration_type is being returned now.

Thanks,
Tommy