Neophyte
ProfessorThat is not the limit I was referring to. Each api endpoint has a defined number of calls allowed in a defined period of time.
Here is an example of my how my python function evaluates the api limits.
returned_headers = response.headers
api_limit = int(returned_headers['x-rate-limit-limit'])
api_left = int(returned_headers['x-rate-limit-remaining'])
api_threshold = api_limit - api_left
if api_threshold > 5:
time.sleep(int(returned_headers['x-rate-limit-window']))
How long until they build pagination into the SDK?
ProfessorHonestly, I don't use the SDK as I always had odd results on items returning differently sometimes. So I wrote my own Python function that handles pagination, api limitations, etc and returns it always in the same manner.
Yes, i have one of those too. But the SDK should include it.
The problems you've had have been around filtering and returning specific columns, right? I've also had weird situations where a call shouldn't require a value but it does. Like if you're patching the display name, you also have to include a couple other fields. The code under the hood of the SDK doesn't handle it on some methods.
LM, please open source your SDK and put it into github so we can submit pull requests and "make LM friendly to the developers." (your words not mine).
ProfessorYeah, filtering was a huge pain. And whatever version I was using awhile ago, would change the returned columns between snake case and something else randomly I believe.
