#jairo094215_api
oak echoBOT
👋 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/1263504831377575976
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
daring thornBOT
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- jairo_connect-webhooks, 2 days ago, 7 messages
undone heath
Can you share an event id where it was an empty string and an event id where it is null?
urban herald
yes
empty string: evt_1PbUvGDyCiiQ0txVAJfAbI2D
null: evt_1PdnyZDyCiiQ0txV6otqNYVA
urban herald
great, thanks
We're creating client subscriptions using Stripe Checkout, and those invoices are generated automatically by Stripe
undone heath
When did this start happening?
urban herald
I don't know exactly
probably this property wasn't nullable in the past? not so far... we've invoices registered correctly on 11 july
undone heath
Have a colleague looking into this, but you should code your webhook handler so this doesn't break it. Description is a nullable string, so it can be null or it can be a string: https://docs.stripe.com/api/invoices/object#invoice_object-description
urban herald
Yes! We are on it 🙂
But we would like to find the cause of this change if is possible
Thank you!
undone heath
No problem. Will get back to you
undone heath
We identified the issue, and we'll revert the change
Still recommend that you code in such a way that this doesn't break your integration. Ideally this shouldn't be a breaking change
urban herald
Oh, it was and accidentally breaking change from your side?
undone heath
It shouldn't be a breaking change since that field is a nillable string
It was unintentional that we started sending a empty string instead of null
But it shouldn't break integrations because we do say that the field can be null or a string in the docs, so you shouldn't code in a way that breaks your integration if you receive a string