#denjaland_api
dense thornBOT
👋 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/1240975865102340150
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
kindred thistle
hi! not sure what you mean, can you elaborate?
eager imp
hiya - probably a stupid question, but the API docs still show old version - I don't want to change the version there because we have some integrations still using that version, but for new implmeentations, we of course want to see the "latest version" of the documentation
this is what we see at the bottom left, so we still see 2019 version of the docs
eager imp
are you sure?
kindred thistle
100% yes
eager imp
okay - weird - I always thought the version was considered in the documentation 🙂
kindred thistle
what's in the docs is static and does not match itself to your own API version(which is a source of confusion)
yeah you would think it would be, hence the confusion
eager imp
okay - reason I was thinking it is because I assumed in newer versions, charge.payment_method would have been expandable by now 🙂
so to get payment method, I'd still need to retrieve it seperately with the charge.payment_method then, right?
(I was looking for the easiest way to get the payment_method.type - it doesn't appear in the paypment method details (except for the key of the array there), and payment_method doesn't seem expandable