#CrisBadilla-invoices

1 messages · Page 1 of 1 (latest)

wraith crater
#

Hi 👋 I'm not readily aware of any changes being made to those endpoints, and don't see anything related in our API changelog that shows changes made in between API version releases:
https://stripe.com/docs/changelog

Do you have more details about the problem that you were encountering?

Changelog

Keep track of every change to the Stripe API.

spice bluff
#

Yes, The problem was, when I sent this request: https://api.stripe.com/v1/invoices/upcoming?customer=cus_MeMlqrmfVa5K6j&subscription=sub_1Lv42549NNKdO11vG4d5sgKx&subscription_items[][id]=si_MeMlmvNJBWwoW2&subscription_items[][plan]=150788&subscription_items[][quantity]=1&subscription_items[][plan]=150491&subscription_items[][quantity]=1&subscription_proration_behavior=create_prorations&subscription_proration_date=1666797834 the endpoint returns ok, but the lines.url property returns the next "/v1/invoices/upcoming/lines?subscription=sub_1Lv42549NNKdO11vG4d5sgKx&subscription_proration_date=1666797834&subscription_proration_behavior=create_prorations&subscription_items%5B%5D%5Bquantity%5D=1&subscription_items%5B%5D%5Bplan%5D=150788&subscription_items%5B%5D%5Bid%5D=si_MeMlmvNJBWwoW2&subscription_items%5B%5D%5Bquantity%5D=1&subscription_items%5B%5D%5Bplan%5D=150491&customer=cus_MeMlqrmfVa5K6j" (with query parameters) but our system was expecting "/v1/invoices/upcoming/lines"

#

So, the system added the query parameters again and performed the call with duplicated query params and our system crashed

fickle kernel
#

Checking in to this.

#

Do you have the request ID (req_123) from the request that you made that saw this behavior?

spice bluff
#

Give me some minutes to get this information from stripe

fickle kernel
#

No worries, my colleague found info on this. Looks like there was a recently deployed change that caused this behavior. Still figuring out what should happen next here

fickle kernel
#

Hey apologies for the delay here. It looks like this change did not cause many errors and only in test mode, so it isn't looking like we are going to roll it back at the moment.

#

Apologies for the inconvenience. We have processes to catch potentially breaking changes and not release them until API version updates, but it looks like this one got past that here.

#

Right, that is the plan now to keep it.

spice bluff
#

So, to understand, there was a change yesterday in test and prod mode related to that endpoints. Right?

fickle kernel
#

Correct