Wireless Client Health Scores = b''

Solved
AidanVenn
Here to help

Wireless Client Health Scores = b''

Hello,

 

Running

 

VisStudio 1.77.3 on windows 11
Meraki Library version 1.32.1
Python 3.10

Meraki AP: MR36

Firmware 17.10.4

 

I am attempting to run - https://developer.cisco.com/meraki/api-v1/#!get-network-wireless-clients-health-scores

 

This gives back wireless clients health scores

 

The code is below:

 

url = "https://api.meraki.com/api/v1/networks/XXXXXXX/wireless/clients/healthScores"

payload = None

headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"X-Cisco-Meraki-API-Key": API_KEY
}

response = requests.request('GET', url, headers=headers, data = payload)

 

print(response.text.encode('utf8'))

 

However I get the output of:

 

b'' - in visStudio

 

and Error 404 Not Found in the developer hub test environment.

 

The API and network appear to work fine on other scripts.

 

Any ideas what's wrong?

 

Many Thanks

 

Aidan

1 Accepted Solution
sungod
Kind of a big deal

This is an Early Access API call, have you enabled EA on the organization?

 

I suspect not, which would explain the 404.

 

See...

 

https://developer.cisco.com/meraki/api-v1/#!api-reference-early-access-overview

View solution in original post

4 Replies 4
PhilipDAth
Kind of a big deal
Kind of a big deal

We need @sungod for this one ...

 

If you are using the Meraki library - why are you using requests directly?

RaphaelL
Kind of a big deal
Kind of a big deal

I will check the results on my end. 

 

On a side note , you have included a firmware ( MX ) that has no influence on your issues. What MR firmware are you running ?

AidanVenn
Here to help

Good point! MR fw is 29.5.1 - latest and greatest...

sungod
Kind of a big deal

This is an Early Access API call, have you enabled EA on the organization?

 

I suspect not, which would explain the 404.

 

See...

 

https://developer.cisco.com/meraki/api-v1/#!api-reference-early-access-overview

Get notified when there are additional replies to this discussion.