08-26-2026 09:07 AM
We have an org with 15 networks. We're calling the following endpoint to pull some wireless event detail (client associations):
https://developer.cisco.com/meraki/api-v1/get-network-events/
However, one a few of our networks (but not all), the clientMac is null on the returned data, whereas on most networks, its populated as documented.
Before I raise with support, does anyone know of any reason why? It knows the client, as it does have the clientId - and if I look at this clientId in the dashboard it shows me the client mac!
Example response:
{
"message": null,
"pageStartAt": "2026-08-26T13:54:15.596596Z",
"pageEndAt": "2026-08-26T13:57:47.940308Z",
"events": [
{
"occurredAt": "2026-08-26T13:57:20.321909Z",
"networkId": "L_xxx",
"type": "association",
"description": "802.11 association",
"clientId": "k83xxx",
"clientDescription": null,
"clientMac": null,
"category": "80211",
"deviceSerial": "xxx",
"deviceName": "xxx",
"ssidNumber": 0,
"ssidName": "xxx",
"eventData": {
"channel": "6",
"rssi": "37"
}
},
{
"occurredAt": "2026-08-26T13:57:19.848129Z",
"networkId": "L_xxx",
"type": "association",
"description": "802.11 association",
"clientId": "k40xxx",
"clientDescription": "xxx",
"clientMac": null,
"category": "80211",
"deviceSerial": "xxx",
"deviceName": "xxx",
"ssidNumber": 0,
"ssidName": "xxx",
"eventData": {
"channel": "112",
"rssi": "36"
}
},
{
"occurredAt": "2026-08-26T13:57:15.754595Z",
"networkId": "L_xxx",
"type": "association",
"description": "802.11 association",
"clientId": "k4bxxx",
"clientDescription": null,
"clientMac": null,
"category": "80211",
"deviceSerial": "xxx",
"deviceName": "xxx",
"ssidNumber": 0,
"ssidName": "xxx",
"eventData": {
"channel": "161",
"rssi": "38"
}
},
[snip]I checked over a 24 hour period and all 3,000+ records all return with a null clientMac.
What's more strange is that the same clientMac field is correctly returned for the "disassociation" event type, so it appears limited to "association" only.
Thanks,
James
08-26-2026 09:11 AM
I would lean toward this being a Meraki backend defect or network-specific backend issue rather than a configuration problem. So, I suggets you open a support case.
08-26-2026 09:51 AM
+1 for opening a support case.
08-26-2026 10:18 AM
Thanks both!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide