#sylar_best-practices
1 messages ¡ Page 1 of 1 (latest)
đ 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/1318952119314681986
đ 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.
Hello
When you say slug, do you mean a custom ID/text or something?
thats right. something that could reference the price inside my app without exposing its id (also usefull for SEO)
For example I have a list of "prices" (subscriptions) and I'd like to make it accessible as .../subscriptions/some_seo_name
Prices have a parameter called lookup_key which you can use for this purpose
https://docs.stripe.com/api/prices/create#create_price-lookup_key
Product objects unfortunately don't have anything as such. A workaround would be to pass in your own custom ID when creating the product object
https://docs.stripe.com/api/products/create#create_product-id
Yeah, I saw the property called "lookup_key", but I didnt see any API call / library method to retrieve the price object using this field, only its ID (or search)
You can use List All Prices endpoint and pass lookup key as a param - https://docs.stripe.com/api/prices/list#list_prices-lookup_keys
This is because the same lookup key can be used with multiple prices
Yeah, thats not the thing, so I guess its better to handle this stuff separately from the stripe api using my own API layer
Yup, that would give you more flexibility