#skarmoryman_api
acoustic mountainBOT
👋 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/1441442529416577024
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
ornate garnet
Hi there! Juggling a couple of threads, will look into this momentarily to verify
(off the top of my head, it's pretty interesting if it does work, but I'd be a little hesitant to rely on an undocumented feature, to be safe I would just write a loop or list comprehension in Python and not rely on it)
upper isle
ok thanks, this is what stripe ai told me for reference You're right—the official documentation for the List Disputes endpoint does not mention a status filter. The API reference only lists filters for charge and payment_intent. However, in practice, the Stripe Python SDK and API do accept a status parameter when listing disputes, even though it's not documented. This is a case where the API supports more functionality than is described in the docs.
acoustic mountainBOT
solemn igloo
hello, yeah don't know what the history behind that was (whether we ever allowed that publicly or deprecated that at some point) but my rule of thumb is: if it isn't public then you shouldn't rely on it. It may work but at some point, it may stop, there's no guarantee
quickly checked and stripe-ruby doesn't have status on Disputes List either
upper isle
ok thanks