#tamim-ikbal_api
1 messages ยท Page 1 of 1 (latest)
๐ Welcome to your new thread!
โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
๐ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1392498768481615932
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hello, can you tell me a bit more about what you mean by number based pagination? Looking in to if there is a good alternate way to get the total count of the entire list
I am talking about this type of pagination and this required total count.
1,2,3,4,5,6,7,8
๐
Gotcha, looking in to this
Thanks
Unfortunately not finding anything for this. It looks like we would expect you to page through the full list and get a count from that. I can file feedback about adding this field back but especially because we just removed it I can't promise if or when it could get added.
FWIW the search API still has this field (only accurrate up to 10,000 objects) but I'm not sure if that property is planned to go as well
https://docs.stripe.com/api/pagination/search#search_pagination-total_count
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Yes, i go you, because you guys are using cursor pagination and it's hard to imeplement page based there, because it's work with hashed
Yep, I think there isn't a good way to do this without having a cache of the objects that exist on your side
And it's helped with large dataset pagination.
I will include that in the feedback, that is definitely a helpful usecase that was broken by this change
Okay, Thanks.
Yes, one weird case, it's work on my production and don't in local, but both are same api "2024-06-20".
Interesting, can you send me the request IDs for each? That property should have only been removed in our 2025-03-31 version and later
https://docs.stripe.com/changelog/basil/2025-03-31/deprecate-total-count-expansion
I will surely send you later, At this moment I can't sorry, sir.
Sounds good, and to be clear you should be able to keep using total_count as long as you are using an older API version than that 2025-03-31 one. We shouldn't have broken your existing integration that was using an older version