#vytal_api

1 messages · Page 1 of 1 (latest)

spiral wharfBOT
#

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

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

icy storm
#

Hello, I am taking a look 🙂

#

The request you shared happened at 2026-03-04 14:30:37 UTC and is a replay meaning it has the same idempotency key as req_bYj1HPzjKdSir8 which happened at 2026-03-04 14:24:00 UTC. Did you change access before both of these timestamps?

west hornet
#

Only changed access sometime between the initial and the latest request

#

Tried a at 14:41:03 with this request as well req_CeUmZvGJlutl4Y

icy storm
#

That is also a replay with the same idempotency key. Can you try a request with a new key? According to our docs: https://docs.stripe.com/api/idempotent_requests

Stripe’s idempotency works by saving the resulting status code and body of the first request made for any given idempotency key, regardless of whether it succeeds or fails. Subsequent requests with the same key return the same result, including 500 errors.