#salmoon_api
magic nymphBOT
👋 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/1218323624855994430
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
coarse veldt
Here are screenshots of the two operations and what they return. Both operations use a customer email copied directly from the Dashboard
teal ironBOT
wintry cedar
Hi there, sorry for the delay!
coarse veldt
No problem 🙂 Thank you for being here
wintry cedar
In your first screenshot (the GET call to /v1/customers), email should be a body parameter, not a query parameter. Not sure why the second screenshot (the call to /v1/customers/search) didn't return a result. Could you share your account ID or a recent request ID?
I'd like to take a look at your logs
coarse veldt
Sure, let me see
My account ID is acct_1F34KCHAKU8aYpwk
Also, I tried to put email as a body paramenter, and the response is still the same
wintry cedar
Taking a look!
coarse veldt
Thank you!
wintry cedar
Ah, I think I see what's happening here. I take it you're searching your Dashboard for users with a specific email address, are finding results, and are expecting to see the same results with your GET calls?
coarse veldt
Yes, that's what I expected 😅
What I expected was that I'd be able to find the users I have in my Dashboard through the API by specifying their emails
(or customers, the pane is called Customers and that's what I've been looking at)
wintry cedar
I see the customer you're attempting to retrieve is what we call a "guest" customer. this is not a real customer, it's a way we group payments we think are related
More details about Guest Customers are available here: https://support.stripe.com/questions/guest-customer-faq
Any calls to retrieve Customers will only return Customer objects (with IDs "cus_..."), not Guest Customers
gentle shoal
@coarse veldt we're about to close for the week end. Any last question?
coarse veldt
Thank you, in that case, I have two more questions for after the weekend (@gentle shoal you can come back to it after the weekend):
- Is there a way to automatically convert these already-existing guests to "real" customers so I can use them?
- Is there a way to create customers automatically when someone buys my app, for example by modifying my checkout session, or do I have to create some sort of a custom workflow? I'm not sure where to look in the docs, as I'm a total Stripe beginner.
I'm also attaching my "create checkout session" file for reference
gentle shoal
- no that's impossible
- You can use
customer_creation: https://docs.stripe.com/api/checkout/sessions/create#create_checkout_session-customer_creation
(we don't really follow up after the week end, this thread will be closed permanently, but you can come back on Monday and ask new questions for sur 🙂
coarse veldt
Ok
gentle shoal
The change I mentioned will create a brand new Customer every time though which is not good and is partly why our Guest Customers feature is way better as it groups them for you in the Dashboard
if you are creating Customers in theory you should have your own "account management" on your app/website, recognize when they come back, re-use their existing Customer id cus_123 on Checkout Session creation, etc.