#lutzee-lookup-key
wind goblet
exotic wharf
@scenic hinge unfortunately yes, these are API-only right now 😦
scenic hinge
Is this on a roadmap for it to be added?
And is it considered safe to just use the price app_id instead? I've not found any guidance on whether we should be keeping these id strings (prod\_, price\_) private or not.
And some feedback from me is that the sample integration shouldn't be suggesting features that aren't easily accessible from the dashboard,
exotic wharf
I'm not sure of the roadmap but I completely agree we should do better here(and we need to document lookup_keys better).
The IDs like prod_xxx/price_xxx themselves are not sensitive and can't be used for anything without your secret API key, so you don't need to especially keep them private.
What is the "app_id"? Do you mean the ID field here?
scenic hinge
App Id was here in the dashboard on the product info page, is this term not correct in the UI?
I can't read
API not App 🤦♂️
exotic wharf
ah API ID
yeah so you can't change that, usually
I can in my screenshot because my account has some legacy behaviour
I was kind of testing if you had it as well
scenic hinge
I didn't want to change it, just a different way of saying price id
exotic wharf
anyway it's legacy and discouraged since setting your own ID causes performance problems. So the correct approach is lookup keys! But the dashboard doesn't support them :/
but yes you can store the price_xxx in your database and look it up manually , that's totally fine too.
scenic hinge
I've managed to change the lookup_key with the CLI now, just would be nice to do it in the dashboard, it is only one text field after all