Error updating BSSIDs with wildcard via API

Using https://api.zoom.us/v2/phone/locations/<location_id>, I’m getting “BSSID format error” when trying to update a location and using BSSIDs with wildcards.

Update I’m PATCHing:
{
“bssid”: “b5:a8:67:d1:b8:d*”
}

Using the above gets me a “400 Bad Request” with the message “BSSID format error.”

I can update the same location using BSSIDs that don’t have a wildcard.
{
“bssid”: “b5:a8:67:d1:b8:d0”
}

I suspect this is a data validation bug in the API. Anybody else run into this?

1 Like

Hi @sosherof
Thanks for reaching out to us and welcome to our Developer Community!
I am happy to help here!
Allow me to do some testing on my end and I will get back to you with an update soon

Hi @sosherof
Hope you are doing fine!
I am not able to replicate this issue on my end. Are you still getting this 400 Bad request? If so, please let me know so I can take a closer look into this

I’m still getting the error. I’m testing with postman using this URL:
PATCH https://api.zoom.us/v2/phone/locations/<location_id>
and sending the JSON data:
{
“bssid”: “b0:ba:67:d1:b8:d*”
}
This gets me back this reply:
{
“code”: 400,
“message”: “BSSID format error.”
}

The above BSSID works in the web UI. Additionally, there’s an error in the documentation for this PATCH method. The example data uses a BSSID that is definitely the wrong format.

I’d be happy to screen share with you but not sure how to get you my contact details.
-Sam

Hi @sosherof
I will send you a private message to follow up on this !

In case others make it here, this issue was fixed on 2023-01-16.

1 Like

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.