#hendie_api
cinder runeBOT
đ 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/1371989539542925473
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
wheat igloo
Hi! So a 500 means an issue on Stripe's side. We talk about how to handle them here: https://docs.stripe.com/error-low-level#server-errors
silk canopy
OK, but since it said it was an api_error is there a possibility that we passed wrong paramters to the endpoint? It would be useful to know what, so we can avoid it in future?
wheat igloo
Sure, it's possible that something on Stripe's end failed and returned a 400 before we could respond to you with a 400 indicating wrong parameters, but since it never got that far, it's impossible to know.
When this happens, you'll need to compare the state of your data with that in Stripe for that particular object to make sure they line up (and adjust as necessary).
I guess my point there is just: there's really no way to know, but even if it's something you did, it's still something we would need to fix on our end, and the original request is in a state of "maybe some of it did something", so it requires investigation to make sure your system and Stripe are in sync.
cinder runeBOT