# Wrong MAC address in dashboard /metrics/meetings API responses

**URL:** <https://devforum.zoom.us/t/wrong-mac-address-in-dashboard-metrics-meetings-api-responses/135361>\
**Category:** Meetings\
**Created:** [July 17, 2025, 3:01pm UTC](https://devforum.zoom.us/t/wrong-mac-address-in-dashboard-metrics-meetings-api-responses/135361 "2025-07-17T15:01:12Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![ucczoomaruba](https://avatars.discourse-cdn.com/v4/letter/u/e56c9b/32.png) [@ucczoomaruba](https://devforum.zoom.us/u/ucczoomaruba)\
**Post date:** [July 17, 2025, 3:01pm UTC](https://devforum.zoom.us/t/wrong-mac-address-in-dashboard-metrics-meetings-api-responses/135361/1 "2025-07-17T15:01:12Z")

</div>

**API Endpoint(s) and/or Zoom API Event(s)**

> **[Accounts APIs](https://developers.zoom.us/docs/api/accounts/#tag/dashboards/GET/metrics/meetings/%7BmeetingId%7D/participants)**
>
> The Zoom Account APIs allow developers to programatically access data related to accounts, dashboards, information barriers, and roles.

> **[Accounts APIs](https://developers.zoom.us/docs/api/accounts/#tag/dashboards/GET/metrics/meetings/%7BmeetingId%7D/participants/%7BparticipantId%7D/qos)**
>
> The Zoom Account APIs allow developers to programatically access data related to accounts, dashboards, information barriers, and roles.

**Description**  
Sometimes, these above /metrics/meetings APIs provide wrong mac\_address in their responses i.e. I get mac\_addr=0000-0000-0000. And on other occasions I get proper value like mac\_addr, for e.g. cc15-cc15-cc15.  
Please check why these APIs sometimes give all zero mac\_address in participants’ details.

**Error?**  
Sample response partial data:  
{  
id=Cd…n6g,  
user\_id=16XXX264,  
participant\_uuid=71XXXX03-54BE-8262-A09D-3EXXXX8A313A,  
user\_name=N H,  
device=Windows,  
client=6.3.11.60501,  
ip\_address=134.224.141.113,  
internal\_ip\_addresses=[192.168.1.10],  
connection\_type=Reliable UDP,  
join\_time=2025-04-22T04:30:09Z,  
leave\_time=2025-04-22T04:35:54Z,  
pc\_name=DSF0EZVCGB,  
[domain=xx.hq.net](http://domain=xx.hq.net),  
mac\_addr=0000-0000-0000,  
version=6.3.11.60501  
…  
}

**How To Reproduce**  
_Steps to reproduce the behavior:_  
_1. Onboard a Zoom account having multiple users to a General App in marketplace_  
_2. Complete the OAuth process to get access token to execute the above mentioned APIs_  
_3. Subscribe to meeting.ended events_  
_4. Start a meeting from user1 and let user2 join the meeting through the zoom link. And then end the call after 4-5 mins_  
_5. meeting.ended event is received at the webhook callback URL with meeting id_  
_6. Using this meeting id make above mentioned metrics/meetings calls_

Info:  
Zoom client version: 6.3.11.60501

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [July 22, 2025, 6:35pm UTC](https://devforum.zoom.us/t/wrong-mac-address-in-dashboard-metrics-meetings-api-responses/135361/2 "2025-07-22T18:35:53Z")

</div>

Hi @ucczoomaruba  
Would you happen to have a sample response body and its tracking ID for this issue?  
I have been trying to reproduce this on my end and I am always getting a proper value for mac\_addr

---

<div class="post-metadata">

**Author:** ![ucczoomaruba](https://avatars.discourse-cdn.com/v4/letter/u/e56c9b/32.png) [@ucczoomaruba](https://devforum.zoom.us/u/ucczoomaruba)\
**Post date:** [July 23, 2025, 7:45am UTC](https://devforum.zoom.us/t/wrong-mac-address-in-dashboard-metrics-meetings-api-responses/135361/3 "2025-07-23T07:45:40Z")

</div>

Hi @elisa.zoom  
I couldn’t reproduce the issue of all zeros MAC again today when I tested few times today.  
However I saw an empty MAC for one of the user/client which was on an iPhone device. Is this an expected thing of empty MAC if the user is logged in and joined the meeting from a mobile device?

I will test again to check the all zeros MAC btw.

---

<div class="post-metadata">

**Author:** ![ucczoomaruba](https://avatars.discourse-cdn.com/v4/letter/u/e56c9b/32.png) [@ucczoomaruba](https://devforum.zoom.us/u/ucczoomaruba)\
**Post date:** [July 25, 2025, 2:21pm UTC](https://devforum.zoom.us/t/wrong-mac-address-in-dashboard-metrics-meetings-api-responses/135361/4 "2025-07-25T14:21:52Z")

</div>

Hi @elisa.zoom

I was able to reproduce the issue multiple times today between 2 laptop clients. In fact, on the laptop for which I am seeing the “mac\_addr”: “0000-0000-0000” issue, I made sure to use the latest Zoom client (version: 6.4.12.64384).

Here is the sample response, the URL with meeting id and also the tracking ID:

```auto
https://api.zoom.us/v2/metrics/meetings/87080328066/participants?type=past
x-zm-trackingid:	v=2.0;clid=us06;rid=WEB_6fffa4ec770ac784344d4f6ea1f97be9
{
    "page_count": 1,
    "page_size": 30,
    "total_records": 2,
    "next_page_token": "",
    "participants": [
        {
            "id": "<ID1>",
            "user_id": "<UID1>",
            "participant_uuid": "9176AA1A-<...>-EA6AF239AFEE",
            "user_name": "zoom ucc",
            "device": "Windows",
            "client": "6.4.12.64384",
            "ip_address": "136.226.243.2",
            "internal_ip_addresses": [
                "192.168.1.24"
            ],
            "location": "Chennai (IN)",
            "network_type": "Wifi",
            "microphone": "Microphone Array (Intel® Smart Sound Technology for Digital Microphones)",
            "speaker": "Speakers (Realtek(R) Audio)",
            "camera": "HP HD Camera",
            "data_center": "India (HYD Top)",
            "full_data_center": "India (HYD Top);",
            "connection_type": "P2P",
            "video_connection_type": "P2P",
            "as_connection_type": "P2P",
            "join_time": "2025-07-25T14:00:50Z",
            "leave_time": "2025-07-25T14:04:33Z",
            "share_application": false,
            "share_desktop": false,
            "share_whiteboard": false,
            "recording": false,
            "pc_name": "<PC1>",
            "domain": "<DOMAIN1>",
            "mac_addr": "0000-0000-0000",
            "harddisk_id": "",
            "version": "6.4.12.64384",
            "leave_reason": "zoom ucc left the meeting.<br>Reason: Host ended the meeting.",
            "email": "<EMAIL1>",
            "audio_quality": "good",
            "video_quality": "good",
            "screen_share_quality": "",
            "registrant_id": "",
            "status": "in_meeting",
            "os": "win",
            "os_version": "10+ 19045",
            "browser_name": "",
            "browser_version": "",
            "device_name": "",
            "groupId": "",
            "health": "Good",
            "customer_key": "",
            "sip_uri": "",
            "from_sip_uri": "",
            "role": "host",
            "participant_user_id": "<PUID1>",
            "audio_call": [
            ],
            "has_archiving": false,
            "optional_archiving": "no optional archiving"
        },
        {
            "id": "<ID2>",
            "user_id": "<UID2>",
            "participant_uuid": "83B4D30E-<...>-FB3F303DEEC5",
            "user_name": "Naveen...",
            "device": "Windows",
            "client": "6.4.12.64384",
            "ip_address": "61.246.230.194",
            "internal_ip_addresses": [
                "10.96.241.40"
            ],
            "location": "(IN)",
            "network_type": "Wired",
            "microphone": "Microphone (Realtek High Definition Audio)",
            "speaker": "Speaker/Headphone (Realtek High Definition Audio)",
            "camera": "HP TrueVision HD",
            "data_center": "India (HYD Top)",
            "full_data_center": "India (HYD Top);",
            "connection_type": "P2P",
            "video_connection_type": "P2P",
            "as_connection_type": "P2P",
            "join_time": "2025-07-25T14:01:12Z",
            "leave_time": "2025-07-25T14:04:33Z",
            "share_application": false,
            "share_desktop": false,
            "share_whiteboard": false,
            "recording": false,
            "pc_name": "<PC2>",
            "domain": "",
            "mac_addr": "80ce-62a6-26a8",
            "harddisk_id": "",
            "version": "6.4.12.64384",
            "leave_reason": "Naveen... left the meeting.<br>Reason: Host closed the meeting. ",
            "email": "<EMAIL2>",
            "audio_quality": "good",
            "video_quality": "good",
            "screen_share_quality": "",
            "registrant_id": "",
            "status": "in_meeting",
            "os": "win",
            "os_version": "10+ 19045",
            "browser_name": "",
            "browser_version": "",
            "device_name": "",
            "groupId": "",
            "health": "Good",
            "customer_key": "",
            "sip_uri": "",
            "from_sip_uri": "",
            "role": "attendee",
            "participant_user_id": "PUID2",
            "audio_call": [
            ],
            "has_archiving": false,
            "optional_archiving": "no optional archiving"
        }
    ]
}

```

Please check and get back.

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [July 28, 2025, 2:03pm UTC](https://devforum.zoom.us/t/wrong-mac-address-in-dashboard-metrics-meetings-api-responses/135361/5 "2025-07-28T14:03:24Z")

</div>

Thanks @ucczoomaruba  
I created an internal ticket for our engineering team about this (ZSEE-174483)

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [July 29, 2025, 1:35pm UTC](https://devforum.zoom.us/t/wrong-mac-address-in-dashboard-metrics-meetings-api-responses/135361/6 "2025-07-29T13:35:29Z")

</div>

Hi @ucczoomaruba  
Thank you so much for your patience here and for reporting this issue.  
Our engineering team has identified this on our end and we are working on fixing this on our next release. I am waiting to hear back from the team with an estimated date

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [July 31, 2025, 8:06pm UTC](https://devforum.zoom.us/t/wrong-mac-address-in-dashboard-metrics-meetings-api-responses/135361/7 "2025-07-31T20:06:31Z")

</div>

Hi @ucczoomaruba  
I have an update on this issue. The fix is planned for our **September release**.

In the meantime, our Engineering team suggests checking whether **NetBIOS is disabled** on the affected machine. If NetBIOS is disabled, the `mac_address` value will return as all zeros. Currently, the Zoom client cannot retrieve the MAC address when joining a meeting if NetBIOS is turned off, so if you could enable this on the affected machine while we work on this fix

---

<div class="post-metadata">

**Author:** ![ucczoomaruba](https://avatars.discourse-cdn.com/v4/letter/u/e56c9b/32.png) [@ucczoomaruba](https://devforum.zoom.us/u/ucczoomaruba)\
**Post date:** [August 8, 2025, 11:07am UTC](https://devforum.zoom.us/t/wrong-mac-address-in-dashboard-metrics-meetings-api-responses/135361/8 "2025-08-08T11:07:06Z")

</div>

Thanks @elisa.zoom for the update.

I will check this NetBIOS setting in the machine and keep a watch.
