geordi-upcoming-invoice | Stripe Developers | Page 1

wild onyx Nov 18, 2021, 2:28 PM

#

Hi 👋 do you happen to have the request ID (req_XXX) from when you called that endpoint that you could share?
https://support.stripe.com/questions/finding-the-id-for-an-api-request

obsidian relic Nov 18, 2021, 2:30 PM

#

Hey, will take a look now!

#

Here it is: req_cFKMlRnp5QQ0I3

wild onyx Nov 18, 2021, 2:33 PM

#

Thanks, taking a look

#

Alright, so I can see what you're passing into us, would you mind pasting the response that you received so I can compare?

obsidian relic Nov 18, 2021, 2:36 PM

#

I hit the discord paywall - the response is too long 😆

#

I'll trim it down a bit

wild onyx Nov 18, 2021, 2:38 PM

#

Haha, I forgot that was there, you may be able to dump it in a txt file.

obsidian relic Nov 18, 2021, 2:39 PM

#

https://gist.github.com/geordidearns/1f86ecd7f3863297c87a177f245a520f

Gist

stripe-response

stripe-response. GitHub Gist: instantly share code, notes, and snippets.

#

Theres a gist!

wild onyx Nov 18, 2021, 2:45 PM

#

Thanks for that, I think it's because the price you're moving to is volume-based, but am working on confirming that.

obsidian relic Nov 18, 2021, 2:46 PM

#

ah Okay! We assumed it would be returned as we have the volume (quantity) so should be able to work out the tier, and return the unit_price for that tier - thanks for looking into this!

wild onyx Nov 18, 2021, 2:59 PM

#

Thanks for your patience. I was able to confirm that unit_amount won't be populated as the volume price doesn't have a single set one. You could work backwards to calculate it by dividing amount by quantity (both fields are on the line item object).

#geordi-upcoming-invoice