403 nginx on wigle api

[flabberbabber]

I'm trying to integrate wigle from my business where I have to use a proxy to reach the internet. For every url I try on api.wigle.net I'm getting a 403 nginx response screen, even for trying to access the swagger page or pages that should return a 404.

I'm having doubts if the 403 nginx screen is comming from wigle or if my IT department is messing up. While curling I'm able to retrieve the wigle certificate just fine, but anything after that results in a 403. Could someone tell me if wigle even has this nginx 403 screen?

[arkasha]

It's possible that something about your account or connection was flagged as a violation of our terms. If you're attempting to use WiGLE data for business/commercial purposes without a commercial license, that makes perfect sense.

You're welcome to reach out to the admins with your IP address, connection details, and use case at the email address at the bottom of every page on the site, but since this is potential abuse/violation of the EULA to which you agreed when you signed up for your account, we won't be debugging (or providing tips to potential abusers) on the forums.

-ark