#david2_api
timber muralBOT
👋 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/1317182437834362981
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
forest shuttle
^ humorous contradictory google result
gritty cove
Taking a look now! Need to double check a few things before I can get a definitive answer to you. And yeah that screenshot is pretty good, AI is always afraid to say no 😅
The second answer here is the correct one - for most IDs they are globally unique, but there are exceptions, in cases where we give users the ability to define their own key.
For example, if you create a coupon and don't provide your own ID, we auto generate one for you. This isn't guaranteed to be globally unique.
https://docs.stripe.com/api/coupons/create#create_coupon-id
So the general recommendation would be to assume that IDs are not globally unique and track which account they came from when relevant.
forest shuttle
good deal. is there official stripe documentation (not an answer on google groups, or ephemeral discord q/a) that I can point my co-workers to (and myself, in the future...)?
gritty cove
I don't believe we have anything that addresses this exact question in the docs unfortunately.
forest shuttle
ah that's too bad. well, thank you for your time!
gritty cove
No worries, have a good one!