#pablo_list-search
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/1283804941915263071
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- mr-pablo_api, 54 minutes ago, 12 messages
- mr-pablo_api, 3 hours ago, 10 messages
Search results for what exactly?
currently im working with https://docs.stripe.com/api/charges/search
Ah ok
Yeah there's not a cursor for the previous page
Recommend just using autopagination though: https://docs.stripe.com/api/pagination/auto
And holding on to the results so you don't have to keep paginating back and forth
i can't use auto pagination, as the data takes too long to fetch
i have to use a limit and the next_page token
Where can i make suggestions for API improvements?
any other recommendations on how to implement this? its a proxy api for stripe, so basically any of the stripe endpoints, i need to create a proxy version, where we pass query params etc through where needed.
without a "previous_page" token, i guess we can't actually load a new page of results, and instead need to just append the list of results and fudge it pretty much?
Why do you need to paginate backwards? I don't understand the use-case exactly
typically, for paginated results, you want to only show a single page, eg page 3 or 4. you would then have links to go forwards and backwards between pages. This is pretty common pagination implementation
I put in the feature request
Again, no guarantees if it'll be implemented
There's not really a workaround though
We don't expose previous page cursor at all
Unless you're always starting the search at page 1
In which case, you can store the pages' cursors on your end
you do provide this in the listing endpoints, https://docs.stripe.com/api/charges/list
with starting_after and ending_before
Yeah not in the search api though
Does the search api give you something that list doesnt?
Because otherwise, I recommend just using the list api
potentially. i found that using List and trying to fetch a lot of records form the past day took a very long time. Was hoping Search was quicker.
Also, Search allows better "filtering" using the query, where as Lists pre-filtering is pretty basic