#warren_api

1 messages ¡ Page 1 of 1 (latest)

lucid kernelBOT
#

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

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

short hound
#

I am not sure if the API can access that but will double check and get back to you

#

Apologies for the delay, unfortuantely the API can't access that functionality at the moment but I can file feedback requesting it

dark stag
#

Please, we want to automate a number of our internal workflows and not having access to 100% of the UI's functionality has always gotten in our way, this is just another thing. So anything that can be done here would be really appreciated. Realistically the problem is:

  • Metadata properties do not show in the UI
  • Note adding is not supported via the API

we need alignment here, realistically we need both, but would settle for at least metadata visibility, the note adding via the API is a close second.

#

Thank you

short hound
#

Metadata does show up in our UI for most objects in our dashboard. Do you know a specific object that you aren't seeing it for?

dark stag
#

for most objects it does not

#

subscriptions is the big one for us

short hound
#

I see it on Customers, Subscriptions, Invoices, and Payment intents now

dark stag
#

oh

#

hmmm, let's see what we were still missing

#

hmmm, I do see it in invoices now as well, which was one of the troublesome ones in the past. It's possible we might be okay here

lucid kernelBOT
dark stag
#

let me go back to my team and see if there was a workflow which was problematic here

short hound
#

Absolutely, let us know what you hear back