Different requests returning the exact same response

[rdlauer]

I just started developing an app around the SeatGeek API and I noticed that sending two different requests (one after the other) is returning the same response (the response from the first request). This feels like some strange throttling/caching issue, but really kind of makes app development impossible! Just wondering if this is a known issue? I literally starting using the API yesterday and have submitted no more than 100 requests total, so I can't imagine I've hit any rate limit.

Also to protect the client id/secret I would be issuing all requests from the same server (instead of directly from the client). Since the rate limit isn't documenting I'm kind of nervous about using this API in production.

[rdlauer]

FYI a couple days later this has not seemingly been an issue since 🤷