# API updates 12.21.20

**URL:** <https://devforum.zoom.us/t/api-updates-12-21-20/39018>\
**Category:** New Releases\
**Created:** [December 22, 2020, 6:49pm UTC](https://devforum.zoom.us/t/api-updates-12-21-20/39018 "2020-12-22T18:49:23Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [December 22, 2020, 6:49pm UTC](https://devforum.zoom.us/t/api-updates-12-21-20/39018/1 "2020-12-22T18:49:23Z")

</div>

Hey Zoom developers, the following items were released on December 21, 2020.

## New APIs and Webhooks

- Added APIs that provide metrics on post meeting and webinar feedback.

- Added **Delete a User’s Call Log** API.

- Added billing webhooks.

#### Enhancements

- Added a new field(`event_ts`) in all the webhook payloads. This field represents the timestamp of when the associated event occurred. If you keep track of webhooks delivery timestamp in your storage, you can now determine the latency in webhook delivery by calculating the difference between the delivery timestamp and `event_ts`.

- Added a new field(`outbound_caller_id`) in SIP Trunk APIs.

- Added a new field(`jbh_time`) in the Meeting APIs.

- Added support for `webinar.registration_created` webhook to be triggered when bulk webinar registration is done using a CSV file on the web portal.

- Added security validation requirement in Create and Update a Meeting APIs. All meetings hosted by users in Pro accounts, Business accounts(with 10-100 licenses) and EDU(K/12 Free) accounts must have either a passcode, waiting room or authentication setting enabled.

- Added a new field(`question_and_answer`) in the Webinar APIs.

- Added support for new Zoom Phone plans in the Billing APIs.

- Added a new field(`custom_attributes`) in the `user.updated` webhook.

- Added new fields(`phone_number`,`direct_numbers`,`extension_number`) in **Get a User’s Contact Details** API.

- Added a new field(`login_type`) in **Get a User** API.

- Added a new field(`role_id`) in **Get a User** API and **List Users** API.

- Added a new field(`tracking_fields`) in Meetings Dashboard API.

- Added a new enum(`tracking_fields`) for `include_fields` request parameter in Dashboard API.

- Added a new field(`at_items`) in the **Send Chat Message** API.

- Added a new field(`prevent_host_access_recording`) in Account, Group and Lock Settings APIs.

- Added a new field(`auto_security`) in Account, Group, User and Lock settings APIs.

- Added a new query parameter(`custom_query_fields`) in Account, Group and User Settings APIs.

- Added a new field(`topic`) in the Recording Settings API

- Added a new response field(`plan_united`) in Get Plan Usage API.

- Added a new field(`plan_united_type`) in the User APIs.

- Added a new response fields(`polling_id`, `date_time`) in the poll report APIs.

- Added a new validation error message in **Delete a User** API.

- Added new validation error messages for `plan_united_type` in Create and Update a User APIs.

- Added support to return deactivated users’ recordings via Phone Recording API.

- Added new response field(desk\_phone) in Get Phone User Settings API.

- Added response fields(path, recording\_type, call\_id) in Account and User Call Logs APIs.

- Added request fields(from, to) and response fields(from, to) in **Get User’s Recordings** API.

- Added request fields(from, to) and response fields(from, to) in **Retrieve User’s Voicemail** API.

- Replaced “urn:us:zoom:scim:schemas:extension:1.0:ZoomUser” with “urn:ietf:params:scim:schemas:extension:zoom:1.0:User” schema in Create and Update a User SCIM APIs.

#### Bug Fixes

- Fixed a bug where ‘Not meeting host’ message was being returned even when the meeting was being updated by a host.

- Fixed a bug that allowed a deactivated user’s information to be updated via Update a User API.

- Fixed a bug where the values for meeting authentication settings were not being returned when the settings were disabled.

- Fixed a bug where **Update Live-streaming API** was not functioning as intended.

- Fixed a bug where multiple recording completed events were being sent when a recording was paused and resumed.

You can also see the update listed on our Changelog: [https://marketplace.zoom.us/docs/changelog](https://marketplace.zoom.us/docs/changelog)

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![chris.ota](https://avatars.discourse-cdn.com/v4/letter/c/e47c2d/32.png) [@chris.ota](https://devforum.zoom.us/u/chris.ota)\
**Post date:** [December 22, 2020, 10:54pm UTC](https://devforum.zoom.us/t/api-updates-12-21-20/39018/2 "2020-12-22T22:54:33Z")

</div>

Hi @tommy,

I think this latest API update may have introduced a new bug. After issuing a request to the `PATCH /v2/users/{userId}` endpoint, the `host_key` field for that user got erased even though it was not included in the request. This didn’t happen prior to today’s update.

Let me know if you need me to provide more info for this bug report.

-Chris

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [December 22, 2020, 10:58pm UTC](https://devforum.zoom.us/t/api-updates-12-21-20/39018/3 "2020-12-22T22:58:27Z")

</div>

Hey @chris.ota,

Yes, please provide more info here: #api-and-webhooks

Thanks for lettings us know,  
Tommy

---

<div class="post-metadata">

**Author:** ![chris.ota](https://avatars.discourse-cdn.com/v4/letter/c/e47c2d/32.png) [@chris.ota](https://devforum.zoom.us/u/chris.ota)\
**Post date:** [December 22, 2020, 11:19pm UTC](https://devforum.zoom.us/t/api-updates-12-21-20/39018/4 "2020-12-22T23:19:32Z")

</div>

Hi @tommy,

I’ve posted in the other forum: [Updating a user is now deleting the host key following 12.21.20 update](https://devforum.zoom.us/t/updating-a-user-is-now-deleting-the-host-key-following-12-21-20-update/39044)

---

<div class="post-metadata">

**Author:** ![rval](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/rval/32/6329_2.png) [@rval](https://devforum.zoom.us/u/rval)\
**Post date:** [December 23, 2020, 11:38am UTC](https://devforum.zoom.us/t/api-updates-12-21-20/39018/5 "2020-12-23T11:38:52Z")

</div>

I am getting the response like

{#2248 ▼  
+“code”: 300  
+“message”: “Unable to unlink API user(s).”  
}

When Deleting a User via API.

Please clarify about this validation message that you have updated recently

---

<div class="post-metadata">

**Author:** ![chris.ota](https://avatars.discourse-cdn.com/v4/letter/c/e47c2d/32.png) [@chris.ota](https://devforum.zoom.us/u/chris.ota)\
**Post date:** [December 23, 2020, 3:59pm UTC](https://devforum.zoom.us/t/api-updates-12-21-20/39018/6 "2020-12-23T15:59:18Z")

</div>

@rval, I was getting the same error because I forgot to include the `action` parameter. Adding action=delete to my request solved it.

---

<div class="post-metadata">

**Author:** ![berk](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/berk/32/14353_2.png) [@berk](https://devforum.zoom.us/u/berk)\
**Post date:** [December 24, 2020, 12:56am UTC](https://devforum.zoom.us/t/api-updates-12-21-20/39018/7 "2020-12-24T00:56:53Z")

</div>

@tommy The new update seems to have caused all TIMELINE files to not be exposed in the [Get Recording Meetings](https://marketplace.zoom.us/docs/api-reference/zoom-api/cloud-recording/recordingget) endpoint. I tested this out with a few meetings for which we used to get the TIMELINE file previously (according to our logs).

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [December 28, 2020, 7:29pm UTC](https://devforum.zoom.us/t/api-updates-12-21-20/39018/8 "2020-12-28T19:29:34Z")

</div>

Hey @berk,

Please see my post here relating to the TIMELINE file issue:

> [@Can no longer retrieve TIMELINE file](https://devforum.zoom.us/t/can-no-longer-retrieve-timeline-file/39117/3):
>
> Hey @berk, Sorry to hear about the TIMELINE file issues. We have identified the bug and are fixing it as soon as possible, most likely early Jan. (ZOOM-230716) Thanks, Tommy

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [December 28, 2020, 7:29pm UTC](https://devforum.zoom.us/t/api-updates-12-21-20/39018/9 "2020-12-28T19:29:53Z")

</div>

Happy to hear you sorted out the issue @chris.ota! 🙂

-Tommy

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [December 28, 2020, 7:30pm UTC](https://devforum.zoom.us/t/api-updates-12-21-20/39018/10 "2020-12-28T19:30:28Z")

</div>

Hey @rval,

Can you create a new topic here: #api-and-webhooks and fill out the post template so we have enough information to help? 🙂

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [January 4, 2021, 7:30pm UTC](https://devforum.zoom.us/t/api-updates-12-21-20/39018/11 "2021-01-04T19:30:41Z")

</div>

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
