#stove_api
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/1384633765577621504
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi, can you share the request where you attempted to make that GET request?
On the API, it does not look like that is a valid param: https://docs.stripe.com/api/payment-link/object
It looks like the payment link creation was made via the Dashboard: https://dashboard.stripe.com/logs/req_odZSotzNuj3puR and not the API.
Further looking
Yes - I see that re: API. I was just hoping there would be some type of way to access it because it's really important for one of our customers
The payment link was indeed created via the Dashboard and not the API
I just need to retrieve it via the API and ideally get that parameter as well.
Can you try https://docs.stripe.com/api/payment-link/retrieve-line-items while I test/ confirm with my teammates in the meantime?
Absolutely!
Same situation. req_ztOngP1SEPhyOc. I ran
stripe.PaymentLink.list_line_items(
"plink_1RZbJBJn1DR7Pqdxj4tEnLYY",
expand=["data.adjustable_quantity"]
)
And it let me expand it without throwing an error, but didn't return that field.
Thank you for checking with the teammates!
That was a stretch since it's not in the API but worth the try
haha I appreciate it - I tried :p
Yeah, I was able to reproduce it on my end. We're checking if it's supported with the endpoint
Appreciate you so much!!
It seems like a bug to us, we're further looking on our end. I will share an update as soon I can.
We're going to raise this to our product team as a next step. We do not document that as an expandable field and I think as you mentioned it does makes sense to. I'll share instructions on how to follow-up about this issue by writing in to support. In the meantime, I think you tracking these adjustible quantities as you create them on your end would be helpful. I know this is not ideal but the team will review your request.
Hello @hot parrot, we have sent you a direct message, please check it at https://discord.com/channels/@me/1384641358945452054
- 🔗The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.