#brokensparks_best-practices

1 messages ¡ Page 1 of 1 (latest)

warm parrotBOT
#

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

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

sullen solstice
#

hello! looking at this now

#

so basically you have a charge ID and you want to identify the invoice ID that originated it, right?

#

which API version are you on? do you have an example invoice / charge?

frank sphinx
#

Is there any additional info you need?

sullen solstice
#

hello! i already asked for some additional info, can you share what API version you're using or an example invoice / charge?

sharp iron
#

Hi sorry, we can't see discord responses on my friends machine for some reason - only his sent messages to you

sullen solstice
#

oh that's odd

sharp iron
#

we aren't using the api yet, could use any version that has invoice_id attached to it

#

our goal is to log all charge_obj data in our sql db, and relate it to a invoice_id parent record

#

but did not see the invoice_id on charge_id body

#

so wondering if it exists at all on charge obj, or if we should use a different access pattern entirely?

If different access patter, do you have any suggestions for the best way to implement?

sullen solstice
frank sphinx
#

Okay, great, thanks so much

sharp iron
#

Thank you!