#shanedjrogers - Auto-Pagination

1 messages · Page 1 of 1 (latest)

gritty basin
#

Hello! No, auto-pagination is a feature of our official server-side libraries and will make several list API calls behind the scenes if required.

#

It might be a single API request, but it could also be several.

kindred maple
#

Yeah ok gotcha, I was wondering what counts towards my rate limit capacity

#

So it seems like there are no shorcuts, every request whether manual or automatic from server lib internals will count against my 100 requests per second cap

gritty basin
#

Sorry I didn't see this earlier. That's correct. Are you currently hitting rate limits?

kindred maple
#

Not yet but I think I might, I am hitting the Stripe API on behalf of Connect customers, if their user base is large then I may hit them, trying to figure out a strategy for avoiding that

#

hit them === hit the rate limit

gritty basin
#

When Connect is involved different rate limits apply. It's highly unlikely you'll hit our rate limits unless you're doing something quite unusual. I recommend proceeding without worrying about rate limits until you actually hit them.

kindred maple
#

Oh what are the different rate limits with Connect?

#

I hadnt seen anything in the docs about that

vestal fulcrum
#

There is essentially a separate rate limit for each connected account. Paging through resources shouldn't take up too much of that either. You have to wait for each page before requesting the next one so that is pretty slow as far as the rate limit goes.

kindred maple
#

Ok good to know, thanks for the info, I'll deal with rate limits when they come up