# Unintended Field returned in Get Meeting API

**URL:** <https://devforum.zoom.us/t/unintended-field-returned-in-get-meeting-api/75205>\
**Category:** API and Webhooks\
**Created:** [August 31, 2022, 3:22pm UTC](https://devforum.zoom.us/t/unintended-field-returned-in-get-meeting-api/75205 "2022-08-31T15:22:55Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ckarpyszyn2](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ckarpyszyn2/32/40279_2.png) [@ckarpyszyn2](https://devforum.zoom.us/u/ckarpyszyn2)\
**Post date:** [August 31, 2022, 3:22pm UTC](https://devforum.zoom.us/t/unintended-field-returned-in-get-meeting-api/75205/1 "2022-08-31T15:22:56Z")

</div>

Calling meetings/{meetingUUID}/recordings?include\_fields=download\_access\_token

is suddenly returning a new, undocumented field `recording_play_passcode`

This is breaking a production app because it is unexpected and wasn’t occurring prior to today. Is this field expected, was there an update?

---

<div class="post-metadata">

**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\
**Post date:** [August 31, 2022, 6:12pm UTC](https://devforum.zoom.us/t/unintended-field-returned-in-get-meeting-api/75205/2 "2022-08-31T18:12:03Z")

</div>

Hi @ckarpyszyn2 ,

It was shared in the changelog here for Meeting API - June 21, 2022 updates: [Changelog](https://marketplace.zoom.us/docs/guides/stay-up-to-date/changelog/)

Thank you,  
Gianni

---

<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:** [September 4, 2023, 9:48am UTC](https://devforum.zoom.us/t/unintended-field-returned-in-get-meeting-api/75205/3 "2023-09-04T09:48:31Z")

</div>

Closed on September 4, 2023, 9:48am UTC

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