Oddities and bugs in webhooks

API and Webhooks
1
  1. Duration is rather large…
{
    "event": "meeting.created",
    "payload": {
        "account_id": "SG7cyaTzRoqSEyRnb4Djeg",
        "operator": "xx",
        "operator_id": "_jneLUhhQTmF09bdksDaiQ",
        "object": {
            "uuid": "i07xafRQT+OLz+P/XHQHEQ==",
            "id": 436623359,
            "host_id": "_jneLUhhQTmF09bdksDaiQ",
            "topic": "Zoom Meeting",
            "type": 1,
            "duration": 808529459
        }
    }
}

What use is that number to me?

  1. Meeting ended event provides the start_time, not end_time
{
    "event": "meeting.ended",
    "payload": {
        "account_id": "SG7cyaTzRoqSEyRnb4Djeg",
        "object": {
            "duration": 808529459,
            "start_time": "2019-09-27T12:00:40Z",
            "timezone": "",
            "topic": "Zoom Meeting",
            "id": "436623359",
            "type": 1,
            "uuid": "i07xafRQT+OLz+P/XHQHEQ==",
            "host_id": "_jneLUhhQTmF09bdksDaiQ"
        }
    }
}

Again the duration is wildly inaccurate. If it was correct, I could deduce the end time. Because of these 2 bugs I must fetch the past meeting instance.

  1. Hooks seem to be re-sent hours later?
{
    "event": "recording.resumed",
    "payload": {
        "account_id": "SG7cyaTzRoqSEyRnb4Djeg",
        "object": {
            "uuid": "ypsgTTsBRrKONekWUNjZgg==",
            "id": 536849397,
            "host_id": "_jneLUhhQTmF09bdksDaiQ",
            "topic": "Zoom Meeting",
            "type": 1,
            "start_time": "2019-09-27T12:35:05Z",

This meeting ended 2h ago. Why am I getting this event just now?

2

Hi @jimig,

Happy to Help.

Can you please confirm the following?

We are also currently investigating if this was a bug within our system.

We have taken your feedback under consideration, and have decided to include this field within the event. I have added this as a feature request within our system (ID: ZOOM-112120) and sent it to the engineering team. The “end_time” field will be added to this event in one of our future releases. Please follow our changelog for further updates.

After receiving a notification, your Event Notification Endpoint URL should respond with either a 200 or a 204 HTTP status code within three seconds for Zoom to consider that the notification was successfully delivered. Zoom will try to deliver the notification for up to three times for an event.

Can you confirm that you sent a response to Zoom after the notification was delivered to you?

For more information, please visit: https://marketplace.zoom.us/docs/api-reference/webhook-reference#notification-delivery

Thanks,
Ojus

1 Like
3

Hi Ojus,

Thanks for taking a look.

With 1, yes it was instant (I guess this means the PMI is used implicitly). It was created in the Zoom client.

2, I can now see the webhook is updated, thanks!

  1. I think we did respond with a 204, but this was rather delayed. That would explain it.
5

Hey @jimig,

We are looking into this and will get back to you next week! :slight_smile:

Thanks,
Tommy