WiGLE.net

Posted: **Fri Nov 29, 2019 1:00 pm**

Hi

Not sure if this is a bug in the API or im using it wrong... but if you try to do a search via the API for an SSID (netid) that starts with a hash for example '#Passpoint' then it returns way more data than it should, I see netid's that dont match that so assuming its the hash somehow?

Am I using it wrong?

Any advice

Many thanks

Chris

Posted: **Fri Nov 29, 2019 2:52 pm**

Posting a reply to my own issue, in the vague hope it helps others, through trial and error and reading about # it would appear anyone doing the same as me, needs to swap the # for %23

So instead of searching with for example "#Passpoint" try "%23Passpoint" (without the quotes) when using the API

Problem Solved

Have a great day.

Chris

Posted: **Sun Dec 01, 2019 6:53 pm**

sounds like you found the answer, but yes, url-encoding applies!

cheers, and thanks for your interest!

-ark

WiGLE.net

Using the API to search for a hash in an SSID

Using the API to search for a hash in an SSID

Re: Using the API to search for a hash in an SSID

Re: Using the API to search for a hash in an SSID