#deathnfudge_api

1 messages ¡ Page 1 of 1 (latest)

vapid salmonBOT
#

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

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

fringe dragon
#

I'm trying to confirm if this is supported via the API by testing, hang tight

#

Ok, that is not supported via the API today but one of my teammates is actively working on this. However, there is not a timeline when this would be complete.

ancient pelican
#

Ok. We'll keep an eye out for that functionality.

If we set up a session passing in the customer ID, that will use the configuration as set up in the dashboard right?

fringe dragon
#

They would still need to login

#

I highly recommend that you test this

ancient pelican
#

We will.

As for some feedback, if we could have parity between what the API configuration will handle and what the dashboard handles, or allow us to use the dashboard configuration unless we override part of it (what products the user sees for instance) that would really help us out a lot. We've found that as we've added complexity in our product line, the billing portal has become a headache. We might have to not use it for handling subscription updates because we need more control over that than the dashboard allows.

We also need to auto log in the customers because making them log in really isn't an option as we have resellers who use different emails than the customer ultimately uses.

fringe dragon
ancient pelican
#

Thanks. We will do so.