#Dan(ClassFit)-express-request-limit
autumn lynx
Hey there
Following up on the above, stripe's rate limiter caps out at 100 read and 100 write operations per second
So unfortunately there's no way to increase the limit
would you mind sharing the exact information that you're looking to extract for the users so we can check if there are any alternatives.
fallow lark
I think @cunning cape is talking about the page size limit on the list endpoint?
to get more than 100 records, you have to paginate through the data cf https://stripe.com/docs/api/pagination
there isn't a way to make the pages bigger, though, if that's what you're after
gleaming shore
@cunning cape Does that cover your question? If you have questions about pagination we'd be happy to answer them
cunning cape
Ah sorry for the slow response"
In Stripe's standard dashboard, you allow for a CSV export of all payment data. This is really useful for people when doing their accounting. On the Express dashboard you don't offer anything like this, we need to build it ourselves, which we have done. However, the data we pull from Stripe seems to be limited to 100 lines.
So our Express dashboard looks like this
The CSV downloaded though seems to be restricted to only grabbing 100 lines of data from Stripe
As below but x100
This is pretty limiting as the accountants will need the full set of transaction data for the period.
gleaming shore
If you want the full list of data, you'd use auto-pagination https://stripe.com/docs/api/pagination/auto which will make additional requests until all the data has been retrieved
cunning cape
I understand the pagination concept for showing result in page, like on the first screenshot I've sent. Does this same concept apply to downloading a CSV file if we wanted for example 1000+ Lines?
gleaming shore
I assume so - I don't know what logic you have for generating the CSV, but I assume the issue is that it's only making a single request to retrieve the first page (100 lines) of data
fallow lark
like tbc, the suggestion is not to paginate the csv itself (ie: having the user download n 100-row csvs)
as karbi says, the idea is to have the logic on your side paginate through all the records with the API to get all of them, then generate a csv with all of them
cunning cape
Got it. Perfect. Thanks for your help.