#ds_api
cerulean anchorBOT
đ 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/1365075798641475688
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
radiant hound
Hi there. There were breaking changes introduced in Basil that change the shape of the Invoice object. https://docs.stripe.com/changelog/basil#2025-03-31-invoice-flexibility
Could you give me the request id (req_abc123) for the most recent request where the Invoice didn't have the parameters you were expecting?
heavy veldt
Hello, thanks for looking into it. I can see the closed attribute using postman for that invoice
The link you shared does not mention about this attribute in particular
Where can I look for the request_id?
heavy veldt
Also I won't be able to share the invoice id in particular
radiant hound
An example request will be enough to look
radiant hound
I'm sorry, but an image isn't that helpful. Can you send over the text, please?
heavy veldt
req_FISDRDKifn9xSf
radiant hound
thank you
heavy veldt
sorry, I work on a client VDI
radiant hound
No problem. This Invoice is over 4 years old, so it is pretty likely that the shape of the object has changed since then. For example, closed isn't a parameter in the current version of the API and at least going back to Acacia: https://docs.stripe.com/api/invoices/object
Do you know roughly when the API version change was made?
heavy veldt
We are using api version 1. I am not very much aware of that. Also do you know which version of acacia should I use since its an old invoice
?
I tried to use till 09-3O-2024 acacia version
radiant hound
That's not what the /v1/ means. If you aren't setting a API version in postman in the request headers, then the default api version on your account will be used, which is 2018-02-28.
heavy veldt
Oh okay
radiant hound
Let me test and see what the Invoice looks like in that API version
Okay so closed still exists on the Invoice in 2018-02-28. If you are specifying a version, such as 09-3O-2024.acacia, the request will return a version of the Invoice in that API version and won't include parameters like closed which no longer exist
heavy veldt
I guess its not acacia
radiant hound
that's not a real API version. The version is " 2018-02-28". Acacia was a major release from last year where we moved to "named" releases
to be clear, if you want to use 2018-02-28, you can simply not set a version at the request level, because that is your account's default api version.
heavy veldt
Thank you! Can I use a version even older than that? There might be invoices older than that I guess. Do you have a link where I can find all the older versions?
radiant hound
But the problem is that it is going to be difficult to identify what API version the Invoices were created with.
heavy veldt
yeah true
Do you recommend using REST API calls instead of stripe library?
I am able to get the attribute now for that invoice
radiant hound
Personally, I've always worked with Stripe's SDKs and found the developer experience to be easy to use and effective
heavy veldt
Oh Okay. We have designed currently to use the stripe API approach
by SDK do you mean python library for stripe?
I really appreciate your assistance today!
radiant hound
Yes, as in https://github.com/stripe/stripe-python
heavy veldt
Thank you for sharing!