#nt_api
boreal condorBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1258018692583653436
đ Have more to share? Add details, code, screenshots, videos, etc. below.
gaunt berry
Something to add, some subscriptions that were migrated are missing from the auto paginated search, but others are present. Out of 209 migrated subscriptions, 117 are missing and the rest are returned correctly. So we don't think that is an issue with how subscriptions were scheduled via the migration toolkit.
gaunt obsidian
Out of 209 migrated subscriptions, 117 are missing and the rest are returned correctly
Do they fit the search criteria? e.g.status: 'active'
Otheriwse, re: search issues, I suspect it'll be better for you to write in so we can take a deeper look into this really. If you can include the JSON responses from the GET requests too (as we don't log them)
https://support.stripe.com/contact/email?topic=api_integration
gaunt berry
Yes they fit the criteria. If I filter the subscriptions in my dashboard with status active, I get 667 subscriptions. Via the auto pagination API, I get significantly less. I would avoid including logs form those searches tbh..
gaunt obsidian
We can't really verify the results of the searches without you providing the JSON returned
I get there's likely sensitive PII in that JSON, hence why I recommended writing in
gaunt berry
ok will write an email thanks.
gaunt obsidian
thank you!
gaunt berry
I suspect you need one JSON response. Not every response from the search pagination