# Webhook v2 recording\_files object different than API

**URL:** <https://devforum.zoom.us/t/webhook-v2-recording-files-object-different-than-api/1155>\
**Category:** API and Webhooks\
**Created:** [April 4, 2018, 7:06pm UTC](https://devforum.zoom.us/t/webhook-v2-recording-files-object-different-than-api/1155 "2018-04-04T19:06:58Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![TeachCast\_Admin](https://avatars.discourse-cdn.com/v4/letter/t/439d5e/32.png) [@TeachCast\_Admin](https://devforum.zoom.us/u/TeachCast_Admin)\
**Post date:** [April 4, 2018, 7:06pm UTC](https://devforum.zoom.us/t/webhook-v2-recording-files-object-different-than-api/1155/1 "2018-04-04T19:06:58Z")

</div>

Hello,

We’re implementing Zoom webhooks (using webhooks v2) to&nbsp;ingest recordings via the recording[s]\_completed event. The request body for a recording\_completed event has a recording\_files object, which is similar to the recording\_files object that is returned when calling the /meetings/{meetingId}/recordings route of the API. However, the webhook recording\_files object does not contain the “play\_url” attribute or “download\_url” attribute. Instead, it has a “file\_path” attribute. It would be very helpful if the recording\_files object provided by the webhook were standardized with the api. Specifically, we need the the “play\_url” attribute added to the webhook request body. As it stands now, when we receive a webhook for the recording\_completed event, we’ll have to then perform another call to the Zoom API to get the recording details, which are almost identical to the information already received through the webhook except that the play\_url is missing.

From this other post, below, it appears that this change my be forthcoming. Do you have an ETA?

[https://support.zoom.us/hc/en-us/community/posts/360000606503-Breaking-changes-to-webhook-payload-for-RECORDING-MEETING-COMPLETED-events?input\_string=Webhook%20v2%20recording\_files%20object%20different%20than%20API](https://support.zoom.us/hc/en-us/community/posts/360000606503-Breaking-changes-to-webhook-payload-for-RECORDING-MEETING-COMPLETED-events?input_string=Webhook%20v2%20recording_files%20object%20different%20than%20API)

Thanks for your assistance and for considering this request.

-Spencer

---

<div class="post-metadata">

**Author:** ![TimZoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/timzoom/32/978_2.png) [@TimZoom](https://devforum.zoom.us/u/TimZoom)\
**Post date:** [June 6, 2018, 6:06pm UTC](https://devforum.zoom.us/t/webhook-v2-recording-files-object-different-than-api/1155/2 "2018-06-06T18:06:16Z")

</div>

Thanks for the feedback!&nbsp;We are already talking about this internally. While I don’t have a timeline for release I personally believe the object should be exactly the same and will push for that change.&nbsp;

---

<div class="post-metadata">

**Author:** ![DeveloperBot](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/developerbot/32/12632_2.png) [@DeveloperBot](https://devforum.zoom.us/u/DeveloperBot)\
**Post date:** [August 21, 2020, 5:40pm UTC](https://devforum.zoom.us/t/webhook-v2-recording-files-object-different-than-api/1155/3 "2020-08-21T17:40:23Z")

</div>

Closed on August 21, 2020, 5:40pm UTC