#chrisg_customer-portal-configuration-discussion
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/1354600550032871645
đ 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.
- chrisg_api, 1 day ago, 4 messages
Hi! You can read more about the implementation of it here: https://docs.stripe.com/customer-management/configure-portal
i already read that. i am wondering about the right way to call the API.
if we do create new configuration objects every time we call the API, are there limits that we could run into?
we want to have two separate configurations for the customer portal (one for consumer subscriptions and one for business subscriptions). the stripe dashboard UI does not allow us to create multiple configurations afaict so we need to create configurations via the API
so if i do that, do i only need to call the API twice to create the configuration objects and then reuse those IDs whenever i create a customer portal session for a user, or should i be creating a new configuration object every time i create a new customer portal session?
Sounds like you should only need two configurations that you choose from, depending on whether it's consumer or business, ya?
yup
just trying to make sure we're not doing anything crazy before we actually write this code
I think you just need two configurations in this case.
If you think about it like 'one config per product lines', I think that maps; you have consumer and business product lines, so you need two configs.
Do we need to create the configurations with each API key for the various sandboxes/test mode/production? Or can we just use any API key to create the portal configuration and expect that configuration ID to be found across environments?