search

seatgeek / api-support

A support channel for the SeatGeek Platform
9 stars 10 forks source link

API request fails when sending from localhost or Postman #161

Open ThirdEyeSqueegee opened 8 months ago

ThirdEyeSqueegee commented 8 months ago

The following request fails (HTTP 406) when sent through localhost or Postman:

https://api.seatgeek.com/2/events/?geoip=true&range=5mi&per_page=10&page=1&client_id=<...>&client_secret=<...>

The same request was working fine and returning the expected data until yesterday when it stopped working. The request continues to work as expected in the live version of my web app but it always fails with HTTP 406 when developing locally. There were no changes to my web app's code between the request working and erroring out, so I suspect it might be a server-side issue.

derickrn commented 8 months ago

Hello @ThirdEyeSqueegee 👋

Sorry for the late reply on the following, but we throw a 406 within our networking stack to filter out traffic that may be potentially malicious, related to a large sum of traffic within a short time (potential DoS) and so on.

To help us determine the case of why you were blocked at some point can you please provide your IP address which we can look further into this? As a side note we do have a global rate limit applied, please be wary and throttle your requests to our API endpoint as needed, thank you!