#brel_best-practices
obtuse tideBOT
đ 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/1285244927110021234
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- brel_api, 36 minutes ago, 11 messages
crude pumice
Hello
Those object IDs are not sensitive, no. Only someone with access to your secret key can access them.
The only ID you should not pass/embed in your frontend is a Client Secret
So it is fine if you want to handle those object IDs on your frontend -- that is up to you
calm hearth
ok thank you!
I wanted to use lookup_keys instead but it seems that I cannot use them everywhere
For example I wanted to reference to my proce lookup key from my frontend but then I cannot use those to create a stripe subscription
crude pumice
Hmm not sure what you mean by that? The idea with lookup_key is that you still do call your backend but you don't have to make any backend updates.