joschi_api

[twin smelt]

👋 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/1359091234513092678

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[misty whale]

hi there!

if you make a request and get back an error, then make the same request with the same idepotency key, they you'll get back the exact same error. instead you need to change the idempotency key.

[modest mountain]

Got it, thanks! I was under the impression that the idempotency keys could also be used when we got an error response first.

[modest mountain]

We're using the exact same request parameters between retries, though. Same payload, same timestamps, everything.

This is probably why the error message threw me off a bit:

Keys for idempotent requests can only be used with the same parameters they were first used with.

[misty whale]

yes you can only use idempotency keyswith the exact same parameters. but then you will also get the exact same reponse from Stripe. so if you got an error back, then make sure you change the idempotency key

[modest mountain]

But this I don't understand. If the previous request was rate-limited and I retry the exact same request after some cooldown period, it should not be rate-limited even when using the same idempotency key, no?

[misty whale]

that's not howidempotency keys work