Originally posted by gordonb3
View Post
However watchforstock's python library only has a debug mode which will show the HTTP response for the V2 API, the V1 API call failing just results in an unhelpful uncaught python exception, so I don't know what the actual returned error is for the V1 API when it fails. However both API's seem to fail or succeed at the same time suggesting that there is shared rate limiting between them. If I manually spam queries to one API I then immediately get failures on the other API even though they use different URL's.
Comment