API Dashboard "Return a client" GET doesn't works

[antoniogrillo]

Hi,

try to use postman for this GET via Dashboard API but doesn't works, some ideas?

GET Return a client

https://api.meraki.com/api/v0/networks/{{networkId}}/clients/{{clientMac}}
Return the client associated with the given identifier. This endpoint will lookup by client ID or either the MAC or IP depending on whether the network uses Track-by-IP.

All the GET without "clientMac" variable works perfectly.

https://documenter.getpostman.com/view/897512/meraki-dashboard-api/2To9xm#intro

Some ideas?

[hody.crouch]

Try adding the timespan parameter to your URL.

https://api.meraki.com/api/v0/networks/{{networkId}}/clients/{{clientMac}}?timespan=7200

[hody.crouch]

I take that back. I can't get this new API to work either.

I've had success in the past with the similar API

/api/v0/devices/[serial]/clients?timespan=7200

This returns all devices connected to a specified device. You would call this API for each device in a network.

[antoniogrillo]

@hody.crouch

Yes, this work also for me, in fact there isn't client variable.

I need with a single call GET identify a mac-address client if i know its IP Address.

If i search in a client list i need a DB for scanning the data...

[psteinbe]

I haven't had an issue with new the API call. Can you post your results?

This is the get request from my Postman "{{baseUrl}}/networks/{{networkId}}/clients/{{clientMac}}"

[antoniogrillo]

@psteinbe

for you works also if you put the IP address in clientmac variable?

[psteinbe]

@antoniogrillo

I don't track my clients by IP. You need to turn that on.

see documentation:

https://documentation.meraki.com/MX-Z/Monitoring_and_Reporting/Client_Tracking_Options

FYI, I tried to test tracking by IP and got the following error:

• Tracking clients by IP addresses is not supported in a combined network and will break client tracking data.

[Stephen Rodriguez]

I read that:
"Return the client associated with the given identifier. This endpoint will lookup by client ID or either the MAC or IP depending on whether the network uses Track-by-IP."

the way I read this:
1) We should always be able to poll for the client ID
2) poll via mac or IP, is based on Client Tracking.

I'm tracking by Mac and not IP as well, so I should be able to do a call with the client Mac address and have that return. It does not.

I should be always able to make the call and use the client ID and have that return, it does not.

[antoniogrillo]

may be the call function isn't activate yet ??

[psteinbe]

The clientMac has to be in the same networkId. I have searched for a mac that was not in the network I had set in my variables and it returned a 404.

[antoniogrillo]

@psteinbe

Hi, the clients are in the same networkId, i put the IP from this other GET call....

[psteinbe]

@antoniogrillo

Can you show me your Security Appliance/Addressing & Vlans page?

[Stephen Rodriguez]

@psteinbe it shouldn't matter what your tracking is set to, as long as you are calling the correct element. If you are tracking by Mac, you call the client Mac. if you are tracking by IP, you call the client IP. but you should *always* be able to call the client ID. I just tested this both with track Mac and track IP and I get a 404 error either way I try to test it.

[Stephen Rodriguez]

I've reached out to the SE that posted the meraki.py on Github to see if he can weigh in on this as well.

[psteinbe]

Works both ways for me.